R4.3 usb mounting

General Discussion
1

When I try to attached a usb to a running debian cube I get the message

“error mounting /dev/xdvi1 at /media/user/48C0B6407C3719E9 wrong file type, bad option, bad superblock on /dev/xvdi missin cope page”

Any suggestions would be appreciated.

2

Do you know what file system is on that USB drive?

Please run both lsblk and lsblk --fs inside that qube after attaching the USB drive and post the results here.

1 Like
3

Thank you for your reply. post results are:

user@work: $lsblk –fs

xvda

xvda1 vfat FAT16 EFI ASA2-7299

xvda2

xvda3 ext4 1.0 2864b5f8-39b3-4502-a02f-42867dcb69de 12.4G 31%/

/home

/user/local

/rw

xvdc

xvdc1 swap 1 95a252d3-65b6-4d1e-823b-88f5cd95d7ac [SWAP]

xvd3

xvdd ext3 1.0 fe83fccd-b313-4ae7-a490-11bb9dffa624

xvdi

xvdi1 ext4 1.0 c7dc66ba-05f7-40a9-829b-6b54c1d88c54 26.8G 0%

/media/user/c7dc66ba-05f7-40a9-829b-6b54c1d88c54

4

user@work:$lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS

xvda 202:0 1 20G 0 disk

xvda1 202:1 1 200M 0 part

xvda2 202:2 1 2M 0 part

xvda3 202:3 1 19.8G 0 part/

xvdb 202:16 1 2G 0 disk /var/spool/cron

/home

/usr/local

/rw

vxdc 202:32 1 10G 0 disk

xvdc1 202:33 1 1G 0 part [SWAP]

xvdc3 202:35 1 9G part

xvdd 202:48 1 725.5M 1 disk

xvdi 202:128 1 28.9G 0 disk

xvdi1 202:129 1 28.9G 0 part /media/user/c7dc66ba-05f7-40a9-829b-6b54c1d88c54

5

From this output it looks as if your removable drive is already mounted at /media/user/c7dc66ba-05f7-40a9-829b-6b54c1d88c54

6

Did he manually set mounting point earlier, maybe? in fstab or some other way…

7

Fellows: Thanks for the comments but:

A- I did not alter fstab

B- I did not mount anything but followed the procedure to attach the usb to qube work

C- Is there some way the usb could mount itself as part of the attachment process?

The only issues during the bare install install on a Lenovo p72 machine was:

Error:start failed:internal error:Unable to reset pci device 0000:00:1f.6:no FLR,PM reset or bus reset available, see /var/log/libvirt/libxl/libxl-driver.log for details”

and this was handled by “configure strict reset for pci devices” under setting in sys-net for the specific pci involved