failed to wipe disk da1: operation not permitted '/dev/da1'

jcizzo

Explorer
Joined
Jan 20, 2023
Messages
79
having an issue that makes no sense. Yes, i'm new, trying to get through my first build.

i have truenas core installed across 2 ssds, and a 4 drive pool that i'd like to format as zraid1, however every time i try, i get the above error message.

the spinners are all working properly and non of them are partitioned/formatted in any way.

if i try to do a 'wipe', i get the same error message.

i found a thread that went all the way back to freenas in 201x that spoke about using 'gmirror' however there's no reference to where i'm supposed to run the commands and find the path to the drives. plus, my drives aren't mirrored, if that matters. this doesn't make sense. i've destroyed a pool. even if there was data on one of the drives, when i pull all 4 drives into a pool and create it from scratch, it should just wipe everything out, especially since it warns me that all data on the drives will be lost!

i just want to create a simple pool with 4 empty drives.. why is this so difficult?
 

Arwen

MVP
Joined
May 17, 2014
Messages
3,611
First, it is not intended to be difficult. However, safe guards that prevent you from destroying data are common, though not as common as they should be.

Next, please give a read to the Forum Rules, helpfully linked on all pages at the top, in red. Basically we need more information, like the hardware configuration, which should include disk vendor & model. Those Forum Rules contain helpful information on how to create a post that will get a response of help, not a request for more information.
 

jcizzo

Explorer
Joined
Jan 20, 2023
Messages
79
First, it is not intended to be difficult. However, safe guards that prevent you from destroying data are common, though not as common as they should be.

Next, please give a read to the Forum Rules, helpfully linked on all pages at the top, in red. Basically we need more information, like the hardware configuration, which should include disk vendor & model. Those Forum Rules contain helpful information on how to create a post that will get a response of help, not a request for more information.
sorry for not providing more info.. i took a screenshot of the error but forgot to upload it when i posted, which i'm pretty pissed at myself for because it's something that probably hasn't been looked into because it's not much of an issue until it is..

That being said, i was able to solve my problem and i will explain with the best of my ability.

the setup is as follows:
supermicro x10slq motherboard, flashed with the latest bios.
2 x 240GB ssds for boot/OS connected directly to the SATA ports on the motherboard.
4 x 1TB WD drives (spinners) connected to an LSI 9211 HBA card in IT mode (latest flashing).

none of the drives were partitioned, although that shouldn't matter because they'd be wiped upon adding to the pool.
when attempting to create a storage pool, i received the above error on two of the drives. using the "wipe" function resulted in the same error message.

Ultimately i was able to resolve the problem by restarting the system and booting with gparted.
i used gparted to delete all partitions.. oddly, on the two problematic drives, it gave an error saying basically "it couldn't figure out the drive.. it knew it was there but it couldn't make sense of it.. so go to the device menu and assign it a filesystem".. i assigned it msdos and all came up as it should've, without any partitions.. completely blank..

rebooted the nas and was able to add all drives successfully..

i apologize profusely for not being able to include pics. I'm sure others have had this problem and might think it's a bad drive when it's merely a partition problem.
 

Arwen

MVP
Joined
May 17, 2014
Messages
3,611
Glad you were able to get it solved. Good luck.


If I remember correctly, GPT has 2 partition tables, one at the beginning of the disk and a backup at the end of the disk. Perhaps the one at the end of the disk still existed and the software was confused. Using a blank MS-DOS partition table may have caused the software to ignore the 2nd GPT partition table.
 
Top