Still getting the same errors as everyone else. even after reboots, and running the format commands several times.
Jun 19 18:02:48 RivaUnraid kernel: blk_update_request: critical medium error, dev sdp, sector 4096 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jun 19 18:02:48 RivaUnraid kernel: Buffer I/O error on dev sdp, logical block 512, async page read
Any clue how to get these to run without the errors?
When I “sg_format --format --size=4096” without the --ffmt2 flag, canceled the format, rebooted and then --ffmt2, it formatted quickly and changed the Cluster Size. The hard drive worked for a year without issues.
I did the same thing to another hard drive and stashed it. Bought another 8tb drive to have a quickswap and finally decided to put that first drive in parity.
Parity started calculating and I got read errors on both 8tb hard drives. Just read errors, not write errors, only when making the parity.
Stopped everything, formatted the parity drive with the slow format, took 14 hours, did it again… old hard drive was giving reading errors, new hard drive was not. So I copied all the files over (no read errors there), formatted the data drive slowly, swapped the then-parity, now backup into the new data, put the old data into a new parity, started calculating parity again and no error so far, running for 2 hours.
In other words, doing the “hacky” quick format I performed worked as a regular array drive (never a single error on them), but doesn’t work for when using parity. Slow format was the only way to make them actually work.
tl;dr: quick format doesn’t seem worth it, at least not in the scenario where it doesn’t straight up work.
Firstly, a big thank you to all for helping with working out to format these Oracle drives to full capacity.
I myself have acquired some of the 10TB versions, which I managet to format by running the --size=4096 parameter. One issue I have found since, is that the SMART Health status is now showing some strange values. Has anyone else encountered something similar? I have run badblocks, which has come back clear, but SMART isn’t looking good. Screenshot below:
These are just warnings, and are most likely warnings from the custom Oracle firmware owing from the changes made. This particular combination is not defined in the T10 SCSI standards. You can safely ignore them.
Other than losing space, is there any benefit in leaving the drives at the 7.86tb size, do the extra parity bits help with sector/block recovery on the drive itself? Or does that require having a controller/software designed to take advantage of that parity?
Working on trying to get some of the 8tb drives to replace some aging 3tb drives in my Unraid server. So if there is an advantage to leaving the parity bits there, then I’m find with keeping them at 7.86 because that’s still more than double what I am replacing.
In the user guide for the hugo tool, under format there is an option for protection type (0,1,2,3) but it doesn’t say what the different types are. Is the default no protection?
Yep, default is 0 (disabled). Note that hugo’s fast format is also not meant to work with unlike sector sizes (e.g. 520 → 4096, or 512 w/protection enabled).
Did you change out sdX with the drive letter of choice? I just did this for 4 of the drives in my system and had no problems getting the full capability.
I have not done it yet, this is a long thread with various different attempts so I just was looking for confirmation of the correct commands to be ran - of course changing to the needed drive letter.
Did you run sg_format --format --size=4096 /dev/sdX or sg_format --format --fmtpinfo=0 /dev/sdX
Hi, hopefully someone here can help me… I’ve made a mistake. I have a Dell r510 with a perc H700 raid controller, I installed my 8tb sun HGST set it up as raid 0 and it was found in windows but was missing some capacity… I did a Hugo format in windows to 4k. Problem is now the drive isn’t being recognized anymore. Its showing up in the H700 bios but only as a 900gb drive… if i try to make a Raid 0 with the drive it fails. I’m not very good with Linux & obviously windows also LOL!.
Is it possible to format this drive again with Linux?
If so how do i get the drive recognized and ready to format back to 512b
Hello all. Looks like I am a year late as I see that the last message was posted in March of 2023.
I am having an issue formatting an HGST 8TB drive Model #HUH728080AL5201 (Netapp) The drive appears to be fine except for the fact that I am unable to format it from the ubuntu command line. I have tried both sg-utils and Hugo. I tried most if not all of the suggestions made here and elsewhere to no avail. Your time and assistance will be greatly appreciated. I hope that it is alright that I attached several screenshots to this post.
Thank you @stuffwhy I don’t mind listing the cli commands that I used in sg_util and Hugo if that will help. I have had another HGST Sun/Oracle SAS 8TB HUH7280805200 drive installed and had no issued formatting that.