Thanx for that. Strange thing now.
I tried looking at it with fdisk as suggested, though xvdi is no longer there? Can't figure out why, anyway, when I go to attach/detach block devices I now see: md126p5 md126 They are both also accessible via fdisk but what is bugging me is that I have these two disks setup via hardware RAID? shouldn't they show up as one disk? Since I don't have any data on these disks I tried partitioning one so now I have this when I print the part table: Disk /dev/md126: 1.8 TiB, 2000381018112 bytes, 3906994176 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x89e5c39e Device Boot Start End Sectors Size Id Type /dev/md126p1 16065 3907024064 3907008000 1.8T f W95 Ext'd (LBA) /dev/md126p5 16128 3907024064 3907007937 1.8T 83 Linux I appologise as this is perhaps getting into non-qubes territory but help would be apprecaited (as the uplimate goal is making this RAID1 setup available to some of my larger appVMs and local backups). Thanks in advance (again!) On Fri, May 19, 2017 at 5:58 PM, Unman <un...@thirdeyesecurity.org> wrote: > On Fri, May 19, 2017 at 03:07:40PM -0400, Gaiko Kyofusho wrote: > > On Thu, May 18, 2017 at 3:10 PM, Unman <un...@thirdeyesecurity.org> > wrote: > > > > > On Mon, May 15, 2017 at 11:17:57PM -0400, Gaiko Kyofusho wrote: > > > > I managed (with help from qubes-users) to setup secondary storage on > > > > another computer but I am having trouble with my current computer. > > > > > > > > It (they) are two drives setup with hardware raid, I partd/formated > > > (ext4) > > > > them as one raid drive which seemd to go ok. Qubes "sees" it, > actually it > > > > saw both drives for awhile but now only sees one (don't know what I > did > > > > there) but now when I try to attach it, it qubes vm manager shows it > > > > attached but it doesn't seem to be accessible from things like > nautilus? > > > I > > > > assume I just need to partition/setup as lvm/encrupt or something > like > > > that > > > > but am unsure how to go about it correctly? I'd be happy to post some > > > logs > > > > or something but am not sure where to go to get them? > > > > > > When you attach the drive to a qube, open a terminal in the qube and > > > run dmesg. Look at the contents of /dev/ and see what xvd* devices are > > > there. If you have attached the whole drive you would expect to see > > > /dev/xvdi, and associated partitions. > > > > > > You haven't said what template you are using, but it is possible that > > > you will have to manually mount the device/partition. > > > > > > unman > > > > > Thanks for the reply. I am not sure I 100% follow you (noobness). Other > > devices do show up, here is what I got: > > > > [user@personal ~]$ cd /dev/ > > [user@personal dev]$ ls xvd* > > xvda xvdb xvdc xvdc1 xvdc2 xvdd xvdi > > > > Do you mean like xvdi1 xvdi2 etc? > > > > As for template, sorry about that, I have tried both the fedora-24 and > > debian-9 templates (the above is output from a fed appvm) > > > > I generally got mounting partitions but that does lead me to two > questions: > > #1 I assume I need to see more than just xvdi? (like partition numbers > like > > i do for xvdc?) > > #2 would I have to manually mount it on each appvm everytime I want to > use > > it? (perhaps not a huge deal as I eventually want to have it permantly > used > > by 2-3appvms and no others so I assume that would involve some fstab > > tinkering?) > > I dont know if you attached the drive or a partition - if just the > latter then you would only expect to see xvdi - Try mounting that and > see what happens. > Alternatively run fdisk or cfdisk /dev/xvdi and see what is reported. > > You can mount these during qube startup from /rw/config/rc.local or > alternatively use bind-dirs to have a per-qube fstab. (Check the docs on > bind-dirs) > > unman > -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAGpWZxPm1PUmtW%2B5o5-bD6phNZKE-%2BnBtXGp2%3DQ7E-iw1zDF4g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
