<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 29, 2020 at 11:50 AM Gabor Szabo <<a href="mailto:gabor@szabgab.com" target="_blank">gabor@szabgab.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Thanks for the quick reply, at least I don't feel totally alone in this!</div><div><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 29, 2020 at 11:42 AM Shachar Shemesh <<a href="mailto:shachar@shemesh.biz" target="_blank">shachar@shemesh.biz</a>> wrote:<br></div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><p>
</p>
<p>Some SATA/NVME devices have dual modes, settable in the BIOS.
They might, e.g., have a RAID mode etc. Some of those modes are
not supported by Linux. Resetting that in the BIOS should make at
least your bootable DoK see the disk again.</p>
<p><br></p></div></blockquote><div>I saw that in the BIOS, I'll try that.<br></div></div></div></blockquote></div><div><br></div><div>I changed the disk from RAID to AHCI in the BIOS and booted from USB and now lsblk shows the harddisk.</div><div><br></div><div>sda 8:0 1 14.3G 0 disk /cdrom<br> sda1 8:1 1 1.9G 0 part <br>
sda2 8:2 1 2.4M 0 part <br>
nvme0n1 259:0 0 477G 0 disk <br>
nvme0n1p1 259:1 0 499M 0 part <br>
nvme0n1p2 259:2 0 100M 0 part <br> nvme0n1p3 259:3 0 16M 0 part <br>
nvme0n1p4 259:4 0 332.2G 0 part <br> nvme0n1p5 259:5 0 572M 0 part </div><div><br></div><div>based on this and after consulting my notes I can see that apparently I did not install Linux here, only allocated disk space in case I will want to install it as well.</div><div>I can also see that this was done in December 2018, not that it matters a lot now.</div><div><br></div><div>So now at least I can access the hard disk. That's a relief.</div><div><br></div><div>Gabor<br></div><div><br></div></div>