broken HDD after format change from 512 to 4096 4kn

[payback007]

Hi all,


I used the SeaChest-Software on Linux system to fastformat from 512 to 4kn on a new Seagate Exos X16 10TB HDD. The topic was working for 2v4 brand new HDDs.

But now 2 HDD seem to be fully broken.


Following commands I used:


SeaChest_Lite --scan


SeaChest_Lite --device /dev/sg... --showSupportedSectorSizes
512 and 4096 was reported

SeaChest_Lite --device /dev/sg... --setSectorSize 4096 --confirm ...

Change was reported successfully, I waited some time until no more activities on the HDD an rebooted the system. Tested it also with the SeaChest_utilities, same effect on one of the other HDDs.

After that the HDD seem to be nor longer accessable. Lost MBR and GPT, gdisk is reporting several failures:

Warning! Read error 5! Misbehavior now likely!
Caution! After loading partitions, the CRC doesn't check out

Recovery/transformation command (? for help): e
Warning! This will probably do weird things if you've converted an MBR to
GPT form and haven't yet saved the GPT! Proceed? (Y/N): y
Warning! Read error 5! Misbehavior now likely!
Caution! After loading partitions, the CRC doesn't check out!

Recovery/transformation command (? for help): w
Warning! Main partition table overlaps the first partition by 34 blocks!
You will need to delete this partition or resize it in another utility.
Aborting write of new partition table.

Recovery/transformation command (? for help): v
Problem: The CRC for the main partition table is invalid. This table may be
corrupt. Consider loading the backup partition table ('c' on the recovery &
transformation menu). This report may be a false alarm if you've already
corrected other problems.
Caution: The CRC for the backup partition table is invalid. This table may
be corrupt. This program will automatically create a new backup partition
table when you save your partitions.
Warning! Main partition table overlaps the first partition by 34 blocks!
You will need to delete this partition or resize it in another utility.
Identified 3 problems!

Any idea how to fix it? Is a new or re-format possible?

 

[Samuel Tai]

Sorry, try Seagate support; although I suspect you've bricked your drives. This forum is for FreeNAS/TrueNAS.

 

[HoneyBadger]

Did you send the --setSectorSize command to a disk with data on it? That's a destructive command.

 

[payback007]

yes for sure, it also seemed to work, because I got message 4096 was successfully set. But obviously it did not in a right way and now the disks are unusable in truenas.

 

[HoneyBadger]

yes for sure, it also seemed to work, because I got message 4096 was successfully set. But obviously it did not in a right way and now the disks are unusable in truenas.

I would fully power cycle the devices first - hotswap is fine if your chassis supports it, just yank the drive, wait a few seconds, and replug. Otherwise, fully power down the system, go inside, remove the SATA/SAS power plug, wait a few seconds, then replug. Power back up and check the drive status, if it shows up then you should be able to erase and repartition.

 

[AlexGG]

The partition tables, both MBR and GPT, measure offsets in sectors. Once you change a sector size, the partition tables become incorrect, which produces the error messages you see. If you wipe the disk clean, writing zeros to all of it, and reboot, you will be able to re-partition the disk again as normal with any blank disk. Just be sure to write zeros to the correct disk. Writing zeros to disk fully and irretrievably destroys all data on it.

 

[Alex_K]

Were you able to reuse all these drives?

 

[diskdiddler]

Did you ever get these disks working again? @payback007