RE: Disaster strikes
Joel
Just to clear up, in my earlier email I meant I could mount the drive rw
using your original advice (mount -o remount,rw /) but couldn't get the
changes to checkroot.sh to work.
I have since discovered I was making one of the changes in the wrong place,
you pointed this out as below.
Using the -t $roottype doesn't work, so I removed the $rootdev and
$fstabroot entries and this has resolved the issue.
My only concern now is if I do another apt-get dist-upgrade will this
re-occur? This is how the problem arose.
Thanks for your sage advice.
James
-----Original Message-----
From: Joel Soete [mailto:jsoe0708@tiscali.be]
Sent: 28 July 2004 15:21
To: James Morris; debian-hppa@lists.debian.org
Subject: RE: Disaster strikes
Hello James,
> -- Original Message --
> From: "James Morris" <jmorris@photonicmaterials.com>
> To: <debian-hppa@lists.debian.org>
> Date: Wed, 28 Jul 2004 10:04:34 +0100
> Subject: RE: Disaster strikes
>
>
> Joel
> I have been trying a few things, can't get this to reboot with the root
FS
> as rw.
Did you try to reboot in single -user mode (append option -s to your boot
cmd line at palo prompt;
at the prompt "enter root passwd or CTRL-D..." you enter your root passwd
and try the Thibaut tips:
"mount -o remount,rw /"
If you have some error message, can you send it?
> I have attached my original checkroot.fs which you sugested be edited
> following your instructions below (Attached email).
> I have provided the unedited version.
> Regards
> James
[...]
>
> if [ "$rootcheck" = yes ]
> then
> #
> # Ensure that root is quiescent and read-only before fsck'ing.
> #
> if ! mount -n -o remount,ro $rootdev /
here either you add "-t $roottype" or you remove "$rootdev"
> then
> echo -n "*** ERROR! Cannot fsck root fs because it is "
> echo "not mounted read-only!"
> echo
> rootcheck=no
> fi
> fi
>
[...]
>
> #
> # Remount root to final mode (rw or ro).
> #
> mount -n -o remount,$rootopts,$rootmode $fstabroot /
>
and here either you add "-t $roottype" or you remove "$fstabroot"
> #
> # We only create/modify /etc/mtab if the location where it is
> # stored is writable. If /etc/mtab is a symlink into /proc/
> # then it is not writable.
> #
[...]
(just to be sure, I suppose that you reach to mount your root fs (/) in
rw mode starting from your cd or from another system to save your modified
file?
If that's right and it failed again, can you put a "set -x" at the begining
of checkroot.sh (that put the script in trace mode) and if you have the
new opportunity to grabe the console output during your next try to boot,
it would nice that you post those new results.)
Tell us what?
Joel
---------------------------------------------------------------------------
Tiscali ADSL LIGHT, 19,95 EUR/mois pendant 6 mois, c'est le moment de faire
le pas!
http://reg.tiscali.be/default.asp?lg=fr
Reply to: