Can no longer see windows drive

I had a dual boot system with windows and manjaro and successfully installed grub with os-prober enabled. This is what my lsblk output USED to look like:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    0   1.8T  0 disk 
├─sda1        8:1    0    16M  0 part 
└─sda2        8:2    0   1.8T  0 part 
nvme0n1     259:0    0 465.8G  0 disk 
├─nvme0n1p1 259:2    0   512M  0 part /boot/efi
└─nvme0n1p2 259:3    0 465.3G  0 part /
nvme1n1     259:1    0 465.8G  0 disk 
├─nvme1n1p1 259:4    0   529M  0 part 
├─nvme1n1p2 259:5    0    99M  0 part 
├─nvme1n1p3 259:6    0    16M  0 part 
└─nvme1n1p4 259:7    0 465.1G  0 part 

Everything worked great.
sda is just a big empty data drive.
nvme0n1 is my manjaro drive (where root and boot are installed)
nvme1n1 is the windows disk drive.

Suddenly I was no longer able to boot into windows as grub said it couldn’t find nvme1n1. I haven’t removed the internal hard drive windows is installed on. When I now run lsblk I get the following output:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0  55.4M  1 loop /var/lib/snapd/snap/core18/1997
loop1         7:1    0  55.4M  1 loop /var/lib/snapd/snap/core18/2066
loop2         7:2    0  32.1M  1 loop /var/lib/snapd/snap/snapd/12057
loop3         7:3    0  32.3M  1 loop /var/lib/snapd/snap/snapd/12159
loop4         7:4    0 179.6M  1 loop /var/lib/snapd/snap/spotify/46
sda           8:0    0   1.8T  0 disk 
├─sda1        8:1    0    16M  0 part 
└─sda2        8:2    0   1.8T  0 part 
nvme0n1     259:0    0 465.8G  0 disk 
├─nvme0n1p1 259:1    0   512M  0 part /boot/efi
└─nvme0n1p2 259:2    0 465.3G  0 part /


It is no longer there. Any idea how I can get this back?

Thanks

Does your BIOS still see it?
Did you check cables etc?
Check your journal for errors:

$ journalctl -b -p err
1 Like

yes windows puts drives in readonly state
in windows cmd run

shutdown /s /f /t 0

Not “drives” but “filesystems” - there is a difference.
The whole drive vanished and that does look like a hardware problem.

2 Likes