On Monday 11 October 2004 04:28 pm, Patrick Shanahan wrote:
* Jerome Lyles
[10-11-04 21:01]: On Monday 11 October 2004 03:42 pm, Patrick Shanahan wrote:
Rebooted-still the same. I've got to run now,
Running out of ideas. Try booting "Failsafe".
One other off-the-wall thought. It *is* the root file system that the 'fsck failed' message is referring, isn't it? Because you may have more than one dirty partition and the system will stop the same way.
What is your drive layout, partition structure per /etc/fstab?
/dev/hda5 is a swap /dev/hdb1 is a swap /dev/hda1 is ext3 or 2 /dev/hda6 is ext3 or 2 /dev/sda1 is reiserfs /dev/fd0 is ext2 I think /dev/pts /proc /mnt/linux nfs /proc/bus/usb Both /dev/dvdrecorder and /dev/fd0 are mounted under subfs. fsck couldn't check fd0, /dev/pts, /proc, /mnt/linux or /proc/bus/usb. I recreated both swap partitions: swapoff -a -v mke2fs -c /dev/hda5 mke2fs -c /dev/hdb1 mkswap /dev/hda5 mkswap /dev/hdb1 swapon -a -v I ran e2fsck on /dev/hda1 and /dev/hda6. All good. Every time I reboot and check mtab it has two entries for /dev/hdb2 and it's always mounted 'rw' even though I erase one entry every time. And my prompt looks like this: (none):~>; with 'none' where 'filesystem repair' or something should be according to Anders. My external firewire drive: reiserfsck /dev/sda1 Error: Failed to open '/dev/sda1' no such device or address. Aborted Yet if I do this: init 5 login as my regular user at the prompt and startx manually then open /media/fireiredrive I can read and write the partition. This may be relevant. I first noticed this problem because I partitioned and formated my new firewire drive and mounted it at /media using Yast. I looked in my drives:/ folder and it was empty. I decided rebooting might help. It didn't. If I turn the firewire drive off, it doesn't change anything. The system reboots with the same problems. What program do you think adds another entry to mtab when I reboot ? Well, that's all I can think to do or remember. I'm going to bed, Jerome