[SOLVED] sda has a holder...

[justinclift]

there's a ~ symbol at the end of your command that should not be there.

Ugh, I didn't spot that. Yeah, that'd explain the permission denied thing. No permission to create arbitrary nodes in the /sys device tree, even for the root user.

 

[wond]

Solution once and for all to all those "disk is busy" "disk has holder" disk has....."

root@pve01:~# sgdisk --zap-all /dev/sdx
root@pve01:~# readlink /sys/block/sdx
../devices/pci0000:00/0000:00:01.1/0000:01:00.0/host5/port-5:10/end_device-5:10/target5:0:10/5:0:10:0/block/sdx
root@pve01:~# echo 1 > /sys/block/sdx/device/delete
root@pve01:~# echo "- - -" > /sys/class/scsi_host/host5/scan

Last line is build using hostid from the readlink output, hence highlighted.

This solves the pesky problem! The disk can now be wiped.

Amazing!!! It works! Thanks

 

[djfreak]

Hah!

Got the holder removed by using:

lsblk -> gives you a long ID starting with "ceph-"
dmsetup remove <ID beginning with "ceph">

Just like that. So easy.

This worked perfectly for me thank you.

 

[herrderflammen87]

Was just fiddeling around and came up with the following:

lsblk -r | awk '/ceph--[a-f0-9-]*/ {print $1}' | sed 's/^`-//' | xargs -I {} sudo dmsetup remove "{}"

In sum I had to do the following:

systemctl stop ceph-mon.target
systemctl stop ceph-mgr.target
systemctl stop ceph-mds.target
systemctl stop ceph-osd.target
rm -rf /etc/systemd/system/ceph*
killall -9 ceph-mon ceph-mgr ceph-mds
rm -rf /var/lib/ceph/mon/  /var/lib/ceph/mgr/  /var/lib/ceph/mds/
pveceph purge
apt purge ceph-mon ceph-osd ceph-mgr ceph-mds
apt purge ceph-base ceph-mgr-modules-core
rm -rf /etc/ceph/*
rm -rf /etc/pve/ceph.conf
rm -rf /etc/pve/priv/ceph.*

reboot

lsblk -r | awk '/ceph--[a-f0-9-]*/ {print $1}' | sed 's/^`-//' | xargs -I {} sudo dmsetup remove "{}"

sgdisk --zap-all /dev/nvme0n1
sgdisk --zap-all /dev/nvme1n1

wipefs -fa /dev/nvme0n1
wipefs -fa /dev/nvme1n1

 

[Snackable Bytes]

Hi,
if the disk is actively in use, it cannot be cleanly wiped (the old user might still think it owns the disk afterwards...). For the LVM disks, check the output of pvsand remove the volume groups on the disks you want to wipe with vgremove. For the device-mapped disks, check with dmsetup ls and remove the mapping with dmsetup remove.

Thank you! This fixed my issue!

 

[BloodyIron]

So I found out how to fix this.

View attachment 68689

I just navigated to the LVM section under disks and deleted the entries that corresponded with the disks that were throwing the errors. Simple enough.

This method (with the "More" menu top right) worked for me! I did the CLI stuff earlier in the thread but tried this method again (webGUI) and it worked "better" for me

 

[RedJohn85]

Hola!

I tried:
sgdisk --zap-all /dev/sde

and it replied this:

Problem opening /dev/sde for reading! Error is 6.
Problem opening '' for writing! Program will now terminate.
Warning! MBR not overwritten! Error is 2!

It's like it's not connected, even though lsblk shows it's there

and when I click wipe in the proxmox GUI, the error is:
error wiping '/dev/sde': wipefs: error: /dev/sde: probing initialization failed: No such device or address

An I can't find anything similar on internet...

This all began when I cloned a 120GB SSD with a ProxMox installation to a 240GB SSD, the process completed flawlessly. I later decided to repurpose the 120GB SSD exclusively for ISOs and templates on the same system, so I attempted to wipe it. That's when the following error occurred:

error wiping '/dev/sde': wipefs: error: /dev/sde: probing initialization failed: No such device or address

I then zeroed the drive using Windows. It functions perfectly under both Windows and Ubuntu — I can read, write, and copy files at full speed with no issues.

However, when I attempt to use it in ProxMox, although the drive appears in lsblk, any operation against it fails with the same message:
"No such device or address."

To troubleshoot further, I even performed a fresh installation of the OS directly onto the 240GB SSD, thinking it might resolve any underlying issues. Unfortunately, it made no difference.

- What can it be?
- What can I do?
- Frustration at maximun...

 

[fiona]

Hi,

Hola!

I tried:
sgdisk --zap-all /dev/sde

and it replied this:

Problem opening /dev/sde for reading! Error is 6.
Problem opening '' for writing! Program will now terminate.
Warning! MBR not overwritten! Error is 2!

It's like it's not connected, even though lsblk shows it's there

and when I click wipe in the proxmox GUI, the error is:
error wiping '/dev/sde': wipefs: error: /dev/sde: probing initialization failed: No such device or address

An I can't find anything similar on internet...

This all began when I cloned a 120GB SSD with a ProxMox installation to a 240GB SSD, the process completed flawlessly. I later decided to repurpose the 120GB SSD exclusively for ISOs and templates on the same system, so I attempted to wipe it. That's when the following error occurred:

error wiping '/dev/sde': wipefs: error: /dev/sde: probing initialization failed: No such device or address

I then zeroed the drive using Windows. It functions perfectly under both Windows and Ubuntu — I can read, write, and copy files at full speed with no issues.

However, when I attempt to use it in ProxMox, although the drive appears in lsblk, any operation against it fails with the same message:
"No such device or address."

To troubleshoot further, I even performed a fresh installation of the OS directly onto the 240GB SSD, thinking it might resolve any underlying issues. Unfortunately, it made no difference.

- What can it be?
- What can I do?
- Frustration at maximun...

are there any messages in the system logs/journal around the time of the issue? What kernel version are you using (e.g. you can check by running pveversion).

 

[ghusson]

Hola!

I tried:
sgdisk --zap-all /dev/sde

and it replied this:

Problem opening /dev/sde for reading! Error is 6.
Problem opening '' for writing! Program will now terminate.
Warning! MBR not overwritten! Error is 2!

It's like it's not connected, even though lsblk shows it's there

and when I click wipe in the proxmox GUI, the error is:
error wiping '/dev/sde': wipefs: error: /dev/sde: probing initialization failed: No such device or address

An I can't find anything similar on internet...

This all began when I cloned a 120GB SSD with a ProxMox installation to a 240GB SSD, the process completed flawlessly. I later decided to repurpose the 120GB SSD exclusively for ISOs and templates on the same system, so I attempted to wipe it. That's when the following error occurred:

error wiping '/dev/sde': wipefs: error: /dev/sde: probing initialization failed: No such device or address

I then zeroed the drive using Windows. It functions perfectly under both Windows and Ubuntu — I can read, write, and copy files at full speed with no issues.

However, when I attempt to use it in ProxMox, although the drive appears in lsblk, any operation against it fails with the same message:
"No such device or address."

To troubleshoot further, I even performed a fresh installation of the OS directly onto the 240GB SSD, thinking it might resolve any underlying issues. Unfortunately, it made no difference.

- What can it be?
- What can I do?
- Frustration at maximun...

What is the output of :
hdparm -z /dev/sde