[opensuse] dual boot leap 15.2 ans win-10 issues
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"? Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
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) ??? Thanks mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2020-09-27 at 15:40 -0400, Mark Hounschell wrote:
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:
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.
Well, in one system I see this: /other/auxiliary/boot/grub2/custom.cfg: linuxefi /boot/vmlinuz root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 splash=verbose resume=/dev/disk/by-label/nvme-swap mitigations=auto Maybe I was in error when reccomending Label, you have to use UUID with some possible exceptions.
It is working now though.
:-) - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCX3DuAxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVWgUAn30CpA1XSBTeU0uinqhH S+71BV94AJ90icGwa3GV9nuA2nYo8LT2ZCJEHg== =zyqz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Sun, 27 Sep 2020 21:54:42 +0200 (CEST) időpontban Carlos E. R. írta:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday, 2020-09-27 at 15:40 -0400, Mark Hounschell wrote:
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:
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.
Well, in one system I see this:
/other/auxiliary/boot/grub2/custom.cfg:
linuxefi /boot/vmlinuz root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 splash=verbose resume=/dev/disk/by-label/nvme-swap mitigations=auto
Maybe I was in error when reccomending Label, you have to use UUID with some possible exceptions.
You can use LABEL in grub.cfg, like: linux /boot/vmlinuz root=LABEL=leap151 resume=LABEL=swap The grub manual does not mention it but it works. You have to edit grub.cfg manually and replace UUID=... parts. Make sure to make a backup of your manually edited grub.cfg because next time you run grub2-mkconfig it will overwrite grub.cfg. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/28/20 7:21 AM, Istvan Gabor wrote:
You can use LABEL in grub.cfg, like:
linux /boot/vmlinuz root=LABEL=leap151 resume=LABEL=swap
The grub manual does not mention it but it works.
You have to edit grub.cfg manually and replace UUID=... parts. Make sure to make a backup of your manually edited grub.cfg because next time you run grub2-mkconfig it will overwrite grub.cfg.
Good to know. I wonder why they don't support that directly? Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Mark Hounschell composed on 2020-09-27 13:51 (UTC-0400):
This box has a 3 bay Sata rack. Please describe in detail the meaning of:
1: This box 2: 3 bay SATA rack 3: how "this box" and "rack" are physically related/connected IOW, is this a typical PC containing 3 places to install SATA disks? Or is/are it/they something(s) else? Does each disk separately connect to one motherboard SATA port? Is there any USB involvement with any HDD or SSD? -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/27/20 3:44 PM, Felix Miata wrote:
Mark Hounschell composed on 2020-09-27 13:51 (UTC-0400):
This box has a 3 bay Sata rack. Please describe in detail the meaning of:
1: This box
This box is a normal PC. AM4 based MB
2: 3 bay SATA rack
It is a 3 bay Sata rack. It is a self contained box that is installed in the PC that allows 3 removable Sata disks. Power and sata cables from the MB plug into the rear of it. There is a fan also. Each bay has a power switch and there is a reset button that resets the devices.
3: how "this box" and "rack" are physically related/connected
Sata cables connect the MB to the Sata rack.
IOW, is this a typical PC containing 3 places to install SATA disks?
Basically, yes.
Or is/are it/they something(s) else?
No.
Does each disk separately connect to one motherboard SATA port?
Yes but not directly. See above and below. Is there any USB involvement with any HDD or SSD?
No USB involved. It is something similar to this but a different MFGR. I would have to open up the PC to find the MFGR. https://www.newegg.com/rosewill-rsv-sata-cage-34-hard-disk-drive-cage/p/N82E16816132037?item=N82E16816132037&source=region&nm_mc=knc-googleadwords-pc&cm_mmc=knc-googleadwords-pc-_-pla-_-server+-+accessories-_-N82E16816132037&gclid=EAIaIQobChMItKK5s5GK7AIVR-DICh0QwwVvEAQYAiABEgINkPD_BwE&gclsrc=aw.ds Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carlos E. R. -
Felix Miata -
Istvan Gabor -
Mark Hounschell -
Mark Hounschell