Mailinglist Archive: opensuse (4547 mails)

< Previous Next >
Re: [SLE] cannot open root device
  • From: John Wilkes <john@xxxxxxxxxx>
  • Date: Sun, 2 May 2004 22:15:22 -0700 (PDT)
  • Message-id: <Pine.LNX.4.33.0405022209170.1672-100000@xxxxxxxxxxxxxxxx>
The "failsafe" boot uses "kernel.shipped" and "initrd.shipped" on my
system. This is how the standard SuSE 8.2 installation set up grub's
menu.lst file.

I re-installed the kernel off of the distribution CDs, which gets me a
new initrd. No difference. Still complains that it can't open the
root device.

I'm thinking about backing up the partition and nuking it with
mkreiserfs, then restoring its contents. Is tar suitable for this
purpose? I've heard in the past that tar is not good for backups of
this sort.

Thanks for the suggestions.

--
John Wilkes
john at wilkes dot com

On Fri, 30 Apr 2004, Anders Johansson wrote:

> On Thursday 29 April 2004 17.16, John Wilkes wrote:
> > Based on what I've found with Google, it's acting like the kernel does
> > not have reiserfs support, but I don't think that's the case either
> > because the "failsafe" boot, which boots the distributed kernel using
> > the distributed initrd, exhibits the same problem.
>
> Not sure what you mean here, but by default, 'failsafe' boots exactly the same
> kernel, with exactly the same initrd as the default, only with a few
> parameters that make it more likely to boot properly in situations where for
> example acpi makes it fail
>
> Are you absolutely certain you haven't had a recent kernel update? There has
> been some kernel bugs lately. Try creating a new initrd, just for the hell of
> it and see what happens
>
>
>


< Previous Next >
Follow Ups