[SOLVED] Node/VM with external USB Disk

vikozo

Renowned Member
May 4, 2014
781
30
93
suisse
www.wombat.ch
hello
i have a node and i wish to conect a 5TB Disk for movies.
I would like to crate a VM and add this External Disk to the VM so i will have more or less 5TB Space for Movies!
What would be the best way and format this disk for use?

have a nice day
vinc
 
Hello
i have connected the 4TB USB Disk with the Node.
in the VM i can't add it as a Harddrive, but i add it as usb device i can select it and it show the correct name.
Save and Stop and then Start
in the boot process it häng
Screenshot_20220414_064454.png
disconect the USB Disk it continues to boot
how to avoid this?
the boot Order in the VM Option is correct the USB Device is not active to boot from
any idea?
 
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 2T 0 disk /mnt/movies
sdb 8:16 0 8G 0 disk
├─sdb1 8:17 0 7G 0 part /
├─sdb2 8:18 0 1K 0 part
└─sdb5 8:21 0 975M 0 part [SWAP]
sdc 8:32 0 3.6T 0 disk

sdc would be the corrct Disk
------
# fdisk -l
show the disk but when it should list the information about sdc it hang, crtl-C is not helping to stop it. disconect the disk and fdisk finish. reconecting the disk and lsblk is not showing them again

--------------
# udevadm monitor
remove and reconect the usb Disk shows up and then fdisk will also work again
--------
# mkfs.ext4 /dev/sdc
did run without problem

how to add a UUID to this disk? or do usb Disk not have a UUID?
-----
and doing
lsblk

sometimes it show sdc later not then again, why this happen?

have a nice day
vinc
 
Hello
The USB DIsk ist visible with

# lsusb
Bus 002 Device 010: ID 059f:10c5 LaCie, Ltd Mobile Drive

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdc 8:32 0 3.6T 0 disk

fdisk -l
is not showing the sdc

# fdisk /dev/sdc

