If I can’t get Purism to reply and resolve this, the only next step would be to purchase and replace the m.2 ssd it came with and go from there? Im assuming I can not re load qubes os without getting passed the passphrase? Am I seeing this correctly?
No.
All you would do is download the latest iso I believe technically in beta, been a minute since I checked, then boot off a USB that you loaded the content of the iso to and install.
2 Likes
I booted from a USB and it brought me to the qubes os install screen and gave me the option to re claim my SSD. It looks like there is LUKS encryption set so without the password i wont be able to access it the normal way. If its allowing me to re claim and delete this then it should be normal as the initial install? Am I seeing this correctly this time?
Everyone’s reply is very much appreciated.
If you reinstall off the USB drive it’ll wipe your ssd and reinstall qubes. It’s your OS that’s locked, not the physical ssd itself. Just the data on it.
3 Likes
How stupid is this then to sell the hardware with qubes OS pre-installed and even asking for this and then you have to do it for yourself anyways?
I don’t get it.
What a strange Company…
1 Like
So I ran into this same problem and this solution does not work. Have a LIbrem Mini v2 with SeaBIOS and Qubes OS. When I initially went through the Qubes OS setup I set a password for my user and I logged into the machine a couple of times and it seemed to be working. Then I shutdown the machine and the next time I booted it up was about a month later and it asked for the disk passphrase. Don’t remember setting a disk passphrase. At any rate, I am locked out. So I grabbed the latest Qubes OS iso and when I try to select that from the boot menu the GRUB loading message comes up and then I get the message “error: failure reading sector 0x15fc from ‘hd0’” and it drops me into grub rescue.
1 Like
If you went through the Qubes OS OEM installation procedure, there is no disk password, so simply press Enter/Return.
Otherwise, try using a different USB port.
Thanks for the quick reply. If I try to boot to Qubes OS as it is installed I get the prompt for the disk password. To be exact:
“Please enter passphrase for disk Samsung SSD 970 EVO Plus 250GB (luks-…)::”
Hitting Return/Enter is not excepted. It keeps prompting. If I attempt to boot to the Qubes OS image on USB that fails with the message above after it attempts to load GRUB
1 Like
Okay, try using a PureOS image on a USB drive instead. You will need a different computer to create the installation media.
If you can boot into that, you should be able to redownload Qubes, rewrite the image onto a different USB drive using balenaEtcher, and boot into it.
Just grabbed the Pure OS image and flashed to a USB using Etcher. The I boot to the USB and when I select “Test or install PureOS” it sits at the PureOS splash screen for a while and then I get:
CHS: Error 0c00 reading sector 3433958 (213/192/18)
EDD: Error 0c00 reading sector 3433958
Then it reboots
1 Like
Definitely unusual. @jonathon.hall
It is possible that the USB drive is faulty, so you may want to try a different one in the meantime.
Agree, most likely a faulty USB flash drive, please try a different flash drive.
1 Like
Tried a brand new USB flash drive and got the same error.
CHS: Error 0c00 reading sector 3427421 (213/88/33)
EDD: Error 0c00 reading sector 3427421
1 Like
How large is the USB drive’s capacity?
It is a Sandisk Cruzer Blade 8GB
1 Like
What happens when you try a different USB port?
Have tried 2 different ports. Have my keyboard and mouse plugged into the other two
1 Like
What happens when you attempt to boot the USB drive from a different machine? Does it still throw an error, or does it successfully boot?
So I tried with another pc and the grub menu comes up and the options to boot pureos live come up and either option gives me this message. Does not seem to go beyond this point.
error: no suitable video mode found.
Booting in blind mode
1 Like
That’s expected if the other machine requires proprietary device firmware for the graphics card (AMD/Nvidia or latest generations of Intel), since PureOS doesn’t include that firmware.
Unfortunately that doesn’t really tell us whether the flash drive worked or not in the other system, it may have choked after that but been unable to display the error.
Could you try one of the Debian 12 live ISOs in both the Mini v2 and the other system? (Index of /debian-cd/current-live/amd64/iso-hybrid) The goal here is to get to a point where an image boots correctly on at least one system, so we can tell if there is a problem with the other system (or, preferably, it boots on both and we go back to trying PureOS or Qubes if you prefer).
It could still be a problem with the way the ISOs were written to the media, a problem with the downloaded ISO, or something else. I don’t think you intentionally unplugged them early, but sometimes flushing disk caches can take much longer than you might think. I would assume balenaEtcher would flush caches before telling you it’s done but I’ve never actually tried it, I always dd them myself out of habit.
While you’re trying that, I can give balenaEtcher a try just to see what might go wrong.
1 Like