You are not logged in.
Pages: 1
hi Folks,
grub can not found a 2nd HDD on witch I put some tools for backup and stuff.
System is a VM running on VM-Workstation 17.5.
4 HDDs.
/dev/sda1 2048 1050623 1048576 512M EFI-System
/dev/sda2 1050624 9439231 8388608 4G Linux Swap
/dev/sda3 9439232 167770111 158330880 75,5G Linux-Dateisystem
/dev/sdb1 2048 83884031 83881984 40G Linux-Dateisystem
/dev/sdc1 2048 125827071 125825024 60G Linux-Dateisystem
/dev/sdd1 2048 33552383 33550336 16G Linux-Dateisystem
blkid:
/dev/sdd1: LABEL="tools" UUID="050afca0-5079-4ea2-b605-7f79bca211d3" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="36e99685-9608-42a0-a795-783b42439cdb"
/dev/sdb1: UUID="25ee6dab-c69e-45c1-8c30-c48e8eda244b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="93b1186b-603a-4134-985a-d9ce7c5c2ab0"
/dev/sdc1: UUID="20822b1d-f4c6-449e-ab75-41ab0dec4987" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="728df228-c177-4b39-8b7a-e69e977996e2"
/dev/sda2: UUID="038d9d27-c508-4088-bf17-99801df1a0b7" TYPE="swap" PARTUUID="15b941a4-fcc9-4c9d-8bac-08a164347d10"
/dev/sda3: UUID="45ec27be-f11b-485f-be53-2be2b5315359" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="744f11d7-6462-4cad-81ae-76aedde2a66a"
/dev/sda1: UUID="6AF3-D8C1" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="c3d2d1ac-a4f0-4bea-9c7f-3eab9b23d71c"
this is the grub entry Im trying to boot
#! /bin/sh -e
echo "Füge einen Starteintrag für Tools ein" >&2
cat << EOF
submenu "Tools" {
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
menuentry "SystemRescue 9.04 64-Bit" {
load_video
insmod gzio
insmod part_gpt
insmod part_msdos
insmod ext2
search --no-floppy --label tools --set=root
linux /sysres904/boot/x86_64/vmlinuz archisobasedir=sysres904 archisolabel=tools copytoram setkmap=de-latin1-nodeadkeys
initrd /sysres904/boot/x86_64/sysresccd.img
}
}
EOF
Arch itselfs boots fine.
But if I try to boot SystemRescue grub gives me device not found. No device there called tools.
But from the output of blkid I see it is there.
I also tried using UUID... same result... no device with that UUID.
On Debian putting tools on its own partition worked since Debian 8 for me.
Now that I try to switch to Arch the problem starts.
Offline
Could it be that grub will only find devices that are on the same disc as grub is?
I put the Tools directory here on an other HDD.
Offline
The syntax looks wrong to me:
search --no-floppy --label tools --set=root
It should read
search --no-floppy --label --set=root tools
Offline
Same error:
Error: no such device: tools
Error: File "vmlinuz" not found.
Error: Load kernel first.
Offline
The order doesn't matter.
Try removing the insmod commands. You have a GPT disk but you've forced the MS-DOS module, which isn't needed. I find that GRUB can autoload the modules just fine anyway.
EDIT: and you don't need `cat`, just the menuentry is fine.
EDIT2: actually that would only apply to 40_custom and that should have the `tail` command first. What is the name of the file shown in your post?
Last edited by Head_on_a_Stick (2023-12-22 18:35:28)
Para todos todo, para nosotros nada
Offline
it's /etc/grub.d/11_tools, yes file is 755... a config for my own tools parition.
removing insmod dosent change anything.
Last edited by Ska (2023-12-22 18:47:49)
Offline
Can we see
# grub-probe -t fs_label -d /dev/sdd1
Para todos todo, para nosotros nada
Offline
sure, it display "tools"
Offline
No idea then, sorry. I'm going to blame VM-Workstation because I know nothing about it
Perhaps put "VM-Workstation" in the thread title to attract the attention of people who know about it.
Para todos todo, para nosotros nada
Offline
OK I created another VM.
Just one big drive with differnt partitions for /, /home, /backup, /tools and swap. And not own HDD for each partition.
And guess what... It works with my config on the first try.
So im pretty sure it's the other HDD the tools are on witch causes the problem... Grub just can not find another then the default HDD.
I thought we had UUID for this....
Last edited by Ska (2023-12-22 22:38:45)
Offline
Given that everything is configured correctly and GRUB can recognise the label independently this must be a VMWare problem. It looks to be a proprietary solution so why not ask them?
Para todos todo, para nosotros nada
Offline
Pages: 1