Problems with a debian nslu install and Seagate FreeAgent USB disk
Hello you all,
I've just installed a brand new slug and drive (both of them were not
used before, they've gone from the box to the current state).
The Drive is a Seagate FreeAgent Desktop 320gb plugged into the USB1.
I've formatted it through the debian install with 2 primary
partitions, one of 319.5 ext3 and the other 512 for swap.
I've followed the steps on (http://www.cyrius.com/debian/nslu2/). I've
used the latest firmware from (http://www.slug-firmware.net/)
debian-etch-rc2-20070308.
I haven't installed anything but the base system in the install guide and samba.
But even before installing samba the following happened, when I leave
the system (slug+drive) unattended, when I come back the volume is
remounted read-only (/dev/sda1 on / type ext3 (rw,errors=remount-ro))
and I get the following on dmesg:
sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 219562047
Buffer I/O error on device sda1, logical block 27445248
lost page write due to I/O error on sda1
Aborting journal on device sda1.
ext3_abort called.
EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 624031612
sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 624035708
It happened 3 times, I'm still researching what's wrong, after the
problem I run fsck and It report no errors.
Right now I'm running e2fsck to check for badblocks, until now (60%)
it also didn't report any errors until now, as I said earlier it's a
brand new drive.
I'm not a very deep hardware specialist, but could it be a problem of
for some kind of "new feature" of the drive it turns off something and
when the system makes a call it fails?
I've searched all the day for some problem like mine and didn't find anything.
If someone has any idea where I can start looking for something please
tell. All the other log files are ok, nothing is being reported
anywhere.
Regards,
Jose Muanis
Reply to: