I think that you should create an initial ramdisk with an init script that translates the UUID to the physical device. There is a program called mkinitramfs that can help you create such a ramdisk.
Hello,
I've installed Knoppix 7.0.4 on a pedrive. It boots fine with default GRUB (0.97). I want to boot the system in situations where there are no extra ata/sata drives (as it works after install) and if a drive is left attached. In that case I get kernel panic. I've read somewhere that booting by UUID may help but in GRUB2. I updated my installation to GRUB2. Now I have GRUB menu and chained GRUB2 menu. Original boot works with pendrive only. From GRUB2 entries none boots. I get message:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0).
I've struggled with this for a few days now and seems reached timeout on digging this without help.
Anyone could route me to set this up correctly?
Some parts of setup
Code:# df -T Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs 6663664 2222080 4441584 34% / /dev/root reiserfs 6663664 2222080 4441584 34% / tmpfs tmpfs 2097152 8 2097144 1% /tmp udev tmpfs 20480 4 20476 1% /dev tmpfs tmpfs 2097152 0 2097152 0% /dev/shmgrub.cfgCode:# ll /dev/disk/by-uuid/ total 0 lrwxrwxrwx 1 root root 10 Oct 19 19:39 7265a1af-9120-4bea-a824-2f884e9fe30c -> ../../sda1 lrwxrwxrwx 1 root root 11 Oct 19 19:39 b53f110b-a202-45d0-ac7a-ac6615507484 -> ../../zram0 lrwxrwxrwx 1 root root 10 Oct 19 19:39 ebca161b-33b0-4a6e-9c9c-cc5d1868f6ca -> ../../sda2
My target is to have a hot-swapable station. Hot-Swap works like a charm as the system us running. The problem is that after reboot it won't boot from USB because of mentioned error. From my POV looks like SATA/ATA(/USB?) are logically before the booting pendrive and at position hd(0,1) drive is not the one expected.Code:menuentry 'Knoppix' { insmod gzio insmod part_msdos insmod reiserfs search --no-floppy --fs-uuid ebca161b-33b0-4a6e-9c9c-cc5d1868f6ca --set root echo 'Loading Linux 3.4.9 ...' linux /boot/vmlinuz-3.4.9 root=UUID=ebca161b-33b0-4a6e-9c9c-cc5d1868f6ca ro quiet }
I think that you should create an initial ramdisk with an init script that translates the UUID to the physical device. There is a program called mkinitramfs that can help you create such a ramdisk.
Indeed that helped Creating initrd.img with mentioned tool, removing the 'root' line, and changing kernels root= to use UUID. Now it swings. No the issue is that hdd list seems rebuilding every boot and when addtional drives are in, the booted one is not /dev/sda but gets later letters.
DELL PowerEdge R730XD 24x 2.5" Server Dual 750W Dual Heatsink - BareBones TESTED
$299.99
Supermicro 4U 36 Bay Storage Server 2.4Ghz 8-C 128GB 1x1280W Rails TrueNAS ZFS
$712.98
CSE-118 Supermicro 1U 3x GPU Server 2.6Ghz 20-C 128GB CX353A 2x1600W PSU Rails
$454.03
Dell Poweredge R640 Server | 2x Xeon Gold 6132 | 128GB | H730P | 8x HDD Trays
$1849.00
Intel Xeon E5-2697A v4 2.6GHz 40MB 16-Core 145W LGA2011-3 SR2K1
$37.50
INTEL Xeon E5-2697 V4 SR2JV 2.30GHZ 18-Core CPU 2697v4 GRADE A CONDITION @ A
$49.99
SR1XP Intel Xeon E5-2680 v3 12 Core 30MB 2.5GHz LGA 2011-3 A Grade Processor
$4.79
Intel Xeon Gold 6140 SR3AX 2.3GHz 18-Core Processor CPU
$39.99
Dell Desktop Computer Intel Xeon 16GB RAM 750GB HDD Windows 10 PC AMD Graphics
$154.36
HP Z440 WORKSTATION XEON E5-1603V3 @ 2.80GHz, 16GB RAM 250 GB SSD Win 11
$119.99