LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Kernel (https://www.linuxquestions.org/questions/linux-kernel-70/)
-   -   After making initrd.gz, i get UDF-fs: No partition found(1) (https://www.linuxquestions.org/questions/linux-kernel-70/after-making-initrd-gz-i-get-udf-fs-no-partition-found-1-a-937987/)

Semash! 04-03-2012 08:22 PM

After making initrd.gz, i get UDF-fs: No partition found(1)
 
Hello everyone,
I'm having some trouble getting my new compiled kernel to work.

I installed Slackware 13.1 in an ext3 fs, which comes with linux 2.6.33.4, i copied the current kernel .config from /proc/config.gz to /usr/src/linux/.config, then patched the kernel with the respective bootsplash file,and everything went ok (No warnings or errors), later activated the NEW created module and some others by ~#make menuconfig, compiled and after several minutes my kernel's compilation was complete.

Ran:
Code:

root@darkstar~# mkinitrd -c -k 2.6.33.4-custom -r /dev/sda3 -f ext3
Later, updated initrd.gz to implement the bootsplash with the following command:

Code:

root@darkstar~# splash -s -f /etc/bootsplash/themes/slackware/config/backgr...stuff.cfg >> /boot/initrd.gz
updated lilo.conf to:
Code:

image = /boot/vmlinux-custom
initrd = /boot/initrd.gz
root = /dev/sda3
label = Slackware
read-only

Ran lilo, and rebooted.

Bootsplash is working perfectly, but i get Kernel Panic, i don't know why. It shows the following:

Code:

...
md: ... autorun DONE.
RAMDISK: gzip image found at block 0
UDF-fs: No partition found (1)
(1,1):ocfs2_fill_super:1006 ERROR: superblock probe failed!
VFS: Cannot open root device "803" or unknown-block(8,3)
Please append a correct "root=" boot option; here are the available partitions:
0800      78150744 sda driver: sd
0801      36523746 sda1
0802        498015 sda2
0803      31126400 sda3
0b00      1048575 sr0 driver: sr
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3)
Pid: 1, comm: swapper Not tainted 2.6.33.4custom #1

I've tried everything, making the initrd with "-m sd_mod:ext3", trying to add other drivers and nothing works. I think the problem is in the way i'm creating the initrd, but i'm out of ideas.

Please, help me find a solution to this.
Thanks in advance.

I forgot to mention, that when lilo loads the operating system, during the "Bios data check" process, the dots "jump" in one place, leaving it blank, and takes too much time than before, besides it prints a lot of more dots.

Code:

Loading Slackware...........................  ......................
.....................................................................
................................BIOS Data check successful.

Also, i can boot the system normally if i erase the initd entry from lilo.conf (#initrd = /boot/initrd.gz), but of course, without bootsplash at all. How could i make an uncorrupted initrd file that makes this work?

Semash! 04-03-2012 10:26 PM

The mistake was in the way i loaded and compressed the initial ramdisk. I have another issue but i'll post the solution to this and open a new thread.

The solution is quite simple:
Clean the /boot/initrd-tree by running:
Quote:

root@/boot~# mkinitrd -c -k 2.6.33.4-custom -m ext3
Then create the splash initrd by running:
Quote:

root@/boot~# splash -s -f /etc/bootsplash/themes/slackware/config/bacnd..1024x768.cfg >> /boot/initrd-tree/bootsplash
And after that, update the initrd with the new tree by running:

Quote:

root@/boot~# mkinitrd -o initrd.splash
That made it. Update lilo to point to initrd= /boot/initrd.splash, run lilo and you're done.

Even the BIOS Data Check just prints one dot before loading OS.


All times are GMT -5. The time now is 06:20 AM.