HI All,

Just wondering if someone can help me.

Up until just recently, my Empeg was running with a 20G and the original 12G drive. This has been working fine for over a year.

A couple of days ago, I was given an 32G drive from an IBM Thinkpad, so I figured I may as well use it in the Empeg.

I installed the 32G drive in place of the 12G, with the new drive as slave and the 20G as master. The 20G is connected to the end of the cable.

I ran up the builder image, and left the setup stress testing for around 24 hours, and didn't see any errors.

This afternoon when I was uploading my final batch of music (I had around 7G free in total), I noticed that the uploads had started to freeze periodically, until eventually the upload process hung altogether.

I then proceeded to try and fsck the disks, so as to check if they were okay.

Upon my first attempt, I did the following:

ro
umount /dev/hda4
umount /dev/hdc4
swapon /swapfile
fsck -fay /

At this point, I started seeing the following errors:

hda: multwrite_intr: error=0x10
ide0: reset: success error=0x10
hda: multwrite_intr: status=0x51
hda: multwrite_intr: error=0x10
end_request: I/O error, dev 03:06 (hda), sector 320
ide0: reset: success information

These were repeated a number of times, and the fsck failed to complete.

I then rebooted the player, and tried again. This time the fsck of / and /dev/hda4 went okay.

I then attempted to fsck /dev/hdc4 (30G drive), and saw the following:

empeg:/# fsck -fay /dev/hdc4
Parallelizing fsck version 1.19 (13-Jul-2000)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hdc4 is mounted.
Pass 1: Checking inodes, blocks, and sizes
hda: irq timeout: status=0xd0
ide0: reset timed-out, status=0x80
hda: status timeout: status=0x80
hda: drive not ready for command
ide0: reset: success
hda: irq timeout: status=0xd0
ide0: reset: success
hda: irq timeout: status=0xd0
ide0: reset: success
hda: irq timeout: status=0xd0
ide0: reset: success
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hdc4: 15590/243328 files (16.1% non-contiguous), 26241963/31142002 blocks
empeg:/#

I'm not sure exactly what this means, as the 20G disk (/dev/hda) has previously performed perfectly. If anyone can offer any suggestions, I'd be very grateful.

I was about to start testing things by removing the 30G disk, and just trying the 20G, but if anyone can offer an explanation of the error messages that might help explain the problem, that would be great.

Thanks,

Bagpuss.

EDIT: A quick addition to say that I'm running v2.0 final developer image with Hijack 413.


Edited by Bagpuss (19/10/2004 23:47)