On Tue, Aug 28, 2018 at 04:45:03PM -0500, Ward Family wrote: > Also tried attaching the partition with the same result. It's still saying > that > > "special device /dev/xvdi does not exist" (or xvdi1 as the case may be) > > This recurs across a variety of usb external devices, including those > without partitions. > > On Mon, Aug 27, 2018 at 8:10 AM awokd <aw...@danwin1210.me> wrote: > > > On Mon, August 27, 2018 11:35 am, Ward Family wrote: > > > Using fdisk -l in sys-usb (prior to attaching elswhere) produces: > > > Disk /dev/sda: 28.7 GiB, 30752000000 bytes, 60062500 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: 0x00000000 > > > > > > > > > Device Boot Start End Sectors Size Id > > > Type > > > /dev/sda1 32 60062499 60062468 28.7G c W95 > > > FAT32 (LBA) > > > > That looks normal. Try attaching just the partition instead: > > qvm-block attach usb1 sys-usb:sda1 > > > > Attaching the whole device might have resulted in the partition ending up > > on /dev/xvdi1 instead. Running qvm-block by itself after the attach should > > tell you what device it's on. > > > > > >
Please don't top post. Dod you check the logs on sys-usb to make sure that the process has not crashed there? -- 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/20180829123022.sgoo4h7tdgsdry7f%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
