Hallow everybody.
Since Qubes is not working properly, I am considering reinstalling it on another device. I would like to use the data I currently use on my new device by placing it in the account I am using. But I don’t know how to do that. How can I take over my current Qubes data and accounts on my new device? Please tell me the easiest way to do it.
I don’t understand what do you mean by “account” 
but if you just want to keep your current AppVMs/Templates/etc… Just make a backup and restore it in your new device that’s it.
3 Likes
You can take the hard drive out and move it to another computer. Or make a copy of the drive using Clonezilla. It will save all your dom0 settings
2 Likes
My explanation was missing. This is my entire Qubes account. Each time you start Qubes you will be prompted for an account and password that you can select. If you are installing Quebes on a new device, you can use your current data on the new device by selecting your account name and entering your current account name and password, but there is no evidence. Or do I need to create a backup? I did some research on how to make my own backups, but it didn’t work very well. If you need a backup, please let me know how.
Sorry but i don’t understand lol. In Qubes, you just have one account, you don’t have to select another one You’re talking about connection on lightdm, right?
1 Like
Thank you for replying.
Does that mean that when creating Qubes on a new device, I can set my current account and password to use my current data as is?
Currently, I have installed Qubes on a 1 TB SSD, but it is very slow to boot. So I’m thinking of installing Qubes on my new SSD or laptop. I would also like to use the new SSD or Qubes in my laptop as my current data.
Just do like in documentation:
4 Likes
It may be a little difficult for me, but I’ll try as much as I can. thank you.
it’s not so difficult, don’t worry 
2 Likes
I tried following this URL, but I didn’t know what part 2 was, so I chose the appropriate file (selected bin). I don’t know if that’s why, but an error occurred while the backup was created about 22%. I think that’s because one item with storage was 99% full.
After that, I thought about making a backup again, but I couldn’t proceed from step 2. After that, turn off the power and reinstall it, enter the password from the first password screen.
[ [ 5.290007] dracut-cmdline[246]
USB in dom0 is not restricted. Consider rd.qubes.hide_all_usb or urbcore.authorized_default=0. ]
and I was unable to enter Qubes.
By the way, USB was not used when creating a backup or when starting up.
I dont really understand what you did.
After a failed backup, you reinstalled Qubes OS on another computer, right?
The error message related to USB is another problem. Take a look at the relevant forum topics to change the grub options. Have you changed anything related to sys-usb during the installation process?
By the way, on the forum you can use this to copy/paste command-line content:
```
echo $something
````
Will become:
echo $something
1 Like
Reply, thank you I haven’t reinstalled Qubes on another device after a failed backup. We thought that if the backup was not successful, the data would not be available on the new device. Therefore, this error message is also current. Also, the backup was done in test mode. Therefore, it was written that the records were not actually backed up. Also, I haven’t made any changes to sys USB as far as I know.
Also, from the above error message, you will no longer be able to accept any operations and will not even be able to enter Qubes. Therefore, you cannot put the code for “echo $something”. Where do I put this code? Also, what are “grub options”? What can be done by changing it? I don’t even understand how to back up, so it may be difficult for me to fix this error on my own.
Did you set backup destination to dom0?
If yes, then the reason that you can’t boot could be the out of free space in dom0 issue.
You can try to boot from some LiveCD Linux OS, mount dom0 root and remove the backup files from there to free up the space.
2 Likes
I chose DOM0. Also, in step 2 of the URL to create the packup, I selected a file called [bin] as the backup file (there is no particular reason for choosing this file). I thought any file would be fine).
The Qubes are directly in the laptop, and the laptop currently only works with Qubes, can you use your method?
You need to have another working PC where you can download some Live Linux OS image and write it on USB disk.
Then you’ll be able to boot from it on your Qubes OS laptop, decrypt the LUKS partition, mount the dom0 root LVM volume and remove the backup file from there.
You can also use Qubes OS installation medium that you used to install Qubes OS if you still have it. Boot from it, select Rescue mode and enter the console.
2 Likes
@phirip please ignore my comments. The reasons are:
echo $somethingwas a suggestion for formatting your forum posts, feel free to ignore it- GRUB is the boot loader that shows up before you enter your passphrase. Following @MellowPoison instruction could be better and easier!
2 Likes
It’s a normal message because you surely accept to allow for usb keyboard.
Never use dom0 for location of your backup. The partition is to small, you must use a large usb key or usb disk (around 100Go), mount it on an AppVM ( it could be a disposable if you want) then choose the location of your key to make your backup.
2 Likes
Thank you all for your answers. Sorry for the delay in replying.
I didn’t think it was a bad idea to use dom0 as a backup. The dom0 option was the default, and I thought it wouldn’t cause any problems because it was a test mode trial. I also knew that I needed a USB drive, but I didn’t know how to use it with qubes (I was going to ask how to do it after trying it out in test mode). If you don’t mind, please tell me how to mount and use a USB flash drive on the appvm. Also, can you tell me how to make a USB QUBE disposable? (Just make it a disposable cube?)
I’m talking about solving my error code. Hmm, if I needed another laptop, I was going to change the device anyway, so it might be faster to just install Qubes on my new laptop. The truth is, I put Qubes in my laptop and SSD (both are slow to boot). The error code is now on the laptop. These two are generally the same content, so if you can successfully recover on the SSD, it would be a waste, but I can throw away the laptop. Another reason is that resolving the error code seems more difficult than reverting Qubes from 0 to its current state. MellowPoison, I’m sorry for telling you so much, I may not use your method. However, I don’t want to throw away my laptop, so I’ll try my best. If you don’t mind, could you tell me more about how MellowPoison shows you how to do it?
If you don’t have anything of value in your current Qubes OS, then it’d easier for you to just reinstall.
If you want to recover the OS, then you can mount the dom0 root partition from Live Linux OS like this:
1 Like