I am attempting to setup some secondary storage per https://www.qubes-os.org/doc/secondary-storage/ and when I run " sudo cryptsetup luksFormat --hash=sha512 --key-size=512 --cipher=aes-xts-plain64 --verify-passphrase /dev/sdc" I get "Device /dev/sbc doesn't exist or access denied". It's there in a dom0 terminal when I type "ls /dev/sb*" I am assuming sba is the boot raid1 and sbb is the ROM drive.
My boot drive is an SSD RAID1 on an Intel embedded controller, standard stuff. The drive I want to add is attached to an embedded LSI SAS controller. I can attach the sbc device to a VM easy enough but it seems I am missing a step to make it dom0 aware. I am running an up-to-date Qubes 4.x installed on a SuperMicro serverboard, Xeon something or other (4-core, 3.4GHz) with 32GB RAM (retired ESXi host). I think it is booting with GRUB. FULL DISCLOSURE: I am a *nix newbie really. I've played with embedded *nix, built my share of ESXi boxes and what not, but not really dug into the nuts and bolts of it like I've have been since installing Qubes, which I think is fantastic for its purpose. I want to commit to Qubes as my primary box but I really need to understand it first, especially, ahem, disaster recovery. I have not run a Linux desktop for any significant length of time prior to this either - mostly M$ (since the IBM model 5150), a wee bit of OS/2 Warp (the best multi-node PCBoard BBS host evah!) and a brief fling with the Mac OS before they went to Intel chips. Yes, I could just go buy a bigger pair of SSDs and restore a backup to them, but then I won't really learn anything and I'll be a wee bit poorer for it. Thanks. DG -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1242880289.44777.1581540738832.JavaMail.zimbra%40unseen.is.
