- To: Geoffrey Cowling <geoffrey.cowling@xxxxxxxxx>
- Subject: Re: [SLUG] odd system loss
- From: Amos Shapira <amos.shapira@xxxxxxxxx>
- Date: Sat, 25 Jul 2009 08:01:54 +1000
- Cc: slug@xxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=vAXEWCYHu6nkyX1MlP6to8wHerL8nPFfeRJKdWC2yJ4=; b=OoyqtlwFfP8crvweh3I/1BTVzqoGvMzBEdt9m4UxOrhy1w+qWsjkzFZDZ+RvT32e2U 1Fl5lN7zNqX/zubnHgtiHqmwoU0MO3vm+hUYO5GZkCfxFpvoOsW9YEwSVU/KFvQIk6BH NUG6MxKayWbAWiNS/jZFI18SH8lAqprEUmGzE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=p9IcS+97du3t5jSrSMZ38D3WN1G335agiW5KaRxL2PNDMZYR6svVqCCa7xt177x1Cd HOiTE8TT8lO+Ek6IuFm1Z4cvbXn2Qc7XDMLikBIiln6NMYKMub7guEsEcCkHw3Wuw8aB aOtBckYSuo5Ofvpo3q0uRSuTZzW4oQQ7m8MKo=
2009/7/25 Geoffrey Cowling <geoffrey.cowling@xxxxxxxxx>:
> 2. I made a new directory and mounted the / partition on it.
> (Accessing /etc meant that I could read fstab).
>
> 3. I mounted the other partitions to the directories under / (I
> realise now that vmlinuz was probably broken linked on / becaause
> /boot was not mounted. Derr!
>
> 4. I chrooted into the new /
>
> 5. It seemed to be possible to fix a kernel without destroying
> everything else. This was my BIG question ... I was even tempted to
> use the chroot as a sort of virtual machine. But was a little
> cautious about repeating disaster. In the meantime I had to press on
> with my tasks using an underpowered and less memory/hard disk machine
> (though using Ubuntu 8.10) I had no problems with complex convert
> scripts, with no memory or hard disk problems. So this does not seem
> to have caused my original failure.
>
> 6. There was a suggestion about using apt-get "reinstall kernel", but
> htis seems to be a wish rather than an option. Right? But doing an
aptitude has a "reinstall" option, and besides is more powerful. It
also has full command line interface like apt-get so no down side for
switching to it.
> apt-get update/upgrade got me a new ? security upgrade, which was
> great. Installing the current kernel did not seem to work, but perhaps
> it did occur, but grub problem stopped booting)
>
> 7. I tried update-grub next. This said it could not find the root,
> corrupted fstab? trying hda1. Which was no use!
That possibly happened because the chroot'ed environment didn't have
access to /dev, /sys and /proc, what you need to do AFTER mounting the
root partition and BEFORE the chroot is:
# for i in sys proc dev; do mount -o bind /$i /root/$i; done
(assuming your going-to-be-chrooted root partition is mounted under /root)
I'm not sure this is the reason but it's a good thing to do when
dealing with kernel installation inside chroot in any case - mkinitrd
needs this for instance if you install new kernel modules.
(rest deleted).
In all your post I couldn't find the string "fsck" - have you tried to
force-check the suspected partitions?
Cheers,
--Amos
SLUG Mailing List Archives