SliTaz Forum
You are not logged in.
Pages: 1
SliTaz does not boot on my computer.
The boot process stops and says:
kernel panic - not syncing: VFS: unable to mount root fs on unknown block (0,0)
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.10.238-slitaz64 #2
I have a Ryzen processor.
Offline
Hi akm,
Strange it's on live boot or boot install. On my side i have laptop why ryzen and nvme disk, it's work well.
Do you have special installation ?
For raid/kvm install need initrd to be boot correctly.
Download initrd that support kvm/raid installation
wget http://people.slitaz.org/~shann/Public/initrd-kvmraid.gz -O /boot/initrd-5.10.238-slitaz64.gz
After edit /etc/default/grub and uncomment GRUB_CMDLINE_LINUX_DEFAULT="" and change to it GRUB_CMDLINE_LINUX_DEFAULT="softroot=/dev/mdXY" (XY for device, exemple md0).
Don't forget to update grub.cfg grub-mkconfig -o /boot/grub/grub.cfg
Of course if you use syslinux bootloader, need to be adjust for add initrd line.
Offline
I mean it doesn't boot from the hard drive after I installed it. The USB image does boot and I was able to install SliTaz. But it does not boot after the install.
Offline
I do not have anything special like RAID or KVM. I boot from a normal hard drive.
Offline
On live, can you paste lsmod, and information about disk please.
Also syslinux file or grub.cfg thanks.
Strange that you can install system on disk, and after reboot failed to detect disk and root.
Think kernel line with root= is wrong.
Offline
Hey, I'm not sure, but I think there is no initramfs or initrd on the install. I couldn't find any such file on the SliTaz partition.
Offline
Maybe it's not initrd. I pasted rootfs.gz into /boot and still the same kernel panic.
Offline
I have a debian installation and use debians grub to boot. It always worked with slitaz 5.0. Is that the issue?
Offline
Hi akm,
By default don't need initrd it's just need for special case.
this why you don't see file.
When you install SliTaz at boot screen it's grub2 or syslinux ?
In live can you please mount your root partition and add as attachment /boot/grub/grub.cfg file or boot/syslinux/syslinux.cfg ?
Also please paste return of lsmod command and /var/log/boot.log /var/log/messages ?
Thanks
Offline
What do you mean with disk exactly?
Offline
Ok if you use grub to load SliTaz, normally you should have this entry to simplify
linux /boot/vmlinuz-5.10.238-slitaz64 root=/dev/null ro
initrd /boot/rootfs.gz
It's similar of usb boot, normally this work to boot live ? right ?
Offline
do you really mean root=/dev/NULL?
Offline
Here is my lsmod
Offline
oops
I mean here is lsmod
Offline
I made a mistake. I did not set initrd in grub.cfg correctly first. I set initrd to rootfs now, and it boots from HDD. Username is tux. It is like the USB I think.
Offline
No problem, in case it's work as live.
In live, can you paste return of [c]fdisk -l[/c] please ?
NB: initrd line should be remove after when we found cause and fix kernel panic to boot on installed system instead live.
Offline
here is the return of fdisk -l
Offline
I'm sorry. here it is. the extension was wrong and I had to rename the file.
Offline
Thanks,
If understand you have disk /dev/sdb partitionning in GPT with various partitions.
/dev/sdb21 as root for SliTaz Current and /dev/sdb22 as home.
Normally entry for grub on your debian should be this (not sure for set root line, i compare with grub.cfg generate on fresh install on qemu):
set root='hd1,gpt21'
linux /boot/vmlinuz-5.10.238-slitaz64 root=/dev/sdb21 ro
If i compare of my grub entry (boot EFI)
### BEGIN /etc/grub.d/10_linux ###
menuentry 'SliTaz GNU/Linux' --class slitaz --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-f9460ff0-5a4c-4a68-958f-00919d83b0d9' {
load_video
insmod gzio
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root f9460ff0-5a4c-4a68-958f-00919d83b0d9
else
search --no-floppy --fs-uuid --set=root f9460ff0-5a4c-4a68-958f-00919d83b0d9
fi
echo 'Loading Linux 5.10.238-slitaz64 ...'
linux /boot/vmlinuz-5.10.238-slitaz64 root=/dev/nvme0n1p2 ro
}
Offline
I think it worked. I think I named my drive sda13 instead of sdb13 in GRUB. I think GRUB made a mistake.
But I forgot my password^^
Offline
Nice, if understand wrong match between disk 
For password, in live you can mount root partition and chroot inside to change password 
.
mount /dev/sdb21 /mnt
chroot /mnt passwd <your_username>
umount /mnt
And reboot
Of course you can remove /boot/rootfs.gz not necessary now.
Offline
Yes! It works!
Offline
Pages: 1
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.57 MiB (Peak: 1.77 MiB) ]