Kernel panic: No init found 1728

Erm... I... don't think that's how most distributions work. In order to mount on a directory in the root filesystem, the root filesystem would need to be itself mounted.

And if the initrd contains the filesystem and SATA-SCSI drivers required to read the disk and the filesystem it WOULD fail.

The initrd is usually mounted AS the root filesystem. This allows the kernel to load the drivers required to mount thr REAL hard disks and then switch over to the REAL root filesystem and pbutt control to the REALsbin-init.

When building the image, that can be done without a specific initrd directory too, by simply creating a blank filesystem image, formatting it, mounting it and copying the required files into it.

no no no... The initrd-initramfs DIRECTORIES are NOT required. My suse system here uses initrd and has no directories by those names. It's not how the boot process works.

The fact he's loading an initrd file at bootup implies he doesn't have all the required drivers. Hell, the initrd process shown by the boot messages show he's loading the ext3 module.

Not mine, it treats other ones as *bold* and underline by giving them other colours, but I've not configured italic.

So you meant to say it in italic rather than talk aboutdirectories?

HINT, use underline or *bold* to highlight. cos is a BAD character to use when discussing linux systems considering it's a fecking directory identifier.

If you didn't MEAN to italise the text then my thing about the initrd directory stands. -- Andrew Halliwell BSc(hons) I can SMELL!!! KRYTEN!!! Unpack Rachel and in get out the puncture repair kit!" Computer Science Arnold Judas Rimmer- Red Dwarf ------------------------------------------------------------------------------