HDD/Partition initialization problems

[Jocko]

Ok I did not understand you own both models (there is no fan on a nwsp2);

So I think you have to wait fvdw so that he compiles wipefs. This will allow to delete manually the zombies fs on sda8

[jaker]

Ok. I see. Wipefs doesn't seem to be readily available. I'll wait for it.

[fvdw]

That will be in the course of next week I am a few days on travel, sorry to keep you waiting

[jaker]

Have a nice trip

[fvdw]

attached wipefs from util-linux-2.30
To be installed in /usr/sbin (and make executable with chmod)

[Jocko]

Ok

After installing, run the command

Code: Select all

wipefs /dev/sda8

to list all fs offsets detected by blkid

@fvdw
Note: I do not understand why my dd commandline did not do the job :scratch

[fvdw]

@fvdw
Note: I do not understand why my dd commandline did not do the job :scratch

This probably is because you only have filled the partition with zerosbut not the info stored in the partition table. I need to check where file system on a partition is stored

[Jocko]

:doh
You are right !!!
Information should be stored on the first sector of the extended partition

[fvdw]

I found this

File systems all store information about themselves, often with some form of signature so that they can be identified. In Ext4’s case, the signature is 0xEF53 at offset 0x438, which you can see with od:

$ od -A x -x -j 1080 -N 2 /dev/<your device>
000438 ef53
00043a
This signature is part of the superblock, which contains information such as the overall size of the file system, the features it supports (e.g. whether it has a journal, uses extents, etc.), whether it’s clean or not...

For Ext4 you’ll find a description of the on-disk layout on the Ext4 wiki. Other file systems have similar documentation. You can find other signatures by reading the file systems magic file used by file.

Seems to be part of the superblock, then indeed you would expect that dd should be able te remove but remember there are smultiple superblocks. Did you overwrite them all?

[Jocko]

Did you overwrite them all?

Nope...
But I would expect libblkid does not use the backup superblocks as long as you do not overwrite the first superblock :scratch