[SOLVED] Laptop dual boot win10/fedora installer does not see disks

karcio · 02-21-2021, 04:34 PM

Quote:

Originally Posted by Brains

So you should now look into that to make sure you can get into the recovery environment should the need arise in the future. Open a command prompt as administrator in Windows and check with command:

Code:

reagentc /info

Thank you for this reply. Is that OK?

Code:

PS C:\Windows\system32> reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: a093a880-652f-11eb-895c-0c379608d3d0
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

PS C:\Windows\system32>

karcio · 02-21-2021, 04:38 PM

Quote:

Originally Posted by Brains

Forgot to mention, sometimes reagentc does not updated itself and shows RE as being enabled when it's actually not because it's not aware of the partition changes. It's a good idea to disable it, then enable it, then check to see if it's actually enabled.

Code:

reagentc /disable
reagentc /enable
reagentc /info

Cool, my last answer was before I've seen this one I quote, so I will run above commands

karcio · 02-21-2021, 04:42 PM

I think now I'am safe

Code:

PS C:\Windows\system32> reagentc /disable
REAGENTC.EXE: Operation Successful.

PS C:\Windows\system32> reagentc /enable
REAGENTC.EXE: Operation Successful.

PS C:\Windows\system32> reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: d1633657-7495-11eb-a26e-28c21fcb5a7a
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

PS C:\Windows\system32>

Thank you very much for your help

Brains · 02-21-2021, 04:50 PM

Try the Windows RE to see if it works with the command below, you run the command in an elevated propmt then close all windows and the command window etc. either shutdown or reboot. It should boot into the recovery environment if properly setup.

Code:

reagentc /boottore

Brains · 02-21-2021, 04:57 PM

I'm guessing you didn't install Fedora yet because you're RE is still partition 4. Make sure to check after installing Fedora.

Quote:

\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE

karcio · 02-21-2021, 05:33 PM

Quote:

Originally Posted by Brains

I'm guessing you didn't install Fedora yet because you're RE is still partition 4. Make sure to check after installing Fedora.

I have already installed fedora, pls have a look

Code:

[root@dell ~]# fdisk -l
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: PC611 NVMe SK hynix 1TB                 
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: 72046526-CCE4-4A44-A9D2-36640C0DEE53

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       2048     391167     389120   190M EFI System
/dev/nvme0n1p2     391168     653311     262144   128M Microsoft reserved
/dev/nvme0n1p3     653312 1345120255 1344466944 641.1G Microsoft basic data
/dev/nvme0n1p4 1959520256 1961547775    2027520   990M Windows recovery environment
/dev/nvme0n1p5 1961547776 1997469695   35921920  17.1G Windows recovery environment
/dev/nvme0n1p6 1997471744 2000377855    2906112   1.4G Windows recovery environment
/dev/nvme0n1p7 1345120256 1347217407    2097152     1G Linux filesystem
/dev/nvme0n1p8 1347217408 1959520255  612302848   292G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/mapper/luks-92ac2d42-ac4b-4dfa-a834-7189d3c7d749: 291.95 GiB, 313482280960 bytes, 612270080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/zram0: 4 GiB, 4294967296 bytes, 1048576 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
[root@dell ~]#

karcio · 02-21-2021, 05:51 PM

Quote:

Originally Posted by Brains

Try the Windows RE to see if it works with the command below, you run the command in an elevated propmt then close all windows and the command window etc. either shutdown or reboot. It should boot into the recovery environment if properly setup.

Code:

reagentc /boottore

This command works for me, after I've restarted and boot with windows then opened in RE mode. Thank you

Brains · 02-21-2021, 06:02 PM

Perfect, enjoy Fedora, it's gets a little quirky once in a blue moon but I really like it.
I thought you were originally planning on putting Fedora before the RE partition as mentioned in your first post. You apparently put Fedora partitions at the end instead which is why the Windows RE is still good. Had you put Fedora partitions before the RE, it would have been disabled.

Quote:

- NTFS 1TB partition which I've shrinked and created new NTFS partition 300GB for Linux (this NTFS is only temp)
- 3 hidden recovery partitions

Brains · 02-21-2021, 06:18 PM

