Re: Fsck errors unslung 6.8beta with WD 320GB MyBook Essentials
I have had very similar issues with a Toshiba 500GB drive. However I
found that with time the drive performance was getting worse, i.e. I
got more and more often disk errors when writing to it (slug was
hanging), after which I ran fsck and always got errors as similar as
the below ones.
I was so tired of this that recently I changed to an (older) 250GB
drive, and so far this has been running smoothly (for more than a
Anyway, I too would be interested in hearing anybody who has had
similar experiences and found out why this was happening.
--- In firstname.lastname@example.org, Matthew McDonald <mafm@...> wrote:
> More questions about a new slug.
> Is there any known problem with fsck errors under unslung 6.8beta?
> I've recently unslung a new slug onto a WD MyBook after reading
> worked well with the nslu2. Before I plugged it into the slug, I
> the drive from a windows 2000 machine for a week or so, copying
> GB of files around, running chkdsk repeatedly etc, since I'd had
> luck with usb hard drives in the past. The drive seemed to be fine
> the windows box.
> After formatting the drive in the slug, whenever I fsck the data
> partition, I seem to almost invariably get 2 errors re orphaned
> The following is typical:
> # /sbin/fsck.ext3 -f /dev/sda1
> e2fsck 1.34 (25-Jul-2003)
> Pass 1: Checking inodes, blocks, and sizes
> Inodes that were part of a corrupted orphan linked list found.
> Fix<y>? yes
> Inode 131093 was part of the orphaned inode list. FIXED.
> Inode 557061 was part of the orphaned inode list. FIXED.
> I couldn't get the drive to make errors before it was connected to
> slug. I can boot the slug after running fsck, and reboot within a
> of minutes and find essentially identical errors next time I run
> On the other hand, I can also run the slug for a couple of days and
> 20+G of data to it, delete stuff, and then run fsck and get an
> message about 2 orphaned inodes - the problem doesn't seem to get
> with time - nearly always 2 fsck errors. Also, nothing seems to
> in lost+found after one of these fscks.
> Anyone have any advice, thoughts, or other comments? I'm not sure
> concerned I am about the problem, but it doesn't exactly inspire
> confidence in the data stored on the machine/drive.