Hello fellow freebsd users!
I have a doozy! A friend of mine recently started his own homelab. He acquired a bunch of HGST 1.2TB 2.5" SAS spinning rust drives for his truenas setup. He said he could not figure out how to get them formatted in 512 block size with youtube tutorials, so he tried the following from a freebsd thread via his truenas core shell prompt:
He said it worked, and proceeded to to this to the other 15 drives he had! (yeah I know noob error but he is learning!) however, to his horror, when he went to build the array the next day after they all completed, the drives will simply give input/output error if he tried to use the "wipe" command in truenas core.
After a week of forums, working with other options, he gave up and handed the drives over to me to see what I could do.
For my test bench I have a supermicro server board with an LSI 9200 flashed to IT mode with a EMC DAE sas / sata jbod shelf
and dual boot into freebsd (latest) and ubunut (latest)
I took one of these HGST 1.2TB 2.5" SAS drives he attempted to format and popped it in as the only drive in my test jbod. It assigned as da0
In ubunutu I used my standard command for such drives:
it worked fine. however, I too could not partition the drive, I would slam into command line erros the same input/output error. Hmmm, so I am thinking that the drives needed zeroed before changing block size so I did the following in linux:
smartctl showed that I was back to 520 block size. So I ran:
it worked fine. however, I too could not partition the drive, I would slam into command line erros the same input/output error. Hmmm, so I am thinking that the drives needed zeroed before changing block size so I did the following in linux:
smartctl showed that I was back to 520 block size. So I ran:
It failed. giving the same input/output error. I switched over to freebsd and figured maybe I need to rerun in reverse what he did in camcontrol
So I did the follwing:
diskinfo showed that indeed it was at block size 520 and I was seeing a 1.2TB drive.
I attempted to run:
but it failed with input/output error.
So I ran
and it did not fail.
However, after finishing, I still get input/output error when attempting to wipe / partition etc.. the drive.
Anyone else have this issue??? The SED flag shows not set on the drives, so I am at a loss of why the heck I cannot simply reformat these drives!
thank you!
_DH
I have a doozy! A friend of mine recently started his own homelab. He acquired a bunch of HGST 1.2TB 2.5" SAS spinning rust drives for his truenas setup. He said he could not figure out how to get them formatted in 512 block size with youtube tutorials, so he tried the following from a freebsd thread via his truenas core shell prompt:
Code:
camcontrol cmd da1 -v -c "15 10 0 0 v:i1 0" 12 -o 12 "0 0 0 8 0 0:i3 0 v:i3" 512
camcontrol format da1 -q -y
He said it worked, and proceeded to to this to the other 15 drives he had! (yeah I know noob error but he is learning!) however, to his horror, when he went to build the array the next day after they all completed, the drives will simply give input/output error if he tried to use the "wipe" command in truenas core.
After a week of forums, working with other options, he gave up and handed the drives over to me to see what I could do.
For my test bench I have a supermicro server board with an LSI 9200 flashed to IT mode with a EMC DAE sas / sata jbod shelf
and dual boot into freebsd (latest) and ubunut (latest)
I took one of these HGST 1.2TB 2.5" SAS drives he attempted to format and popped it in as the only drive in my test jbod. It assigned as da0
In ubunutu I used my standard command for such drives:
Code:
sg_format -v --format --size=512 /dev/da
it worked fine. however, I too could not partition the drive, I would slam into command line erros the same input/output error. Hmmm, so I am thinking that the drives needed zeroed before changing block size so I did the following in linux:
Code:
sg_format -v --format --size=520 /dev/da0
Code:
dd if=/dev/zero of=/dev/da0 bs=1m count=1
it worked fine. however, I too could not partition the drive, I would slam into command line erros the same input/output error. Hmmm, so I am thinking that the drives needed zeroed before changing block size so I did the following in linux:
Code:
sg_format -v --format --size=520 /dev/da0
Code:
dd if=/dev/zero of=/dev/da0 bs=1m count=1
So I did the follwing:
Code:
camcontrol cmd da1 -v -c "15 10 0 0 v:i1 0" 12 -o 12 "0 0 0 8 0 0:i3 0 v:i3" 520
camcontrol format da0 -q -y
diskinfo showed that indeed it was at block size 520 and I was seeing a 1.2TB drive.
I attempted to run:
Code:
dd if=/dev/zero of=/dev/ada2 bs=1m count=1
So I ran
Code:
sysctl kern.geom.debugflags=0x10 then sysctl kern.geom.debugflags=0x10
However, after finishing, I still get input/output error when attempting to wipe / partition etc.. the drive.
Anyone else have this issue??? The SED flag shows not set on the drives, so I am at a loss of why the heck I cannot simply reformat these drives!
thank you!
_DH