Messages in this thread | | | Subject | Re: 2.6.13-rc2 (git followed) unable to boot with initrd | From | Bas Vermeulen <> | Date | Tue, 12 Jul 2005 11:03:12 +0200 |
| |
On Tue, 2005-07-12 at 01:25 -0700, Andrew Morton wrote: > Bas Vermeulen <bvermeul@blackstar.nl> wrote: > > > > I am currently unable to boot 2.6.13-rc2. I've got a working 2.6.13-rc1 > > whose .config I use to compile 2.6.13-rc2. I'm attaching the failed boot > > log to this message. I'm booting with the same options as 2.6.13-rc1. > > > > If anyone knows how to get it working again, I'd be grateful. > > ... > > VFS: Cannot open root device "LABEL=/" or unknown-block(0,0) > > ... > > This normally has a simple cause: it didn't find any disks, or a filesystem > driver is missing. Check your .config carefully and if that seems OK, > generate the -rc1 and -rc2 dmesg and diff them, send us the result.
The .config between -rc1 and -rc2 are the same (I always keep the same .config). It found the disks in -rc2 (sda - ata_piix driver), but can't find "LABEL=/" because that's what the initrd is supposed to mount. I've tried mounting /dev/sda6 (which is my root) directly, but that doesn't help either.
I'll generate the diff for you in a bit.
-- Bas Vermeulen <bvermeul@blackstar.nl>
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |