> However after the crash and a reboot I got a message like this on bootup: > /dev/hdb1 is already mounted, aborting
It's strange for the system to mess up mount order. fstab doesn't have a noauto option, so the only way to get that error is for something to mount everything, and then for something else to explicitly mount hdb1 again. > check on startup flags for those filesystems. Now the system boots up > fine and mounts those filesystems, but neither "df" or "mount" show them > as being mounted. mount only shows the contents of /etc/mtab. If your rott fs is read-only that file can't be updated. To get a precise idea of what's really mounted, look into /proc/mounts. Perhaps df does something similar to find mounted filesystems. > Has anyone else encountered this bizarre behaviour and have an idea of > how one might fix it? Never seen. I'd boot from CD and run smart disk selftests first. Then fsck on all partitions. Mount everything read-only and run rpm -aV, which will tell you any package files that were corrupted. If you find corruptions I suggest a mkfs, after backing up everything important. But don't just restore /usr, /opt, or worse /etc from backup over top of your newly installed system... Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
