Date: Mon, 15 Sep 2014 11:31:05 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: Isaac Dunham <ibid.ag@gmail.com>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Re: Cannot mount root filesystem with latest
 vanilla kernel
Message-ID: <20140915113105.182f422b@ncopa-desktop.alpinelinux.org>
In-Reply-To: <20140914210508.GA1775@newbook>
References: <20140914201702.GA513@muslin>
	<20140914210508.GA1775@newbook>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Sun, 14 Sep 2014 14:05:08 -0700
Isaac Dunham <ibid.ag@gmail.com> wrote:

> On Sun, Sep 14, 2014 at 01:17:02PM -0700, Isaac Dunham wrote:
> > Hello,
> > Posting from a different distro, since I can't boot Alpine.
> > 
> > I've got a bit of a problem with the latest linux-vanilla kernel.
> > Yesterday I did an update and upgrade, and today I'm getting an
> > initramfs shell whenever I boot.
> > I have /dev/sda14 as root, formatted as ext2.
> > I can mount it from another distro, as ext2.
> > 
> > When I try mounting /dev/sda14 on /sysroot without specifying fstype,
> > I get this errormessage:
> > mount: cannot mount /dev/sda14 on /sysroot: no such file or directory
> > and there are no new messages in dmesg.
> > 
> > If I specify -t ext2 (or ext3 or ext4), I get 
> > mount: cannot mount /dev/sda14 on /sysroot: no such device
> > and dmesg has a large number of complaints about symbol version mismatches
> > in the filesystem driver (ext2 or ext3 or ext4).
> > 
> > Any ideas how to fix it?
> 
> apk fix linux-vanilla
> solved it.
> 
> No idea what caused this, though.

i think update-extlinux or mkinitfs trigger failed for some reason so
the initramfs image got broken. I have no idea why though.

-nc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---