Le 22/02/2019 à 17:36, Stephen P. Molnar a écrit :
On 02/22/2019 09:13 AM, Dan Ritter wrote:Stephen P. Molnar wrote:My Debian Stretch system has three HD's. I want to remove one of the HD's (not sda)
You can never know which drive will be sda at next boot.
The system needs the following to boot: - the BIOS or UEFI needs to know which drive has a boot loader.
For UEFI, it is rather the other way around : it has a list of boot entries and searches each matching EFI executable in order on the drives. Only if none is available, then as a fallback mechanism it searches a special executable in EFI partitions.
UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 errors=remount-ro 0 1 UUID=d65867da-c658-4e35-928c-9dd2d6dd5742 /sdc1 ext4 errors=remount-ro 0 1 UUID=007c1f16-34a4-438c-9d15-e3df601649ba /sdc2 ext4 errors=remount-ro 0 1
Mount points which have device names that which may differ from the actual mounted device. This is so wrong... Fixed mount points should be named from the contents, not the container. This is what mounting is all about. /var contains variable data, regardless of its container.
Before disconnection the power to the drives, I edited out their lines in fstab. I disconnecting the power to sdb and sdc and started the computer. It booted for a few lines until it encountered the line starting with 'start job fgfor device disk by . . .' (at least that what i jotted down).
You need to post the complete line, and the surrounding lines related to the error.