On 9/27/20 3:23 PM, Carlos E. R. wrote:
On 27/09/2020 21.11, Mark Hounschell wrote:
On 9/27/20 2:18 PM, Carlos E. R. wrote:
On 27/09/2020 19.51, Mark Hounschell wrote:
This box has a 3 bay Sata rack. I can put the 15.2 SSD in any of the 3 bays and boot/run just fine.
I have a windows 10 disk built on said box, with it and only it, installed in the normal slot. IE, the BIOS denotes it as "P0". The windows disk will only boot up in that "P0" bay. Not any of the other 2 bays. Some sort of disk I/O error is shown. No other disks installed.
With the win 10 disk installed in the second bay, it is detected by "grub2-mkconfig -o /boot/grub2/grub.cfg". And an entry in there in the boot menu. But I get the same I/O error as when it was the only disk installed.
I know this is not a windows forum but why can't I boot this win-10 disk in any other sata bay other than the one the bios says is "P0"?
I'd guess it is using some disk reference tied to the path, not to the device as does Linux and Grub.
I'd place the Windows in the first bay, Linux in the second, and then use the bios/uefi settings to boot the second disk first.
When I do that and try to boot Linux, it cannot find the / filesystem. I guess because it's no longer (hd0) ???
Well, just do not use hd0 / sda names. Use UUID or LABEL. Both Grub and fstab.
Well, the fstab is using LABELS already. I commented out this in the /etc/default/grub file and now it works. # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux GRUB_DISABLE_LINUX_UUID=true Is there a way to make grub use LABELS instead of UUIDs? I hate UUIDs on such small systems. It is working now though. Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org