On Tue, 9 Jan 2001, David Cantrell wrote:
> > > ufs_read_super: bad magic number
> > >
> > > Kernel Panic: VFS: Unable to mount root fs on 01:00
> > > Press L1-A to return to the boot prom
> >
> > that the initrd isn't being recognized at all, and mounting an empty
> > ramdisk is being attempted?
> >
> > I dunno. But, at least I'm not crazy ;)
>
> Argh... back to the drawing board. I simply don't understand why this is
> happening. The color.gz and serial.gz root images are 5MB compressed ext2
> filesystems. I will look through everything and try to figure out what's
> up. Both of you are having this happen on SPARCstation 10 systems, right?
For me, it happens on a ss5, ss4, ss10, and ss20. :(
Netbooting works fine, but booting the cdrom no workie.
Since a)there's newer images since the last time I tried, and b)I now
have at least one successfully installed system (an ss5, got a kernel
netbooted, then plopped the CD into a local drive 'cuz the netbooted
kernel didn't have lance support built in... doh) to compare against,
I'll try again soon and dig through source to diagnose.
Is there a chance that there's a cdrom-drive incompatability? Old UNIX
hardware was all kinds of picky about what CDROM drives they'd boot from
(in fairness, at least they *could* boot from CD before the late 90's...
:) I'd been assuming that if the PROM was able to load SILO and the
kernel from CD, then that was it, things were successful. But is there
a chance of some odd block-boundary nonsense causing the initrd loading
to fail even after the kernel has been successfully loaded?
Grasp for straws much...?
Hank
This archive was generated by hypermail 2b30 : Thu Sep 19 2002 - 11:00:02 PDT