Question "block sectors" in "Surface Test" - reserve area for bad blocks? how many blocks have already been placed in the reserve area?

[krikunEWZ]

Hello everyone!

In the program "Hard Disk Sentinel" in the test "Surface Test" -> "view" -> "information" -> block = XXX sectors
YYY mb
S.M.A.R.T. - clean. (maybe it was reset)
Column "offset" = 0 (maybe the values were changed by the seller before sending the goods to me. I can't say for sure.)

Question #1:
XXX and YYY - a reserve area for bad blocks or are these the bad blocks themselves? Or neither? A factory defect?

Question #2:
Is it possible to find out how many blocks have already been placed in the reserve area? Provided that S.M.A.R.T. is reset, and in general traces of activity are carefully hidden.

I pass all the standard tests on the disk, but "block sectors" confuses me. There are already 3 TB disks with the same number of "block sectors". At the same time, all tests give excellent results.

Thanks in advance and good mood to everyone!



4 images

https://imgur.com/a/e69NU0W

View: https://imgur.com/a/e69NU0W

 

[kerberos_20]

one block is that one square on image and each that visual block contains 586 096 sectors
one sector holds 512 bytes
so that makes it 3 000 592 986 624 bytes
not all space is user available, but 3TiB should be there

there is no reserve area, if blocks gets bad, it will be reallocated somewhere else and would be blocked, partition size would be also reduced

hmm technically, if you have it formated with 4096 cluster size, that would make only single sector unused, but dont worry, if failures happen, partition will dinamically resize 😉

 

[krikunEWZ]

kerberos_20​

Thanks for answering question #1! Very valuable information!I didn't understand part of question #2.

reallocated somewhere else

Isn't this the same "torn area"? We're talking about the same thing, I hope.
You don't have to describe it - I've already read very detailed answers to other users' questions about how bad blocks are redistributed to the reserve area. The best method is initialization, and after that the bad blocks will no longer be visible to any test. They are already in the reserve area. To which we, ordinary users, have no access at all.

I wonder if it is possible to find out how many broken blocks have already been sent there and how much space is left in reserve for them?

 

[kerberos_20]

kerberos_20​

Thanks for answering question #1! Very valuable information!I didn't understand part of question #2.


Isn't this the same "torn area"? We're talking about the same thing, I hope.
You don't have to describe it - I've already read very detailed answers to other users' questions about how bad blocks are redistributed to the reserve area. The best method is initialization, and after that the bad blocks will no longer be visible to any test. They are already in the reserve area. To which we, ordinary users, have no access at all.

I wonder if it is possible to find out how many broken blocks have already been sent there and how much space is left in reserve for them?

even from factory there could be already few blocked "invisible" sectors, only with low level format you could see how many are there, otherwise s.m.a.r.t. will report how many are bad through that "reallocated count", or that surface test would show it aswell, as it can retest already marked bad sectors

bad sectors would be visible, they wont go invisible, OS just wont use it

reallocation happens on visible sectors, meaning, sector count wont decrease from what you see now, just available sectors for data will drop

 

[krikunEWZ]

керберос_20 ​

Exactly, the disk surface test shows ideal results. (I'll try again on a disk where initialization found and fixed dozens of sectors).
Low-level formatting also doesn't take bad sectors into account. Maybe it's worth trying too - i see the results.

The task is to determine whether I'm being deceived.

Thanks for your responsiveness!