Hi All, After having done a near-flawless update of one 8.1 sys I started to update my other system. Things went properly until the installer/update process got to the point of booting from the HD for the first time, to continue the update. The boot starts and proceeds well, but after a few screens of the typical boot msgs a lot of "Can't do this or that : real only filesystem" msgs start to pile up. Eventually the non-graphic text msg : "XXX Login: " appears but when I type 'root' it replies: "FATAL: cannot change permission of TTY - read only file system" and login is impossible. I tried re-starting the update from the start w/o success. Same result. I have gotten the rescue system to start but I am a loss as to how to proceed. I think that resetting the 'read/write' status of the / partition might do it but the rescue sys is cryptic at best. The HD is reiserfs from 8.1, boot is in a seperate partition. Can anyone help me here? PeterB
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"
I tried re-starting the update from the start w/o success. Same result. I have gotten the rescue system to start but I am a loss as to how to proceed. I think that resetting the 'read/write' status of the / partition might do it
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.
but the rescue sys is cryptic at best. The HD is reiserfs from 8.1, boot is in a seperate partition.
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.
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
On Mon, 2003-04-21 at 23:03, Peter B Van Campen wrote:
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'
Try switching to tty10 with ALT-F10. With a little bit of luck, the relevant error messages will still be there. If they're not, I'm out of ideas, since with a read-only file system, the file boot.log won't be created. If F10 has scrolled past the errors causing the trouble, I can't think how to get at them
Dear Anders & List, On Monday 21 April 2003 04:11 pm, Anders Johansson wrote:
On Mon, 2003-04-21 at 23:03, Peter B Van Campen wrote:
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'
Try switching to tty10 with ALT-F10. With a little bit of luck, the relevant error messages will still be there.
If they're not, I'm out of ideas, since with a read-only file system, the file boot.log won't be created. If F10 has scrolled past the errors causing the trouble, I can't think how to get at them
Hi again... Using alt-F10 I see error msg: "CLM-6006 writing inode 30496 on read-only FS" Now when the update process is 'cleaning up' in preperation for the first boot of the new code it says that it is writing this and that to the new system; I never see anything that suggests that it ISN'T writing those out. This just has to be an error in the install scripts. There must be a way to set my / (root) back to read/write from the rescue system! Anyone? .................. Help! ............ PeterB
I have some interesting new info: see bottom of email On Monday 21 April 2003 07:28 pm, Peter B Van Campen wrote:
Dear Anders & List,
On Monday 21 April 2003 04:11 pm, Anders Johansson wrote:
On Mon, 2003-04-21 at 23:03, Peter B Van Campen wrote:
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'
Try switching to tty10 with ALT-F10. With a little bit of luck, the relevant error messages will still be there.
If they're not, I'm out of ideas, since with a read-only file system, the file boot.log won't be created. If F10 has scrolled past the errors causing the trouble, I can't think how to get at them
Hi again... Using alt-F10 I see error msg: "CLM-6006 writing inode 30496 on read-only FS"
Now when the update process is 'cleaning up' in preperation for the first boot of the new code it says that it is writing this and that to the new system; I never see anything that suggests that it ISN'T writing those out. This just has to be an error in the install scripts.
There must be a way to set my / (root) back to read/write from the rescue system!
Anyone? .................. Help! ............ PeterB
This PC has a Tyan Tiger 230 SMP P-III mother board with built-in USB-1 ports. The USB sub-sys has been working fine on 8.1. Now I've booted the 8.2 DVD and selected to do clean install on /dev/hdc which is an up-to now unused 10GB drive I had. Once the fresh install process got started it proposed an install scenario. Now here is the ODD PART: the proposed install config wanted to : "Create Swap 1004.0 MB on /dev/sda1" and "Create root 1.00 TeraB on /dev/sda2" Wow! /dev/sda has to be the USB system, because there are NO scsi devices connected to the scsi card in the sys. It is beginning to look like the install scripts are mis-reading what they see on the system. So I disabled the USB on the bios, and the proposed install is now on /dev/hdc1 and it sees the correct size now. My guess: The SuSE 8.2 install scripts will favor a scsi drive over the ide drives given a choice, but they do not take into consideration that a USB mass-storage device is setup as /dev/sda on a sys that has no real scsi drives. Somewhere in the install code there is a serious error in the part that determines the size of some scsi drives. Now an observation/critique on the install/update process in 8.2 When you do a 'clean/fresh' install, the process offers the option to edit/modify the proposed config before you 'commit'; but the update process doesn't even allow for viewing the config choices it is going to use much less edit/modify them. But I still have my orig prob. When the half installed update is booted it still thinks that the / (/dev/hda3) is read only, and I don't how to get it set to read/write. When I boot from DVD 1 and start the update from the start it goes all the way to the "Booting from HD for first time" with out any errors or complaints. But once the boot is rolling it starts pumping out the 'read-only' errors and the sys ends up useless. What to do? PeterB
participants (2)
-
Anders Johansson -
Peter B Van Campen