Hello everyone . I can no longer log in to Qubes. It may be related to the fact that you made the wrong password twice or three times in a row in a Qubes password situation. You can still reach the password screen, but when you enter your password, the following command will appear: The command is long so some parts have been omitted. {(4.048973)dracut-cmdline(249) warning: usb in dom0 is not restricted.Cons ~~~~ You might want to save /run/initramfs/rd sovepovt.txt to a usb strict or/ boot ~~~~ Please Enter for maintenance(or press control-d to continue)}. When I pressed Enter, the command sh-5.2# came up, and pressing control-d did not have any effect. How can I be able to log in again? please tell me. Also, I’m in Qubes from USB.
1 Like
Hi there,
Your message is not very clear. You could edit to add some details…?
Does your error look like the one here:
https://learn.redhat.com/t5/General/Booting-issue-dracut/td-p/42774
I think it means the dracut environment cannot find the Dom0 filesystem. I am guessing the decryption worked OK.
I see this at the end of your post:
…what does it mean? Is Qubes installed on some usb device? Not many people do this, I think. I do not know how it works… Maybe the usb is plugged to the wrong port, or maybe some other device is plugged in? Or maybe there is corruption?
2 Likes
Thank you for your reply. I’m sorry for the poor English language. I put Qubes in a USB flash drive and start Qubes from there. I’m not installing Qubes on the laptop itself. I don’t know if this is abnormal or if this is the cause of the error. I also tried my best to put the details of the command into the question, but it was impossible with my own abilities. However, if you type ~control-d into the line of ~Please Enter for maintenance(or press control-d to continue)}.~,
{478.210939}dracut-cmdline{1098}: warning: USB is dom0 is not restricted. Consider rd.qubes.hide-all-usb or usbcore.authorized-default=0.
A command line came out like this. Also, I didn’t know if it was the same as my error from the article in the URL you attached, but there are obviously different command lines. I will continue to make an effort to include the details of the command in the question. Thank you for your advice.
1 Like
This error is not the big problem, I think:
warning: USB is dom0 is not restricted
It does not prevent starting of Qubes.
If you see the error like in the redhat link above, then I do not really know the answer.
Did the usb key work for a lot of restarts, but just stopped?
I would try these things:
- Verify that all USB devices are plugged exactly like before. (Same computer, same sockets… ). Then try again. If not…
- Do you see some “does not exist” messages, like in the link? These would be your Dom0 volumes. Press “enter” to get the shell. Then try the
lvmcommands in the link. Do you see the “not exist” volumes? Maybe an expert can tell you how to make them work.
1 Like
Was OP thinking Qubes would start like a Live Distro of Qubes. As Mint Linux does? Or Ubuntu Linux does?
If OP has a mission critical need for using a highly secure OS, such as Qubes Linux is.
Like trying to keep his money safe from internet theft. Perhaps they might use Tails OS, which is a Live OS that runs on a USB. Or, perhaps Easy OS, as described on the Puppy Linux forum. Although keeping them secure may require multiple restarts between 'needed Uses."
Building the original Qubes OS on USB for use installing Qubes can sometimes have more problems than a person may originally have guessed. The documentation on the Qubes OS site works though.
Trying to install Qubes OS alongside another OS has security issues, and is more difficult than following the instructions for using Qubes -all alone on the computers hard drive.
2 Likes
Thank you both. I’ve been running Qubes using USB many times so far, and I’ve never had any problems so far. Also, even after I got an error like this, I have tried booting it many times, but it doesn’t work. In fact, the attempt to start Qubes this morning itself has gotten worse. This time, an error occurred without even reaching the password entry screen, and the system was forced to shut down. I don’t think I can fix it with my own abilities, so I’m thinking of recreating Quebes. Thank you for your advice.
2 Likes
It could be that your USB drive has become corrupted. I used to run Qubes this way but after a few months it would always fail, or at least become very slow. USB drives aren’t really made for use as a primary OS partition.
2 Likes
Thank you Plum. It seems that you have to install it using the regular method. At first I thought it was a simple password lock, but it seems to be even more serious. I’ll start over from the beginning.
2 Likes
Unraid users are feed up usb boot feature.
They constantly make startup disk duplicate and change usb pendrive in monthly or weekly maner.
On TrueNAS forum everybody says “connect your drive any how you want but usb”.
Pendrive memory chips and driver chips are unrealiable at best and constant usage wear off memory on them super fast (SD cards are more reliable than usb pendrive) and usb disk shelves uses cheapest drive chips available with fundamental flaws in firmware. When there is chip with programing thru data line capability people use moded firmware.
Max what I would do would be /boot/efi on usb (not much IO during work) and make lots of copies of it all the time.
2 Likes
Even when no writing is done deliberately, regular usb keys seem to fail very quickly. I do not think it can be the marking of the filesystem during the default rw mounting… but it seems to be on every machine and brand.
Currently trying micro SD in a standard SD carrier with the read-only switch set…
Note to @phirip : a true usb-ssd may be a better solution than a usb memory stick/key. More expensive, but much more reliable.
1 Like
I forgot to say when you wrote this:
The problem was not “poor language”, only “not enough details”…
If you have bad luck, I will try to communicate in another language - then you will see “poor”!
(full disclosure: my french is OK, but I know how much work it takes even to get OK. Every other language is hopeless)
1 Like
Thank you both for your advice.
Honestly, I knew that installing it on a laptop was the correct procedure. However, since I had no ability to deal with any issues like this one, I had to use USB. If there is a problem that cannot be dealt with, you can lose $50 on a USB memory stick, but $500 on a laptop. I don’t know anything other than how to install it on a USB or laptop, but is a micro SD card the best place to install on a non-PC? I’ll try to find out how to do that myself, but I don’t know how to install it either. We hope you continue to give us advice.
Thank you so much, phceac