Re: [gentoo-user] Problem with new install

[Mike Diehl <mdiehl@diehlnet.com>]

One more interesting tidbit:

When it boots, I can see that VFS was able to mount ROOT on device 8:3.

So, it doesn't seem to be hardware or driver related.  Looks like something 
with the filesystem?  fsck.ext2 is the only thing complaining.  However, when 
I boot from CD, I can mount it just fine.

Anyone seen this before?

Mike.

On Friday 15 October 2010 11:40:34 am Florian Philipp wrote:
> Am 15.10.2010 19:29, schrieb Mike Diehl:
> > Hi all.
> > 
> > I've never had this much trouble with a server before, but I've been
> > pulling my hair out.
> > 
> > The install seemed to go well, but when I rebooted it from it's own hard
> > drive, it fails.  fsck claims that it can't open /dev/sda3 or that the
> > superblock doesn't describe a valid ext2 filesystem.
> > 
> > However, when I reboot from the live CD, it mounts just fine and fsck
> > says it's clean.
> > 
> > Here is the /etc/fstab:
> > /dev/sda1       /boot           ext2            noauto,noatime  1 2
> > /dev/sda3       /               ext2            noatime         0 1
> > /dev/sda2       none            swap            sw              0 0
> > /dev/cdrom              /mnt/cdrom      auto            noauto,ro       0
> > 0 shm                     /dev/shm        tmpfs   nodev,nosuid,noexec   
> >  0 0
> > 
> > Here is the /boot/grub/grub.conf file:
> > default 0
> > timeout 30
> > splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> > 
> > title Gentoo Linux
> > root (hd0,0)
> > kernel /bzImage root=/dev/sda3
> > 
> > I've verified that ext2 and ext3 are in the kernel statically.  I've also
> > compiled in ALL of the SATA drivers, statically.
> > 
> > What am I missing?
> 
> *All* of the drivers could be too much. There is a generic driver which
> can prevent the "right" driver from taking over. In that case you end up
> with a /dev/hda node and no DMA. Try to deactivate "Generic ATA support"
> = CONFIG_ATA_GENERIC and "generic/default IDE chipset support" =
> CONFIG_IDE_GENERIC.
> 
> I think it is the second option that causes that problem. However, you
> won't need the first option, either.
> 
> Instead of your brute-force "yes to all" approach, newer kernels also
> support `make localyesconfig` which takes all modules currently used in
> the running kernel and compiles them into the new kernel. It is very
> helpful when you already have a good but generic kernel like the one on
> your live CD.
> 
> If even that doesn't help, it might be possible that the device
> numbering has changed and your hard disk is detected as /dev/sdb or so.
> Try mounting it by UUID (google for it, please).
> 
> Hope this helps,
> Florian Philipp

-- 

Take care and have fun,
Mike Diehl.