Welcome to fdisk (util-linux 2.36.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/sdc: Kein passendes Gerät bzw. keine passende Adresse gefunden
fdisk: cannot open /dev/sdc: No such device or address

so what i am doing wrong?

have a nice day
vinc
 
# mkfs.ext4 /dev/sdc
did run without problem
You did format that disk as if it was a floppy disk. This might/will work but it is really unusual.
fdisk -l
is not showing the sdc
Du did not create a partition table. So fdisk can not evaluate/show/edit it...

Also... "fdisk" is very, very old. Try cfdisk instead. Whatever you do with these tools you will destroy the current data on that disk. Use it to create a new and clean GPT and then a partition...

Good luck
 
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 2T 0 disk /mnt/movies
sdb 8:16 0 8G 0 disk
├─sdb1 8:17 0 7G 0 part /
├─sdb2 8:18 0 1K 0 part
└─sdb5 8:21 0 975M 0 part [SWAP]
sdc 8:32 0 3.6T 0 disk
root@fs-15:~# cfdisk /dev/sdc
cfdisk: cannot open /dev/sdc: Kein passendes Gerät bzw. keine passende Adresse gefunden
 
root@fs-15:~# cfdisk /dev/sdc
cfdisk: cannot open /dev/sdc: Kein passendes Gerät bzw. keine passende Adresse gefunden
Strange.

You said you did # mkfs.ext4 /dev/sdc successfully. Was it on a different computer? An on that one it worked fine? If not: try using that device on a different computer. Does it work?

Did you reboot the problematic computer in the near past? Maybe it helps. I have seen hanging/blocking USB on my DeskMini with Linux - and only a full power-cycle could resolve this.

Further on: unplug that USB disk; run journalctl -f in a visible terminal on the host; plug the disk in. Watch the terminal for hints...

Best regards
 
Hello @UdoB
This only worked one time since i can't again do it
mkfs.ext4 /dev/sdc successfully.

yes i rebootet the VM and it did hang at start

Apr 15 19:44:00 fs-15 kernel: usb 2-1: USB disconnect, device number 3 Apr 15 19:44:09 fs-15 kernel: usb 2-1: new high-speed USB device number 4 using xhci_hcd Apr 15 19:44:09 fs-15 kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=10c5, bcdDevice= 0.03 Apr 15 19:44:09 fs-15 kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 Apr 15 19:44:09 fs-15 kernel: usb 2-1: Product: Mobile Drive Apr 15 19:44:09 fs-15 kernel: usb 2-1: Manufacturer: LaCie Apr 15 19:44:09 fs-15 kernel: usb 2-1: SerialNumber: 00000000NL6F8S54 Apr 15 19:44:09 fs-15 kernel: scsi host3: uas Apr 15 19:44:09 fs-15 kernel: scsi 3:0:0:0: Direct-Access LaCie Mobile Drive 0003 PQ: 0 ANSI: 6 Apr 15 19:44:09 fs-15 kernel: sd 3:0:0:0: Attached scsi generic sg2 type 0 Apr 15 19:44:09 fs-15 kernel: sd 3:0:0:0: [sdc] Spinning up disk... Apr 15 19:44:58 fs-15 kernel: .................. Apr 15 19:44:58 fs-15 kernel: sd 3:0:0:0: tag#2 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD Apr 15 19:44:58 fs-15 kernel: sd 3:0:0:0: tag#2 CDB: Test Unit Ready 00 00 00 00 00 00 Apr 15 19:44:58 fs-15 kernel: scsi host3: uas_eh_device_reset_handler start Apr 15 19:44:58 fs-15 kernel: usb 2-1: reset high-speed USB device number 4 using xhci_hcd Apr 15 19:44:59 fs-15 kernel: scsi host3: uas_eh_device_reset_handler success
 
Apr 15 19:46:13 fs-15 kernel: .not responding... Apr 15 19:46:13 fs-15 kernel: sd 3:0:0:0: [sdc] 7814037167 512-byte logical blocks: (4.00 TB/3.64 TiB) Apr 15 19:46:34 fs-15 kernel: sd 3:0:0:0: [sdc] Test WP failed, assume Write Enabled Apr 15 19:46:41 fs-15 kernel: sd 3:0:0:0: [sdc] Asking for cache data failed Apr 15 19:46:41 fs-15 kernel: sd 3:0:0:0: [sdc] Assuming drive cache: write through Apr 15 19:46:41 fs-15 kernel: sd 3:0:0:0: [sdc] Optimal transfer size 33553920 bytes Apr 15 19:46:41 fs-15 kernel: sd 3:0:0:0: [sdc] Spinning up disk... Apr 15 19:47:21 fs-15 kernel: ........ Apr 15 19:47:21 fs-15 kernel: sd 3:0:0:0: tag#1 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD Apr 15 19:47:21 fs-15 kernel: sd 3:0:0:0: tag#1 CDB: Test Unit Ready 00 00 00 00 00 00 Apr 15 19:47:22 fs-15 kernel: scsi host3: uas_eh_device_reset_handler start Apr 15 19:47:22 fs-15 kernel: usb 2-1: reset high-speed USB device number 4 using xhci_hcd Apr 15 19:47:22 fs-15 kernel: scsi host3: uas_eh_device_reset_handler success
 
Apr 15 19:49:20 fs-15 kernel: sd 3:0:0:0: [sdc] tag#7 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD Apr 15 19:49:20 fs-15 kernel: sd 3:0:0:0: [sdc] tag#7 CDB: Read(16) 88 00 00 00 00 00 00 00 00 07 00 00 00 01 00 00 Apr 15 19:49:20 fs-15 kernel: sd 3:0:0:0: [sdc] tag#6 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD Apr 15 19:49:20 fs-15 kernel: sd 3:0:0:0: [sdc] tag#6 CDB: Read(16) 88 00 00 00 00 00 00 00 00 06 00 00 00 01 00 00 Apr 15 19:49:20 fs-15 kernel: sd 3:0:0:0: [sdc] tag#5 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD Apr 15 19:49:20 fs-15 kernel: sd 3:0:0:0: [sdc] tag#5 CDB: Read(16) 88 00 00 00 00 00 00 00 00 05 00 00 00 01 00 00 Apr 15 19:49:20 fs-15 kernel: sd 3:0:0:0: [sdc] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD Apr 15 19:49:20 fs-15 kernel: sd 3:0:0:0: [sdc] tag#4 CDB: Read(16) 88 00 00 00 00 00 00 00 00 04 00 00 00 01 00 00 Apr 15 19:49:20 fs-15 kernel: scsi host3: uas_eh_device_reset_handler start Apr 15 19:49:21 fs-15 kernel: usb 2-1: reset high-speed USB device number 4 using xhci_hcd Apr 15 19:49:21 fs-15 kernel: scsi host3: uas_eh_device_reset_handler success Apr 15 19:49:51 fs-15 kernel: scsi host3: uas_eh_device_reset_handler start Apr 15 19:49:51 fs-15 kernel: sd 3:0:0:0: [sdc] tag#8 uas_zap_pending 0 uas-tag 5 inflight: CMD Apr 15 19:49:51 fs-15 kernel: sd 3:0:0:0: [sdc] tag#8 CDB: Read(16) 88 00 00 00 00 00 00 00 00 04 00 00 00 01 00 00 Apr 15 19:49:51 fs-15 kernel: sd 3:0:0:0: [sdc] tag#9 uas_zap_pending 0 uas-tag 6 inflight: CMD Apr 15 19:49:51 fs-15 kernel: sd 3:0:0:0: [sdc] tag#9 CDB: Read(16) 88 00 00 00 00 00 00 00 00 05 00 00 00 01 00 00 Apr 15 19:49:51 fs-15 kernel: sd 3:0:0:0: [sdc] tag#10 uas_zap_pending 0 uas-tag 7 inflight: CMD Apr 15 19:49:51 fs-15 kernel: sd 3:0:0:0: [sdc] tag#10 CDB: Read(16) 88 00 00 00 00 00 00 00 00 06 00 00 00 01 00 00 Apr 15 19:49:51 fs-15 kernel: sd 3:0:0:0: [sdc] tag#11 uas_zap_pending 0 uas-tag 8 inflight: CMD Apr 15 19:49:51 fs-15 kernel: sd 3:0:0:0: [sdc] tag#11 CDB: Read(16) 88 00 00 00 00 00 00 00 00 07 00 00 00 01 00 00 Apr 15 19:49:51 fs-15 kernel: usb 2-1: reset high-speed USB device number 4 using xhci_hcd
 
taken away formated with Laptop and added again to the Node USB- >> VM USB
shutdown the VM
start the VM
the process of booting go without problem like this

But a LSUSB or lsblk don't see the disk
 
found the Problem!
the Disk ist usb-C (3) the USB-Port on the Node was 1.2. Changing to a USB Port in the Back which is usb3 too. it worked just nice an perfect
have a nice day
vinc
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!