Re: [solution]Re: all is read-only
On Wed, 2004-08-04 at 13:45, Rakotomandimby Mihamina wrote: Hi everybody ! :-) These are some (i hope usefull) indications: -The checkroot.sh script was not the same as the one archived by google so that I had to guess how to edit it . I just edited the two lines to have [...] if ! mount -n -o remount,ro / [...] (I'm so sorry, I didnot remember how was the line before I edit it...) and [...] # Remount root to final mode (rw or ro). mount -n -o remount,$rootopts,$rootmode / [...] - I also modified silo.conf : the read-only option - read-write. Now the system boots correctly with the woody 2.4.18 kernel. Thanks to all and see you soon :-) Glad it works. You have to watch out for this repair being undone by future package upgrades. When I had this problem under a Sarge installation it recurred two or three times after package upgrades. According to Dave Miller, the underlying bug is not in checkroot.sh, it is in the kernel. Later kernels from Debian, such as 2.4.26 which I run on an Ultra 10, seem to be patched. -- SP
all is read-only
Hello, I just installed a woody 3.0r1 on an Ultra5. Then I changed the sources.list to testing, then dist-upgraded the distro. All passed ... but when rebooting, the root FS is read-only so that nothong can launch ... (removing tmp files cant'be done because of FS read-only, no deamons can be launch because of FS read-only, ...) It is still kernel 2.4.18 (from the woody one) ... how do you suggest me to solve this ? I cant copy/paste you the boot messages because it's not the same machine as the one i write with now Is it a known problem ? ... Thanks in advance for your precious help -- Rakotomandimby Mihamina Andrianifaharana Tel : +33 2 38 76 43 65 http://www.rktmb.org/Members/mihamina
RE: all is read-only
-Original Message- From: Rakotomandimby Mihamina [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 04, 2004 9:44 AM To: debian-sparc@lists.debian.org Subject: all is read-only Hello, I just installed a woody 3.0r1 on an Ultra5. Then I changed the sources.list to testing, then dist-upgraded the distro. All passed ... but when rebooting, the root FS is read-only so that nothong can launch ... (removing tmp files cant'be done because of FS read-only, no deamons can be launch because of FS read-only, ...) I had the same, this was a hardware error (disk crashed). Do you have another harddisk you can try ?? NF It is still kernel 2.4.18 (from the woody one) ... how do you suggest me to solve this ? I cant copy/paste you the boot messages because it's not the same machine as the one i write with now Is it a known problem ? ... Thanks in advance for your precious help -- Rakotomandimby Mihamina Andrianifaharana Tel : +33 2 38 76 43 65 http://www.rktmb.org/Members/mihamina -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: all is read-only
Op wo 04-08-2004, om 09:43 schreef Rakotomandimby Mihamina: All passed ... but when rebooting, the root FS is read-only so that nothong can launch ... (removing tmp files cant'be done because of FS read-only, no deamons can be launch because of FS read-only, ...) I had the same problem yesterday. Look in the mail archives how to fix checkroot.sh. It's pretty easy. Koen
Re: all is read-only
Figaro, Nicolas wrote: I had the same, this was a hardware error (disk crashed). Do you have another harddisk you can try ?? Oh f$@# ! There's no other possibility ? big smile 'apt-get dist-upgrade' brakes the disk ? because the stable one seemed to boot correctly ... /big smile -- Rakotomandimby Mihamina Andrianifaharana Tel : +33 2 38 76 43 65 http://www.rktmb.org/Members/mihamina
Re: all is read-only
On Wed, Aug 04, 2004 at 09:43:46AM +0200, Rakotomandimby Mihamina wrote: Hello, I just installed a woody 3.0r1 on an Ultra5. Then I changed the sources.list to testing, then dist-upgraded the distro. All passed ... but when rebooting, the root FS is read-only so that nothong can launch ... (removing tmp files cant'be done because of FS read-only, no deamons can be launch because of FS read-only, ...) It is still kernel 2.4.18 (from the woody one) ... how do you suggest me to solve this ? I had the same problems a while ago. Remounting the filesystem read/write and then installing a 2.6 kernel (2.6.7 from a friend of mine) and booting that kernel fixed the problem. Admar
Re: all is read-only
On Wed, Aug 04, 2004 at 09:43:46AM +0200, Rakotomandimby Mihamina wrote: All passed ... but when rebooting, the root FS is read-only so that nothong can launch ... (removing tmp files cant'be done because of FS read-only, no deamons can be launch because of FS read-only, ...) try append at boot to silo rw - it mount rootfs in rw mode. what a filesystem is at /? xfs? -- Andrzej 'The Undefined' Dopierała UNIX Linux administrator, Adam Mickiewicz University WMiI PLD Linux Developer HomePage: http://aramin.net/ JID: [EMAIL PROTECTED]e-mail: [EMAIL PROTECTED]
Re: all is read-only
Admar Schoonen wrote: I had the same problems a while ago. Remounting the filesystem How ? the system doesn't boot till the end ... read/write and then installing a 2.6 kernel hum... I still need to boot correctly first... isn't it? :-) -- Rakotomandimby Mihamina Andrianifaharana Tel : +33 2 38 76 43 65 http://www.rktmb.org/Members/mihamina
Re: all is read-only
The Undefined wrote: try append at boot to silo rw - it mount rootfs in rw mode. I'll try This is the content of my silo.conf file. partition=1 root=/dev/hda1 timeout=100 image=1/vmlinuz label=linux read-only what havei got to edit to make it possible ? I guess adding rw somewhere ... what a filesystem is at /? xfs? ext2 PS :as well as i could'nt boot with the precedent dist-upgraded system, i did another installation, and now, will ask for your opinion before finally boot (and pray). -- Rakotomandimby Mihamina Andrianifaharana Tel : +33 2 38 76 43 65 http://www.rktmb.org/Members/mihamina
Re: all is read-only
I re-did another fresh new install, but checking badblocks. I found no badblocks. -- Rakotomandimby Mihamina Andrianifaharana Tel : +33 2 38 76 43 65 http://www.rktmb.org/Members/mihamina
Re: all is read-only
Koen Vermeer wrote: I had the same problem yesterday. Look in the mail archives how to fix checkroot.sh. It's pretty easy. I searched but did not find ... google had not the time to archive it, I guess... would you help me to find the relevant thread please? Thank you. -- Rakotomandimby Mihamina Andrianifaharana Tel : +33 2 38 76 43 65 http://www.rktmb.org/Members/mihamina
Re: all is read-only
On Wed, Aug 04, 2004 at 02:37:44PM +0200, Rakotomandimby Mihamina wrote: Admar Schoonen wrote: I had the same problems a while ago. Remounting the filesystem How ? the system doesn't boot till the end ... You can boot in single user mode (runlevel 1) if you type 'linux single' on the silo prompt. after that, you can fsck your filesystem, mount it read/write and install a 2.6 kernel. Admar
Re: all is read-only
Don't get me wrong, but maybe you should just combine your minutely emails into one... On Wed, 2004-08-04 at 14:55, Rakotomandimby Mihamina wrote: Koen Vermeer wrote: I had the same problem yesterday. Look in the mail archives how to fix checkroot.sh. It's pretty easy. I searched but did not find ... google had not the time to archive it, I guess... would you help me to find the relevant thread please? Thank you. -- Rakotomandimby Mihamina Andrianifaharana Tel : +33 2 38 76 43 65 http://www.rktmb.org/Members/mihamina
Re: all is read-only
On Wed, Aug 04, 2004 at 02:37:44PM +0200, Rakotomandimby Mihamina wrote: Admar Schoonen wrote: I had the same problems a while ago. Remounting the filesystem How ? the system doesn't boot till the end ... read/write and then installing a 2.6 kernel mount -o remount,rw / -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/
Re: all is read-only
On Wed, Aug 04, 2004 at 02:51:12PM +0200, Rakotomandimby Mihamina wrote: The Undefined wrote: try append at boot to silo rw - it mount rootfs in rw mode. I'll try This is the content of my silo.conf file. partition=1 root=/dev/hda1 timeout=100 image=1/vmlinuz label=linux read-only my silo.conf on one from my sparcs ;) [EMAIL PROTECTED] undefine]$ less /etc/silo.conf partition = 1 root = /dev/sda1 read-write default=linux timeout = 100 image = /boot/vmlinuz-2.4.20 label = linux-2.4.20 alias = linux append = root=/dev/sda4 rw (but it isn't debian - pld) -- Andrzej 'The Undefined' Dopierała UNIX Linux administrator, Adam Mickiewicz University WMiI PLD Linux Developer HomePage: http://aramin.net/ JID: [EMAIL PROTECTED]e-mail: [EMAIL PROTECTED]
Re: all is read-only
Op wo 04-08-2004, om 14:55 schreef Rakotomandimby Mihamina: Koen Vermeer wrote: I had the same problem yesterday. Look in the mail archives how to fix checkroot.sh. It's pretty easy. I searched but did not find ... google had not the time to archive it, I guess... would you help me to find the relevant thread please? Start google, type 'checkroot.sh sparc', and click on the first link that shows up. To apply the fix, start with typing something like 'linux single' on the silo prompt, enter your password on the prompt, remount / (something like 'mount -o remount,rw /') and change the two lines in checkroot.sh according to the fix. Sorry, I cannot make it much easier than this... Koen
[solution]Re: all is read-only
Hi everybody ! :-) These are some (i hope usefull) indications: -The checkroot.sh script was not the same as the one archived by google so that I had to guess how to edit it . I just edited the two lines to have [...] if ! mount -n -o remount,ro / [...] (I'm so sorry, I didnot remember how was the line before I edit it...) and [...] # Remount root to final mode (rw or ro). mount -n -o remount,$rootopts,$rootmode / [...] - I also modified silo.conf : the read-only option - read-write. Now the system boots correctly with the woody 2.4.18 kernel. Thanks to all and see you soon :-) -- Rakotomandimby Mihamina Andrianifaharana Tel : +33 2 38 76 43 65 http://www.rktmb.org/Members/mihamina
