Chinaman,

I'm not going to lose my patience as you are trying to help and I am in need of it. HDD1 is the hard drive, it's my system and I know where my drives are at and what they've been assigned. It's the ReiserFS check that has the issue now, not the kernel or the BIOS or whatever else. If I had chosen the wrong /dev assignment there would have been a kernel panic and it never would have reached the file system check as shown by the output offered, which is why I offered it.

I have tried editing /etc/lilo.conf and running lilo however it won't work when the drive is actually /dev/hdb1 as lilo does a sanity check and I as of yet can't force it to boot to /dev/hdd1 for reasons specified in my previous post. What I haven't tried is finding a force option for lilo making it accept /dev/hdd1 and skip the sanity check however I believe that still leaves me with the issue of the ResierFS system check.

What I believe I need is a way to bypass the ReiserFS file system check it goes through upon boot. Then I can boot the drive on a separate controller and see if that truly is what's causing the stability issue. Thanks to all for the assistance so far.

-Tomaczar

Primary IDE Controller
HDD 40GB = /dev/hda
DVD-RW = /dev/hdb

Secondary IDE Controller
HDD 160GB = /dev/hdc
CDROM = /dev/hdd


Therfore:

Second IDE controller, device 0, partition 1 CANNOT be /dev/hdb1

It MUST be /dev/hdc1

The only way around this is by reordering devices in the BIOS (but even then the kernel may see past BIOS preferences when querying the chipset directly) or by hacking the kernel (which I presume you did not do)

Could you please post your /etc/fstab file in entirety here?

--Kim

Oh! And please post the output of:

#fdisk -l

Also post the output of:

# ls -l /proc/ide/

Thanks.