[sf-lug] Hayes Valley Mystery
tom at greenleaftech.net
Fri Apr 18 00:27:46 PDT 2008
On Thu, 2008-04-17 at 23:56 -0700, Asheesh Laroia wrote:
> 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).
Yeah, gives the same output:
e2fsck 1.40-WIP (14-Nov-2006)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda1: 39/26104 files (28.2% non-contiguous), 62530/104388 blocks
It did this before without the -f option. And I'm able to mount it fine
once the system's booted, which we were before as well. The real test
is, can we uncomment the entry in /etc/fstab and have it mounted on
boot? Will have to wait til one of of is onsite and able to deal with
any issues that come up if it doesn't boot correctly before we can check
> -- Asheesh.
> The clash of ideas is the sound of freedom.
More information about the sf-lug