Problems Booting 2005.1 Live CD

[ba6351]

I have installed 2005.0 on my Beige Power Mac G3 with little issue, and have decided to start from scratch again and install 2005.1. When I follow the install guide to try to start up from the cdrom, I found that the G3G4 kernel and G3G4.igz files are nonexistent. However i did find ppc32 and ppc32.igz on the disc which I attempted to use with BootX 1.2.2. After putting in all the kernel arguments that the install guide mentioned,

cdroot root=/dev/ram0 init=linuxrc loop=livecd.squashfs looptype=squashfs console=tty0 nodevfs udev

I ensured the correct ramdisk size and file was selected and it did start to boot, however, it halted with a problem attempting to mount and/or connect to the root partition. Like I said, I have already tried to install 2005.0 with little issue, and have had the same problem when trying to reinstall 2005.0 while following the install guide for it.

Any thoughts or hints are much appreciated.

Thanks

ba6351

[dgooding]

I'm having the exact same problem. 2005.1 with no G3G4 kernel. Used ppc32 instead and the reboot freezes looking for the root partition.

I'll try a 2005.0 disc to see if I can at least get the install started.

[ba6351]

That may work. I initially installed 2005.0 and it worked fine, but I remember the kernel args being different from what they are in the documentation when I tried to reinstall 2005.0 after trying 2005.1

[dgooding]

FYI, I have a PowerMacintosh 7600/132 with a G4 daughterboard. Not sure what the other specs are.

Alright, I tried the ppc32/ppc32.igz combo from 2005.1 LiveCD and got these errors when booting from BootX using the kernel options suggested in the Handbook:

Code: Select all

>> Mounting tmpfs for /newroot
>> No bootable medium found.  Waiting for new devices...
Could not find CD to boot, something else needed!
Determining root device...
The root block device is unspecified or not detected.

I'm then prompted to choose a different root device or go into a 'shell'.

Trying the G3G4/G3G4.igz combo from the 2005.0 LiveCD gave me these errors when booting from BootX using the same kernel options:

Code: Select all

