Side question:
Since NVMe (SSD) are life limited (actually or āon purposeā ?) I guess I should āsacrificeā the cheapest of the three for all RW intensive, like /swap, /tmp, /var ⦠how does that work with Qubes, as it would totally deafeat the security purpose. Will I be able to get a separate /var /tmp etc ⦠while still within LVM encrypted ?
Based on my very limited knowledge:
The log file is generated during install tentative
Thatās when I have access to said file, and also when I donāt have access to any drive.
If I unplug the USB with install.iso to plug an empty one, I will no longer have access to install system, therefore no longer access to log nor any way to write it ?
IāM not questionning th epossibility to do so
Iāve been using separate partitions for /swap and /tmp for decades, on all my OS including windows.
My question (side one = not exactly related to the thread main subject) is about the NVMe limited life, and the use of heavy RW folder/partition such as /tmp; /var and of course Swap.
As my 2x 2TB NVMe are more expensive than the smaller 512G one, I would rather use the later as āsacrificialā and move all swap; tmp; etc ⦠to it.
But while it has not problem with Win10 (being m ādecoy OSā), it will have a major security issue with Qubes, and therefore Iām here asking the community what they think of the use of swap and tmp on NVMe
No matter how long I wait, the prompt never comes back to anything usable (user or root prompt)
As Iāve been able to install and reinstall Win10; Suse Leap 15.4; Debian 11 and Fedora 37, there is clearly something wrong with Qubes installer, but I canāt extract the log (only the picture I provided)
Thank you @51lieal ,
But I donāt think you understand:
There is no command available at āsh-5.0#ā prompt
Since there is no LS, that means I canāt CAT nor Less
The installer crashes even before loading the graphical installer, so I donāt even have access to ctrl-f2
Giving it another try, using again the menu option: āTroubleshooting, Verbose and installā
And then echo dozains of lines about dracut-initqueue timeout, until giving me the ctrl-D choice
If I enter āenterā I end up with āsh-5.0#ā prompt which doesnāt give me any CMD possibility
Iām not āenteringā (as in āvoluntary actionā) the shell, IāM just plugging-in the SD card with Qubes install (DLād from the latest monthly update) and let it run ā¦
We can see that the installer mounted the SD card in sda1,
But it seems the Qubes installer is unable to map none of the 3 NVMe ⦠while Debian.11 and Fedora.37 are totally fine with mapping it, therefore someā wrong in the Qubes installer
PMād you
What I can do though, is to run again the Fedora.37 installer and capture the log
Or any previous version (to match the one used in Qubes)
If that helps ?
As I was messing (actually!) around with my other laptop, the T440p, and crashed the partition table ⦠Iāve had to rebuild it, and while at it, I decided to move back from Dynamic USB disk to internal static disk, and move from MBR to GPT all together.
At some point, as it didnāt work, I decided to install SUSE to use its grub2 to make it for the windows boot partition missing.
Bu I took the wrong SD card and went on installing QUBES.
As it turn out ⦠QUBES 4.1.1 doesnāt install on my T440p (2,5 SSD, not NVMe) neither !!
So now Iām going to try with older version of QUBES