1 |
One more interesting tidbit: |
2 |
|
3 |
When it boots, I can see that VFS was able to mount ROOT on device 8:3. |
4 |
|
5 |
So, it doesn't seem to be hardware or driver related. Looks like something |
6 |
with the filesystem? fsck.ext2 is the only thing complaining. However, when |
7 |
I boot from CD, I can mount it just fine. |
8 |
|
9 |
Anyone seen this before? |
10 |
|
11 |
Mike. |
12 |
|
13 |
On Friday 15 October 2010 11:40:34 am Florian Philipp wrote: |
14 |
> Am 15.10.2010 19:29, schrieb Mike Diehl: |
15 |
> > Hi all. |
16 |
> > |
17 |
> > I've never had this much trouble with a server before, but I've been |
18 |
> > pulling my hair out. |
19 |
> > |
20 |
> > The install seemed to go well, but when I rebooted it from it's own hard |
21 |
> > drive, it fails. fsck claims that it can't open /dev/sda3 or that the |
22 |
> > superblock doesn't describe a valid ext2 filesystem. |
23 |
> > |
24 |
> > However, when I reboot from the live CD, it mounts just fine and fsck |
25 |
> > says it's clean. |
26 |
> > |
27 |
> > Here is the /etc/fstab: |
28 |
> > /dev/sda1 /boot ext2 noauto,noatime 1 2 |
29 |
> > /dev/sda3 / ext2 noatime 0 1 |
30 |
> > /dev/sda2 none swap sw 0 0 |
31 |
> > /dev/cdrom /mnt/cdrom auto noauto,ro 0 |
32 |
> > 0 shm /dev/shm tmpfs nodev,nosuid,noexec |
33 |
> > 0 0 |
34 |
> > |
35 |
> > Here is the /boot/grub/grub.conf file: |
36 |
> > default 0 |
37 |
> > timeout 30 |
38 |
> > splashimage=(hd0,0)/boot/grub/splash.xpm.gz |
39 |
> > |
40 |
> > title Gentoo Linux |
41 |
> > root (hd0,0) |
42 |
> > kernel /bzImage root=/dev/sda3 |
43 |
> > |
44 |
> > I've verified that ext2 and ext3 are in the kernel statically. I've also |
45 |
> > compiled in ALL of the SATA drivers, statically. |
46 |
> > |
47 |
> > What am I missing? |
48 |
> |
49 |
> *All* of the drivers could be too much. There is a generic driver which |
50 |
> can prevent the "right" driver from taking over. In that case you end up |
51 |
> with a /dev/hda node and no DMA. Try to deactivate "Generic ATA support" |
52 |
> = CONFIG_ATA_GENERIC and "generic/default IDE chipset support" = |
53 |
> CONFIG_IDE_GENERIC. |
54 |
> |
55 |
> I think it is the second option that causes that problem. However, you |
56 |
> won't need the first option, either. |
57 |
> |
58 |
> Instead of your brute-force "yes to all" approach, newer kernels also |
59 |
> support `make localyesconfig` which takes all modules currently used in |
60 |
> the running kernel and compiles them into the new kernel. It is very |
61 |
> helpful when you already have a good but generic kernel like the one on |
62 |
> your live CD. |
63 |
> |
64 |
> If even that doesn't help, it might be possible that the device |
65 |
> numbering has changed and your hard disk is detected as /dev/sdb or so. |
66 |
> Try mounting it by UUID (google for it, please). |
67 |
> |
68 |
> Hope this helps, |
69 |
> Florian Philipp |
70 |
|
71 |
-- |
72 |
|
73 |
Take care and have fun, |
74 |
Mike Diehl. |