Summary: | udev-070 locking up external firewire hard disk | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | marchino <marchino> |
Component: | [OLD] Core system | Assignee: | Greg Kroah-Hartman (RETIRED) <gregkh> |
Status: | VERIFIED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
marchino
2005-10-18 07:25:50 UTC
If you comment out that line, and then run the vol_id program from the command line (as root), what does it output or do? Any kernel log entries get generated? This is what I see in kernel log running # /sbin/vol_id --export /dev/sda Oct 24 13:32:48 [kernel] ieee1394: sbp2: aborting sbp2 command - Last output repeated 4 times - Oct 24 13:33:48 [kernel] scsi1 (0:0): rejecting I/O to offline device No output from the program itself After this command the unit is unaccessable, and running again the above program gives: /dev/sda: error open volume To get back the drive, I need to switch the unit off and then on. After some further investigation, I've found that the problem isn't related vo vol_id itself, but it seems to stay somwhere between sbp2 driver and the external firewire interface. Disk is a 160Gb ide I've done a badblock scan of the disk and I've found that exactly at 128*1024*1024+1 block it starts giving the same errors as reported for vol_id. I tested the disk directly to IDE interface and it works perfectly, no badblocks or other problems. My conclusion is that the problem arise because the external disk reports to be 160Gb in size, but driver or firmware is only able to handle 128Gb. Sorry for the WOMBAT... Ok, marking closed then. |