Apparently, though unproven, at 19:36 on Thursday 04 November 2010, dhk did opine thusly:
> On 11/04/2010 01:08 PM, Neil Bothwick wrote: > > On Thu, 04 Nov 2010 13:00:21 -0400, dhk wrote: > >> The reason I didn't include the exact error is that I can't capture it. > >> > >> I'd have to write it on paper and then reboot to the working kernel. > > > > Which is a lot less work than trying to fix the problem by guesswork. > > I have /boot as ext2 and the rest ext3 with lvm2. > > $ df -k > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/hda3 8262068 712028 7130344 10% / > udev 10240 336 9904 4% /dev > /dev/mapper/vg-usr 15481840 12867912 1827496 88% /usr > /dev/mapper/vg-home 51606140 42781428 6203272 88% /home > /dev/mapper/vg-opt 5160576 2635064 2263368 54% /opt > /dev/mapper/vg-var 15481840 2387500 12307908 17% /var > /dev/mapper/vg-tmp 2064208 68708 1890644 4% /tmp > shm 512572 0 512572 0% /dev/shm > > The ext2 wasn't compiled in, so I compiled it in and rebooted. I got > the same error. > > "kernel panic - not syncing : VFS: unable to mount root FS on > unknown-block (2,0)" > > This is what I had. > < > Second extended fs support │ │ > │ │ <*> Ext3 journalling file system support > │ │ > │ │ [ ] Default to 'data=ordered' in ext3 > │ │ > │ │ [*] Ext3 extended attributes > │ │ > │ │ [*] Ext3 POSIX Access Control Lists > │ │ > │ │ [*] Ext3 Security Labels > > This is what I added. > <*> Second extended fs support │ │ > │ │ [ ] Ext2 extended attributes (NEW) > │ │ > │ │ [ ] Ext2 execute in place support (NEW) > │ │ > │ │ <*> Ext3 journalling file system support > │ │ > │ │ [ ] Default to 'data=ordered' in ext3 > │ │ > │ │ [*] Ext3 extended attributes > │ │ > │ │ [*] Ext3 POSIX Access Control Lists > │ │ > │ │ [*] Ext3 Security Labels > │ │ > > Thanks, > > --dhk Is your / partition in or out of the lvm? -- alan dot mckinnon at gmail dot com
