[sf-lug] Hayes Valley Mystery
asheesh at asheesh.org
Thu Apr 17 23:56:36 PDT 2008
On Thu, 17 Apr 2008, Tom Haddon wrote:
> On Thu, 2008-04-17 at 23:38 -0700, Asheesh Laroia wrote:
>> On Wed, 16 Apr 2008, Tom Haddon wrote:
>>> So the questions here are:
>>> • How did the system boot from a device that it failed to mount (we know
>>> it was booting from /dev/sda1 because the changes we'd made
>>> to /boot/grub/menu.lst when we manually mounted /dev/sda1 before
>>> rebooting were applied)?
>> Sounds like it worked because GRUB's ext2/ext3 driver could read it; Linux
>> never had to, for it to boot.
> Aha, yeah, that makes sense.
>>> • How can we mount a partition if it's failing to be mounted as part of
>>> the boot sequence?
>> Well, sounds like you should fsck and then see if it mounts.
> Well it mounts fine. And an fsck produced no problems. Do you know what
> command options would do an "exhaustive" check, as I just did fsck with
> no options.
e2fsck -f "force[s] checking even if the file system seems clean", at
least (says its man page).
The clash of ideas is the sound of freedom.
More information about the sf-lug