On 2022-06-18 17:40, Simon Becherer wrote:
Am 18.06.22 um 17:16 schrieb Carlos E. R.:
On 2022-06-18 17:10, Simon Becherer wrote:
Am 18.06.22 um 16:33 schrieb Simon Becherer:
Am 18.06.22 um 16:13 schrieb Andrei Borzenkov:
On 18.06.2022 16:57, Simon Becherer wrote:
...
as a result of this analysis you tell me that the content of my: "/etc/default/grub_installdevice" file is wrong ???????? i have inside only one line: /dev/nvme0n1p2
that points to the partition where /boot is. must it point to the partition where the core.img is ? that would be /dev/nvme0n1p1 or must there be not a partition inside instead a whole disk: /dev/nvme0n1 ??
sorry, i have not found any documentation what has to be inside that file. (using google)
When using the MBR, it points to the disk. The system knows that the next stage is in the bios partition, and next in the boot directory or partition, if it is separate.
i do not understand, a other system tumbleweed i use, is mbr no gpt and has 3 lines inside: "/dev/nvme0n1p1 activate generic_mbr"
I do not know what the other two lines do. I know that the first line, in this case, is the whole disk. I know that in my machine, which is bios based and uses a GPT disk, that file has a single line pointing to the disk: Elesar:~ # cat /etc/default/grub_installdevice /dev/disk/by-id/ata-Samsung_SSD_850_EVO_250GB_S2R6NB0J535704L Elesar:~ # And this was done by YaST, so it must be correct. And you have seen the partition table: Elesar:~ # fdisk -l /dev/sda Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors Disk model: Samsung SSD 850 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: DD259BAE-154F-49DC-83F9-EA43B4A27EEE Device Start End Sectors Size Type /dev/sda1 2048 50333695 50331648 24G Linux swap /dev/sda2 50333696 50364415 30720 15M BIOS boot /dev/sda3 50364416 81819647 31455232 15G Linux filesystem /dev/sda4 81819648 291534847 209715200 100G Linux filesystem /dev/sda5 291534848 343963647 52428800 25G Linux filesystem Elesar:~ #
sda sda 512 0 0 232.9G disk ... Samsung_SSD_850_EVO_250GB ├─sda1 sda1 24G part swap ssd-swap ssd-swap ├─sda2 sda2 15M part primary ├─sda3 sda3 15G part ext4 ssd-test primary ├─sda4 sda4 100G part crypto_LUKS ssd_home_cr
i never touched this file by hand.
so there is not a disk, there is a partition and that is the partition where /boot is on. why is this different to a gpt where i have (maybe) to write a disk not the partition in?
where is the dorcumentation of this fiele ?
simoN
-- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)