Unable to add HDD to ZFS

JonazThern

Member
Sep 28, 2021
23
1
8
45
I'm trying to add a HDD for file storage, to be used in a Windows10 VM later on. I go to Datacenter -> Node -> Disks -> ZFS and try to add the HDD installed in the server, but I getthe following error:

command '/sbin/zpool create -o 'ashift=12' File-Storage /dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-WCC7K4XYK8NJ' failed: exit code 1
 
Try to run wipefs in CLI first or use the partitioning tool of your choice to destroy all partitions existing on that disk. Only if that disk is unpartitioned the GUI will allow you use it with ZFS. Or you could create your ZFS pool using CLI with zpool create -f -o 'ashift=12' File-Storage /dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-WCC7K4XYK8NJ to force it to use it even if that disk isn't empty but then you will need to add that pool later as a ZFS storage for your PVE.
 
Last edited:
Try to run wipefs in CLI first or use the partitioning tool of your choice to destroy all partitions existing on that disk. Only if that disk is unpartitioned the GUI will allow you use it with ZFS. Or you could create your ZFS pool using CLI with zpool create -f -o 'ashift=12' File-Storage /dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-WCC7K4XYK8NJ to force it to use it even if that disk isn't empty but then you will need to add that pool later as a ZFS storage for your PVE.

Am I doing something wrong?

root@redpill:~# zpool create -f -o 'ashift=12' Movie-Storage-1 /dev/sda/ata-WDC_WD40EFRX-68N32N0cannot resolve path '/dev/sda/ata-WDC_WD40EFRX-68N32N0'
root@redpill:~# ls /dev/sda
/dev/sda
root@redpill:~# zpool create -f -o 'ashift=12' Movie-Storage-1 /dev/sda/
cannot resolve path '/dev/sda/'
root@redpill:~#


I did "wipefs /dev/sad" first.
 
Am I doing something wrong?

root@redpill:~# zpool create -f -o 'ashift=12' Movie-Storage-1 dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0cannot resolve path '/dev/sda/ata-WDC_WD40EFRX-68N32N0'
root@redpill:~# ls /dev/sda
/dev/sda
root@redpill:~# zpool create -f -o 'ashift=12' Movie-Storage-1 /dev/sda/
cannot resolve path '/dev/sda/'
root@redpill:~#


I did "wipefs /dev/sad" first.
It should be "zpool create -f -o 'ashift=12' File-Storage /dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-WCC7K4XYK8NJ" and not "zpool create -f -o 'ashift=12' Movie-Storage-1 /dev/sda/ata-WDC_WD40EFRX-68N32N0".

Always make sure your path is correct before you try formating/wiping something so you don't wipe the wrong drive.
 
It should be "zpool create -f -o 'ashift=12' File-Storage /dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-WCC7K4XYK8NJ" and not "zpool create -f -o 'ashift=12' Movie-Storage-1 /dev/sda/ata-WDC_WD40EFRX-68N32N0".

Always make sure your path is correct before you try formating/wiping something so you don't wipe the wrong drive.

Ah, I thought "/disk/by-id/" ment my "/dev/sda/". What I get from not reading everything..sorry.

I put a bigger disk in, a 14TB instead of 4TB, and now I get the following:

root@redpill:~# zpool create -f -o 'ashift=12' Movie-Storage-1 /dev/disk/by-id/ata-WDC_WD40EFFX-68VBXN0_WD-9RJLAVC6C"
>

And nothing happens.
 
If there is no output that usually means a command completed successfully. You can run zpool status to see what pools are there and if they are healthy.
 
Is this copy-n-paste?
The single ' " ' at the end is a problem - it starts quoting. Simply remove it...

Best regards

No, the " in the end was remove in the CLI. I'm missing something crucial, probably something easy since I'm an idiot at this. Tried a few varieties now:

root@redpill:~# zpool create -f -o 'ashift=12' Movie-Storage-1 /dev/disk/by-id/ata-WDC_WD40EFFX-68VBXN0_WD-9RJLAVC6C
cannot resolve path '/dev/disk/by-id/ata-WDC_WD40EFFX-68VBXN0_WD-9RJLAVC6C'

root@redpill:~# zpool create -f -o 'ashift=12' Movie-Storage-1 /dev/sde
cannot label 'sde': try using parted(8) and then provide a specific slice: -3

root@redpill:~# zpool create -f -o 'ashift=12' Movie-Storage-1 /dev/sde/ata-WDC_WD40EFFX-68VBXN0_WD-9RJLAVC6C
cannot resolve path '/dev/sde/ata-WDC_WD40EFFX-68VBXN0_WD-9RJLAVC6C'
 