Quote:

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 391167 389120 190M EFI System
/dev/nvme0n1p2 391168 653311 262144 128M Microsoft reserved
/dev/nvme0n1p3 653312 1345120255 1344466944 641.1G Microsoft basic data
/dev/nvme0n1p4 1959520256 1961547775 2027520 990M Windows recovery environment
/dev/nvme0n1p5 1961547776 1997469695 35921920 17.1G Windows recovery environment
/dev/nvme0n1p6 1997471744 2000377855 2906112 1.4G Windows recovery environment
/dev/nvme0n1p7 1345120256 1347217407 2097152 1G Linux filesystem
/dev/nvme0n1p8 1347217408 1959520255 612302848 292G Linux filesystem

/dev/nvme0n1p1 ---> Partition #1
/dev/nvme0n1p2 ---> Partition #2
/dev/nvme0n1p3 ---> Partition #3
/dev/nvme0n1p7 ---> Partition #4
/dev/nvme0n1p8 ---> Partition #5
/dev/nvme0n1p4 ---> Partition #6
/dev/nvme0n1p5 ---> Partition #7
/dev/nvme0n1p6 ---> Partition #8

You will notice your partitions are in order of creation, not in disk order. The last two partitions created are 7 & 8, your Fedora partitions. However you'll notice they are situated before the 3 recovery partitions.
I'm not sure why this is, I do recall GPT partitions originally were listed in order of creation not disk order. But on my machine, something rearrange them so they are in disk order. I suspect Gparted Live did it on mine. What this means, if your partition table gets modified in the future to disk order, your RE will be disabled.

Brains · 02-21-2021, 06:37 PM

And Windows Recovery works with partition numbers, as you saw in the reagentc /info command. The two other recovery partitions likely have the Windows images for full/partial restoration. They used to be partitions 5 and 6, if your partition table is altered to disk order, they will be in partitions 7 and 8.
I always move my RE partition up against Windows where Windows expects it to be, keep partitions in partition order same as original setup and install Linux after Windows stuff.

colorpurple21859 · 02-21-2021, 07:04 PM

Quote:

something rearrange them so they are in disk order.

If your duel booting with windows, a windows update will do this sometimes.

Brains · 02-21-2021, 07:27 PM

Quote:

Originally Posted by colorpurple21859

If your duel booting with windows, a windows update will do this sometimes.

I suspected this also.
Which is why one must take note of this creation/disk order thing, and keep an eye on it.
If it changes, it's not too hard to set the recovery partitions properly with a couple reagentc commands.

karcio · 02-22-2021, 07:11 AM

This is worrying what you guys mention above

I guess, I need to run this command sometimes

Code:

reagentc /info

and if something change like this line

Code:

\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE

then run following

Code:

reagentc /disable
reagentc /enable

and for confirm

Code:

reagentc /info

computersavvy · 02-22-2021, 04:05 PM

Quote:

Originally Posted by karcio

Thank you for this reply. Is that OK?

Code:

PS C:\Windows\system32> reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: a093a880-652f-11eb-895c-0c379608d3d0
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

PS C:\Windows\system32>

That should be OK. Unless the partitions are reordered on the drive that one should stay #4 and it should be fine.
My dual boot system shows the same, even though I shrunk partition 3 (the windows OS) and installed linux in between the smaller partition 3 and the existing partition 4.
My disk now shows

Code:

$ sudo fdisk -l

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1      2048     534527    532480   260M EFI System
/dev/nvme0n1p2    534528     567295     32768    16M Microsoft reserved
/dev/nvme0n1p3    567296  199752334 199185039    95G Microsoft basic data
/dev/nvme0n1p4 998473728 1000214527   1740800   850M Windows recovery environmen
/dev/nvme0n1p5 199753728  210239487  10485760     5G Linux filesystem
/dev/nvme0n1p6 210239488  998465535 788226048 375.9G Linux LVM

Partition table entries are not in disk order.

Note that the partition names are in order but the start & stop locations are not. This is not a problem for windows recovery unless you manage to change the partitioning numbers.

calliealbert · 02-23-2021, 02:25 AM

It should not be any different than dual booting on a regular hard drive.