>> Mounting filesystems
mount: Mounding devfs on /newroot/dev/failed: No such device
Error opening file: ".devfsd" No such file or directory
>> Attempting to mount CD:- /newroot/dev/cdroms/*
>> Attempting to mount CD:- /newroot/dev/ide/cd/*
>> Attempting to mount CD:- /newroot/dev/sr0
>> Attempting to mount CD:- /newroot/dev/sd*
>> No bootable medium found.  Waiting for new devices...
>> Attempting to mount CD:- /newroot/dev/cdroms/*
>> Attempting to mount CD:- /newroot/dev/ide/cd/*
>> Attempting to mount CD:- /newroot/dev/sr0
>> Attempting to mount CD:- /newroot/dev/sd*
Could not fine CD to boot, something else needed!
... some other stuff ...
The root block device is unspecified or not detected.

This was followed by the same prompt for another root device or 'shell'.

I then tried the kernel JoseJX keeps suggesting (OW-Kernel - http://dev.gentoo.org/~josejx/OW-Kernel.bz2). I downloaded it and unbzipped it. I placed it in the Linux Kernels folder on the mac and used an OW-Kernel/G3G4.igz combo. I booted from BootX using the same kernel options and got the same error as with the G3G4/G3G4.igz combo.

Is there any other information I can provide that will aid in helping me? I thought maybe the SCSI ID of the harddrive/cdrom might come into play. I think I remember seeing that my HD was SCSI-ID 3 and my CD was SCSI-ID 2? If that's a possible problem, I can double check the actual numbers...

Any ideas?

[Hyp]

Hi,

I've got the same problem, although on an ordinary x86 PC

Could you go into the shell and look ("ls -l") if linuxrc exists resp. to what target it points to and if this target exists.

Hyp

[dgooding]

Well, before I do that, I'd like to mention that I tried the OW-Kernel/ppc32.igz combo and got a different error. It did find the CD:

Code: Select all

>> Making tmpfs for /newroot
>> Attempting to mount CD:- /dev/sr0
>> CD medium found on /dev/sr0
>> Determining root device...
>> Determining looptype...
!! Invalid loop location:
!! Please export LOOP with a valid location or reboot and pass proper loop= ...
!! kernel command line!

This was followed by a prompt. An 'ls' in /mnt gave me three folders 'cdrom', 'gentoo' and 'livecd'. The 'cdrom' folder pointed to the CD in the tray, while the others were empty.

I'm using the same kernel arguments that the Handbook suggests:

Code: Select all

cdroot root=/dev/ram0 init=linuxrc loop=livecd.squashfs looptype=squashfs console=tty0 nodevfs udev

Should it be different?

Hey JoseJX, care to comment?

[Hyp]

Code: Select all

cdroot root=/dev/ram0 init=linuxrc loop=livecd.squashfs looptype=squashfs console=tty0 nodevfs udev

Shouldn't it be

Code: Select all

cdroot root=/dev/ram0 init=/linuxrc loop=/livecd.squashfs looptype=squashfs console=tty0 nodevfs udev

?

Hyp

[dgooding]

Oddly enough, I tried with the leading slashes too and I get the same error.

And the Handbook doesn't say to use the slashes, anyway.

[Hyp]

Hi,

Seems like it's a greater bug and doesn't depend on the own hardware configuration.
I spent the whole last day trying to figure out what I did wrong (I followed this HowTo).
But I always ended up with the same error as dgooding:

Code: Select all

>> Mounting tmpfs for /newroot
>> No bootable medium found.  Waiting for new devices...
Could not find CD to boot, something else needed!
Determining root device...
The root block device is unspecified or not detected. 

Hyp

[JoseJX]

I've just moved and I'm waiting for my OW machine to be shipped to my new location. As soon as it gets here, I'll figure out what's going wrong. Sorry about this. The OW kernel that I provided before is for 2005.0 only, but try removing the nodevfs udev kernel parameters (for 2005.0 only, 2005.1 doesn't come with devfs) and see if that helps.

[dgooding]

I removed the nodevfs and udev arguments while using the OW-Kernel/ppc32.igz combo and I got the same error as with them still there.

// I just realized I completely stole this thread from ba6351. My apologies, though I think we're after the same thing.

[JoseJX]

Sorry that wasn't clear. I suggested to use the G3G4 initrd with either the G3G4 kernel or the OW-Kernel, not the one from the 2005.1 release. As I said before, the 2005.1 release does not come with devfs, and as such, those kernel options do nothing.

[dgooding]

use the G3G4 initrd

What do you mean by that? The Handbook says to copy the kernel image (G3G4/ppc32) and the IGZ file (G3G4.igz/ppc32.igz) to the System Folder in a new folder named Linux Kernels. Following this, using BootX, I am to select the kernel from the dropdown, and choose the IGZ as the ramdisk. The Handbook never mentions initrd. Is the G3G4.igz ramdisk what you mean by "use the G3G4 initrd"??

If that's the case, I used the OW-Kernel/G3G4.igz combo with the 2005.0 LiveCD and the two kernel arguments taken out and the same (G3G4) error occurs.

I assume it's right to use the LiveCD corresponding to which IGZ you're using (2005.0 for G3G4.igz and 2005.1 for ppc32.igz)?

I'm apologize for my ignorance, but I've been spoiled by the "boot from CD" x86 world. PPC (at least OW) is very foreign to me. I'll be glad to try anything or provide any information that would help. I know my way around Gentoo, I've been using it for over a year on more than 6 machines.

[JoseJX]

Old World is a pain, New World machines do boot from CD easily. Anyway, yes, the igz is just a compressed initrd. You had specifed that you used the OW/ppc32.igz combo which will not work, as the kernel version is different between releases.

For those whose machines can't find the cdroot, when MESH initializes does it find you CD drive? Do you have it attached to a different controller?

I'm not sure why 2005.0 isn't working, with the OW kernel, that always booted for me.

[dgooding]

I'll be glad to supply the output of dmesg for you, but I simply don't know how to get it off the machine. Is there a way?

Here's what happens when I boot from OW/G3G4 without the devfs kernel arguments.

Code: Select all

mesh : performing initial bus reset...
scsi0 : MESH
elevator: using deadline as default io scheduler
mesh: targe 2 synchronous at 5.0 MB/s
  Vendor: IBM         Model:  DNES-318350        Rev: SA30
  Type:   Direct Access                          ANSI SCSI revision: 03
mesh: target 3 synchonous at 5.0 MB/s
  Vendor: MATSHITA    Model:  CD-ROM CR-8008     Rev: 8.0h
  Type:   CD-ROM                                 ANSI SCSI revision: 02
SCSI device sda: 35843670 512-byte hdwr sectors (18352 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 35843670 512-byte hdwr sectors (18352 MB)
SCSI device sda: drive cache: write back
  sda: [mac] sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
Attached scsi disk sda at scsi0, channel 0, id 2, lun 0
sr0: scsi-1 drive
Uniform CD-ROM driver Revision: 3.20
Attached scsi generic sg0 at scsi0, channel 0, id 2, lun 0, type 0
Attached scsi generic sg1 at scsi0, channel 0, id 3, lun 0, type 5

[dgooding]

JoseJX, anyone... Any ideas?

I've been volunteering in Mississippi because of Katrina (and then was fleeing Rita) for the past two weeks. I haven't had any time to mess with the PPC. Everything seems to be coming back together now, but I still can't get my machine to boot off a Gentoo CD (2005.0 or 2005.1).

[JoseJX]

My OW PPC should be here by this weekend, I'll get a chance then to look it over.

[Siftah]

Just about to download 2005.1 and do a fresh install (b0rked update from 2004.3 profile to 2005.* and I want to swap to RAID5'd drives)

Came across this thread and looked back at my old notes, I've always used:

Code: Select all

root=/dev/ram0 rw init="/linuxrc" looptype=gcloop cdroot

And it's worked for me - perhaps the "rw" and the "cdroot" bits will help?

[alien_ghost]

I have a beige g3, rev c, and using the 2005.1 image i have not been able to install linux on it.
I have tried both set of kernel flags, to no avail.
i managed to get somewhat farther with the codes Siftah provided, by that i mean i've gone passed the loop bit

Code: Select all

>> Making tmpfs for /newroot
>> Attempting to mount CD:- /dev/sr0
>> CD medium found on /dev/sr0
>> Determining root device...
>> Determining looptype...
!! Invalid loop location:
!! Please export LOOP with a valid location or reboot and pass proper loop= ...
!! kernel command line!

however it's not saying it can't find a cdupdate.sh file or something, and can't create some directories.

As i'm new to putting linux on my beige g3 (mklinux works perfect on 7100/66), i would really apreciate some help.
many many thanks

[dgooding]

I tried using the kernel options that Siftah used but I couldn't get anything different.

alient_ghost: What exactly did you do to get past the "invalid loop location" error? What disc/kernel/igz combination and what kernel options?

JoseJX: Got your OW setup? I'm not trying to nag, but it seems as though you're our only hope...

[JoseJX]

No worries about the nagging, but I was getting around to it... ;)

Alright, I've gotten my OW Mac setup first, the specs. I've got a PowerMac 8500/180 w/64MB of Ram, SCSI CD and 2 2GB SCSI HDs. I've also just today recieved a dual 225MHz CPU card for this machine (thanks rajiv!).

The 2005.0 install CD boots perfectly fine on either CPU card with the parameters that are given in the handbook for 2005.0. All I did was copy the G3G4 kernel and the G3G4.igz, put in the parameters and it booted as expected.

The 2005.1 install CD does boot, but doesn't really work since the scsi modules are not detected on startup. I'll make a new OW kernel to address this.

What bus is your CD device attached to? Try adding doscsi to the kernel parameters if it's not the internal scsi but an external one instead. If you have a piece of hardware that isn't in our kernel, I'll make a new one for you.

[skunkworx]

Hello!

I am also unable to boot the 2005.1 PPC minimal CD on my OldWord Mac. This is a Beige G3 tower, with no SCSI peripherals attached; the hard drive and the CD-ROM are both IDE. I've tried upping the ramdisk size, and specifying /dev/ram0 explicitly as the root device, but haven't had any luck. The CD-ROM is recognized during boot, assigned /dev/hdc. Let me know if I can provide any additional info.

[JoseJX]

What kind of error are you getting? Have you tried 2005.0?

[skunkworx]

What kind of error are you getting?

The same error the original poster is getting, where it says the "root block device is unspecified or not detected."

Have you tried 2005.0?

I just did, and it gives me a different error. I see this:

Code: Select all

/linuxrc has to be run as the init process as the one
with a PID of 1.  Try adding init="/linuxrc" to the
kernel command line or running "exec /linuxrc"
  XFS: bad magic number
  XFS: SB validate failed
Kernel panic: not syncing: VFS: Unable to mount root fs on unknown-block(3,7)

Adding that init line didn't help.

[Sword_Mas]

Hello gentlemen.
I am trying to install Gentoo on a PowerMac 9600, but have run into some problems and haven't been able to troubleshoot it away.
I'm using BootX in Mac OS 9.1, hopefully that's not the problem (a friend of mine told me that BootX wouldn't boot correctly in Mac OS >= 9.1, but I don't believe him).
I've tried with both the 2005.1 and 2005.0, and I'm using the specified kernel arguments in the coresponding handbook, and always with a ramdisksize >= 32000 and here is what I've found out so far:

2005.0/G3G4/G3G4.igz
Hangs at:

Code: Select all

Serial: 8250/16550 driver $ Revision: 1.90 $ 6 ports IRQ sharing disabled

If I cross off "No video driver" in BootX it would freeze with only Tux visible in an "ocean of black". (For further notice, normally the background would be blue and Tux kinda bluish inverted, but with "No video driver" the colorset would be correct - but would freeze with only Tux surrounded by black.)

Well, since I've read the posts regarding freezes with OWhardware and the G3G4kernel, I tried with the new OW-Kernel.

2005.0/OW-Kernel/G3G4.igz

Code: Select all

>> Mounting filesystems
mount: Mounting devfs on /newroot/dev failed: No such device
Error opening file: ".devfsd"   No such file or directory
>> Attempting to mount CD:- /newroot/dev/cdroms/*
>> Attempting to mount CD:- /newroot/dev/ide/cd/*
>> Attempting to mount CD:- /newroot/dev/sr0
>> Attempting to mount CD:- /newroot/dev/sd*
>> No bootable medium found.  Waiting for new devices...
>> Attempting to mount CD:- /newroot/dev/cdroms/*
>> Attempting to mount CD:- /newroot/dev/ide/cd/*
>> Attempting to mount CD:- /newroot/dev/sr0
>> Attempting to mount CD:- /newroot/dev/sd*
Could not find CD to boot, something else needed!
... x2 ...
... some stuff about virtual groups ...
Determining root device...
The root block device is unspecified or not detected.
...
boot() ::

First try: boot() :: /dev/ram0

Code: Select all

>> Mounting root...
>> Booting.umount: Cannot open /proc/mounts
mount: invalid option -- -
mount: invalid option -- m
mount: /proc/filesystems: No such file or directory
*: Failed to move over the /dev tree!
/linuxrc: 504: cannot open /dev/console: No such file
Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 180 seconds

Second try: boot() :: shell

Code: Select all

/ # mount
/dev/ram0 on / type ext2 (rw)
/proc on /proc type proc (rw,nodiratime)

Since init didn't manage to mount a dev filesystem on newroot, I thought maybe I should fix it somehow ...

Code: Select all

/ # cp -R /dev /newroot/dev
cp: unable to create `...`: No space left on device
...

Hm... No space left on device... Okey, maybe that's what it meant with "mount: Mounting devfs on /newroot/dev failed: No such device" - but, which device is it really meaning?

Well, I finally got around to write down the kernel messages for 2005.0 (if anybody's interested):

Code: Select all

/ # more /proc/kmsg
<4>mem_pieces_remove: [48b000,5d9b37) not in any region
<4>Total memory = 160MB; using 512kB for hash table (at c0600000)
<4>Linux version 2.6.10-gentoo-r8-G3G4 (root@powerbook) (gcc version 3.4.3-20050110) (Gentoo Linux 3.4.3.20050110-r2, ssp-3.4.3.20050110-0, pie-8.7.7)) #3 SMP Tue Apr 26 21:18:00 EDT 2005
<6>Found a Grand Central mac-io controller, rev: 2, mapped at 0xfdc7f000
<6>PowerMac motherboard: PowerMac 9500/9600
<6>Cache coherency enabled for bandit/PSX
<6>Found Bandit PCI host bridge at 0xf2000000. Firmware bus number: 0->0
<6>Cache coherency enabled for bandit/PSX
<6>Found Bandit PCI host bridge at 0xf4000000. Firmware bus number: 1->2
<4>nvram: OF partition at 0x1800
<4>nvram: XP partition at 0x1300
<4>nvram: NR partition at 0x1400
<7>On node 0 totalpages: 40960
<7>  DMA zone: 40960 pages, LIFO batch:10
<7>  Normal zone: 0 pages, LIFO batch:1
<7>  HighMem zone: 0 pages, LIFO batch:1
<4>Built 1 zonelists
<4>Kernel command line: ramdisk_size=64000 rw init=/linuxrc cdroot
<4>System has 32 possible interrupts
<4>PID hash table entries: 1024 (order: 10, 16384 bytes)
<4>GMT Delta read from XPRAM: 120 minutes, DST: on
<6>via_calibrate_decr: ticks per jiffy = 25000 (1500024 ticks)
<4>Console: colour dummy device 80x25
<4>Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
<4>Inode-cache hash table entries: 16385 (order: 4, 65536 bytes)
<4>Memory: 155520k available (3160k kernel code, 1296k data, 212k init, 0k highmem)
<7>Calibrating delay loop... 299.0 BogoMIPS (lpj=149504)
<4>Mount-cache hash table entries: (order: 0, 4096 bytes)
<4>Brought up 1 CPUs
<7>CPU0:
<7> domain 0: span 1
<7>  groups: 1
<6>checking if image is initramfs... it isn't (no cpio magic): looks like an initrd
<4>Freeing inird memory: 1338k freed
<6>NET: Registered protocol family 16
<6>PCI: Probing PCI hardware
<4>PCI: Enabling device 0001:02:04.0 (0116 -> 0117)
<4>PCI: Enabling device 0001:02:05.0 (0116 -> 0117)
<7>Registering pmac pic with sysfs
<5>SCSI subsystem initialized
<6>usbcore: registered new driver usbfs
<6>usbcore: registered new driver hub
<4>Thermal assist unit not available
<6>Squashfs 2.1 (released 2004/12/10) (C) 2002-2004 Phillip Lougher
<6>SGI XFS with ACLs, security attributes, large block numbers, no debug enabled
<6>SGI XFS Quota Management subsystem
<6>Initializing Cryptographic API
<6>Generic RTC Driver v1.07
<6>Macintosh non-volatile memory driver v1.1
<4>kobject_register failed for radeonfb (-17)
<4>Call trace:
<4> [c019a650] kobject_register+0x60/0x78
<4> [c0214fc4] bus_add_driver+0x78/0x184
<4> [c02156f4] driver_register+0x38/0x48
<4> [c01a5eb8] pci_register_driver+0x78/0xcc
<4> [c0416dbc] radeonfb_old_init+0x44/0x54
<4> [c00041b4] init+0x36c/0x534
<4> [c0007140] kernel_thread+0x44/0x60
<6>imsttfb_probe: OF name IMS,tt128mb
<4>Console: switching to colour frame buffer device 160x64
<4>fb0: IMS TT (IBM) frame buffer; 4MB vram; chip version 2
<6>imsttfb_probe: OF name IMS,tt128mb8A
<4>fb1: IMS TT (TVP) frame buffer; 8MB vram; chip version 2
<6>MacOS display is /bandit/IMS,tt128mb
<6>mice: PS/2 mouse device common for all mice
<6>io scheduler noop registered
<6>io scheduler deadline registered
<4>RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
<6>loop: loaded (max 8 devices)
<6>MacIO PCI driver attached to Grand Central chipset
<6>eth0: MACE at 00:05:02:1e:f8:0f, chip revision 25.64
<6>input: Macintosh mouse button emulation
<4>Macintosh CUDA driver v0.5 for Unified ADB.
<6>apm_emu: Requires a machine with a PMU
<6>Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
<6>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
<6>adb: starting probe task...
<6>mesh: configured for synchronous 5 MB/s
<7>adb devices: [2]: 2 5 [3]: 3 1
<4>ADB keyboard at 2, handler set to 3
<6>Detected ADB keyboard, type ISO, swapping keys
<6>input: ADB keyboard on adb22:2.05/input
<4>ADB mouse at 3, handler set to 4
<6>input: ADB mouse on adb3:3.01/input
<6>adb: finished probe task
<6>mesh: performing initial bus reset...
<6>scsi0: MESH
<6>elevator: using deadline as default io scheduler
<6>mesh: target 0 synchronous at 5.0 MB/s
<5>  Vendor: IBM       Model: DCAS-34330        Rev: S65A
<5>  Type:   Direct-Access                      ANSI SCSI revision: 02
<6>mesh: target 3 synchronous at 5.0 MB/s
<5>  Vendor: MATSHITA  Model: CD-ROM CR-8024    Rev: 2.0e
<5>  Type:   CD-ROM                             ANSI SCSI revision: 02
<5>  Vendor: IOMEGA    Model: ZIP 100           Rev: J.03
<5>  Type:   Direct-Access                      ANSI SCSI revision: 02
<5>SCSI device sda: 8467200 512-byte hdwr sectors (4335 MB)
<5>SCSI device sda: drive cache: write back
<5>SCSI device sda: 8467200 512-byte hdwr sectors (4335 MB)
<5>SCSI device sda: drive cache: write back
<6> sda: [mac] sda1 sda2 sda3 sda4 sda5 sda6 sda7
<5>Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
<5>Attached scsi removable disk sdb at scsi0, channel 0, id 5, lun 0
<4>sr0: scsi-1 drive
<6>Uniform CD-ROM driver Revision: 3.20
<7>Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
<5>Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0
<5>Attached scsi generic sg1 at scsi0, channel 0, id 3, lun 0,  type 5
<5>Attached scsi generic sg2 at scsi0, channel 0, id 5, lun 0,  type 0
<7>ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
<6>USB Universal Host Controller Interface driver v2.2
<6>usbcore: registered new driver hiddev
<6>usbcore: registered new driver usbhid
<6>drivers/usb/input/hid-core.c: v2.0:USB HID core driver
<6>i2c /dev entries driver
<6>NET: Registered protocol family 2
<6>IP: routing cache hash tabble of 1024 buckets, 8KBytes
<6>TCP: Hash tables configured (established 16384 bind 16384)
<6>NET: Registered protocol family 1
<6>NET: Registered protocol family 17
<5>RAMDISK: Compressed image found at block 0
<4>EXT2-fs warning: checktime reached, running e2fsck is recommended
<4>VFS: Mounted root (ext2 filesystem).
<4>Freeing unused kernel memory: 212k init 4k chrp 32k prep

2005.1/ppc/ppc.igz

Code: Select all

...
adb: finished probe task
>> Loading modules
>> Activating udev
>> Making tmpfs for /newroot
>> No bootable medium found. Waiting for new devices...
>> Could not find CD to boot, something else needed!
>> Determining root device...
!! the root block device is unspecified or not detected
  Please specify a device to boot, or "shell" for a shell
boot() ::

First try: boot() :: /dev/ram0

Code: Select all

>> Mounting root...
mount: Mounting /dev/ram0 on /newroot failed: Invalid argument
!! Could not mount specified ROOT, try again
!! The root block device is unspecified or not detected
  Please specify a device to boot, or "shell" for a shell
boot() ::

Second try: boot() :: shell

Code: Select all

/ # mount
proc on /proc type proc (rw, nodiratime)
udev on /dev type tmpfs (rw)

I sorry I didn't bother to write down _another_ kernel message, but hey, I'll do it if someone here thinks it will help greatly. ^_^
Anyhow, I did notice some interesting messages there though, here is an extract:

Code: Select all

/ # more /proc/kmsg
...
<6> checking if image is initramfs... it is
...
<3>VFS: Can't find ext3 filesystem on dev ram0
<4>VFS: Can't find an ext2 filesystem on dev ram0
<3>SQUASHFS error: Can't find a SQUASHFS superblock on ram0
<4>Unable to identify CD-ROM format.
<4>XFS: bad magic number
<4>XFS: SB validate failed
... x2 ...

/ # ls /dev/sg0
ls: /dev/sg0: No such file or directory

So... this stirs up quite an amount of questions, doesn't it?
First things first, what device is it looking for here:

Code: Select all

mount: Mounting devfs on /newroot/dev failed: No such device

and is it the reason there's no space left on device?

Code: Select all

cp: unable to create `...`: No space left on device

With the 2005.0combo it manages to mount the initrd,

Code: Select all

/dev/ram0 on / type ext2 (rw)

even though it gives "funny" kernel messages:

Code: Select all

<6>checking if image is initramfs... it isn't (no cpio magic): looks like an initrd

But with the 2005.1combo it won't mount,

Code: Select all

/ # mount
proc on /proc type proc (rw, nodiratime)
udev on /dev type tmpfs (rw)
/ #

even though at first it gives a much more soothing message compared to the 2005.0combo,

Code: Select all

<6> checking if image is initramfs... it is

but then freaks out rendering itself useless, of some sort. ^_^:

Code: Select all

<3>VFS: Can't find ext3 filesystem on dev ram0
<4>VFS: Can't find an ext2 filesystem on dev ram0
<3>SQUASHFS error: Can't find a SQUASHFS superblock on ram0

There... Sorry for hijacking the thread a tad, but I thought it would be alright to gather all the information about this problem at one place.

Thanks in advance.