root@redpill:~# ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 9 Oct 24 16:15 ata-HL-DT-ST_DVDRAM_GUE1N_KVGK7RB2249 -> ../../sr0
lrwxrwxrwx 1 root root 9 Oct 24 18:55 ata-WDC_WD140EFFX-68VBXN0_9RJLAV6C -> ../../sde
lrwxrwxrwx 1 root root 10 Oct 24 16:15 dm-name-pve-root -> ../../dm-1
lrwxrwxrwx 1 root root 10 Oct 24 16:15 dm-name-pve-swap -> ../../dm-0
lrwxrwxrwx 1 root root 10 Oct 24 16:15 dm-uuid-LVM-lO3BmVO0oAdHaPOPENyd6HlZ2G01OLcXTDSbVD5WPmuzg2UA2nSowj0qd1NRU4uv -> ../../dm-0
lrwxrwxrwx 1 root root 10 Oct 24 16:15 dm-uuid-LVM-lO3BmVO0oAdHaPOPENyd6HlZ2G01OLcXZ2oPftFdZNs45Z7wRXsmJ1JCzlrXe1dk -> ../../dm-1
lrwxrwxrwx 1 root root 15 Oct 24 16:15 lvm-pv-uuid-X1JIz0-0wfp-VQAU-2igr-55mv-zMei-CoueWs -> ../../nvme1n1p3
lrwxrwxrwx 1 root root 13 Oct 24 16:15 nvme-eui.00080d020031b2ec -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Oct 24 16:15 nvme-eui.00080d020031b2ec-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Oct 24 16:15 nvme-eui.00080d020031b2ec-part9 -> ../../nvme0n1p9
lrwxrwxrwx 1 root root 13 Oct 24 16:15 nvme-eui.001b448b48cbc129 -> ../../nvme1n1
lrwxrwxrwx 1 root root 15 Oct 24 16:15 nvme-eui.001b448b48cbc129-part1 -> ../../nvme1n1p1
lrwxrwxrwx 1 root root 15 Oct 24 16:15 nvme-eui.001b448b48cbc129-part2 -> ../../nvme1n1p2
lrwxrwxrwx 1 root root 15 Oct 24 16:15 nvme-eui.001b448b48cbc129-part3 -> ../../nvme1n1p3
lrwxrwxrwx 1 root root 13 Oct 24 16:15 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_97HS113CTAST -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Oct 24 16:15 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_97HS113CTAST-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Oct 24 16:15 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_97HS113CTAST-part9 -> ../../nvme0n1p9
lrwxrwxrwx 1 root root 13 Oct 24 16:15 nvme-WDC_PC_SN730_SDBQNTY-512G-1001_21125G806986 -> ../../nvme1n1
lrwxrwxrwx 1 root root 15 Oct 24 16:15 nvme-WDC_PC_SN730_SDBQNTY-512G-1001_21125G806986-part1 -> ../../nvme1n1p1
lrwxrwxrwx 1 root root 15 Oct 24 16:15 nvme-WDC_PC_SN730_SDBQNTY-512G-1001_21125G806986-part2 -> ../../nvme1n1p2
lrwxrwxrwx 1 root root 15 Oct 24 16:15 nvme-WDC_PC_SN730_SDBQNTY-512G-1001_21125G806986-part3 -> ../../nvme1n1p3
lrwxrwxrwx 1 root root 9 Oct 24 16:15 usb-Generic-_USB3.0_CRW-CF_MD_201412031053-0:0 -> ../../sda
lrwxrwxrwx 1 root root 9 Oct 24 16:15 usb-Generic-_USB3.0_CRW-MS_201412031053-0:2 -> ../../sdc
lrwxrwxrwx 1 root root 9 Oct 24 16:15 usb-Generic-_USB3.0_CRW-SD_201412031053-0:1 -> ../../sdb
lrwxrwxrwx 1 root root 9 Oct 24 16:15 usb-Generic-_USB3.0_CRW-SD_MS_201412031053-0:3 -> ../../sdd
lrwxrwxrwx 1 root root 9 Oct 24 18:55 wwn-0x5000cca264e48666 -> ../../sde
lrwxrwxrwx 1 root root 9 Oct 24 16:15 wwn-0x5001480000000000 -> ../../sr0
 
so far there is only a single WD harddisk in the list. if you´re sure that it´s the right one (compare it with the orginal label), try the follow command:

zpool create -f -o 'ashift=12' Movie-Storage-1 /dev/disk/by-id/ata-WDC_WD140EFFX-68VBXN0_9RJLAV6C
 
so far there is only a single WD harddisk in the list. if you´re sure that it´s the right one (compare it with the orginal label), try the follow command:

zpool create -f -o 'ashift=12' Movie-Storage-1 /dev/disk/by-id/ata-WDC_WD140EFFX-68VBXN0_9RJLAV6C

New error, which in my world is progress ;)

root@redpill:~# zpool create -f -o 'ashift=12' Movie-Storage-1 /dev/disk/by-id/ata-WDC_WD140EFFX-68VBXN0_9RJLAV6C
cannot label 'sde': try using parted(8) and then provide a specific slice: -3
 
you can try the "wipe disk" button in the gui (server => disks) or run the follow command and cancel it after 10-15 seconds with "ctrl c"

shred -v /dev/disk/by-id/ata-WDC_WD140EFFX-68VBXN0_9RJLAV6C
 
you can try the "wipe disk" button in the gui (server => disks) or run the follow command and cancel it after 10-15 seconds with "ctrl c"

shred -v /dev/disk/by-id/ata-WDC_WD140EFFX-68VBXN0_9RJLAV6C

I'm starting to think that the drive is broken? I tried the "Wipe Disk", and it ticked 0-100% over and over like 10 times, and then the following error:

error wiping '/dev/sde': 209715200 bytes (210 MB, 200 MiB) copied, 49.8897 s, 4.2 MB/s
 
So, I replaced it with a HDD that I know works, and now it runs fine. Pool created without errors, so it looks like that HDD is broken.

Thanx for trying to help me, and sorry for taking up your time!!
 

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!