On Monday 21 April 2003 01:09 pm, Anders Johansson wrote:
On Mon, 2003-04-21 at 20:02, Peter B Van Campen wrote:
"FATAL: cannot change permission of TTY - read only file system" and login is impossible.
It sounds like something failed on startup. I'm guessing the "fsck on startup"
some text clipped......................................
There is no "read/write" status set at partition level. When the system boots, the partition is mounted read only. This is at OS level, so fsck can work undisturbed. If everything runs to completion, the file system gets remounted read/write.
Do you know the names of your partitions (/dev/hda3 for example) and what file system you have on them? If you do, run fsck for that file system from the rescue system. For example, if / is /dev/hda3 with reiserfs, you would run
reiserfsck /dev/hda3
If there are any problems, it should tell you what you need to do.
It could of course be something other than the fsck, but without the boot log it's difficult to say what.
Thanks for the assistance Anders, here is what I found/did: /dev/hda1 is boot and ext2 /dev/hda2 is swap /dev/hda3 is root and reiserfs from the 'root' of rescue console I ran fsck on /dev/hda1 "boot" all ok, no errors I ran reiserfssck on /dev/hda3 all ok, no corruption or errors did a shutdown and booted the HD (should be at the same point of 'install phase= first boot of new install on /dev/hda1) the new installations boot choice screen is ok, select "Linux", boot options are ok, hit enter. the boot process starts and screens of msgs pass until I start to see "can not do ***, read only file system" but these msgs scroll away very quickly, then it shows a char mode logon prompt, but it won't accept aa logon, complains that it has a 'read only' file system. I do not know how to view the boot log for more careful examination, since it is not mounted and I can't get to a cmd line on the 'hung sys' Thanks for the kind attention ................ PeterB