Just yesterday my Server that has been booting up faithfully for years all of a sudden stopped and showed the error:

Port 4 - HGST HDN72404OALE640 - SMART status bad. Backup, exchange, replace drive.

 

When I continue to boot it starts the array just fine and in UnRaid SMART reports are just fine. For the time being I disabled in the BIOS the check for SMART and it boots now just fine. Should I be concerned?

 

The problem is I can't correlate Port 4 to the disc as I have 3 other discs with the same labeling it is the part that follows that is different. I have sdf, sdg, sdh & sdi (the parity) that all start with the number that the BIOS SMART test reports.

 

I am open to suggestions but since I only check the UnRaid GUI should I correct this BIOS flagging or just keep an eye on the UnRaid SMART report?

36 minutes ago, One2go said:

For the time being I disabled in the BIOS the check for SMART

Does once enable then BIOS prompt each boot ? If yes, pls provide diagnostics.

Edited January 29, 20197 yr by Benson

1 hour ago, One2go said:

SMART status bad. Backup, exchange, replace drive.

Very likely there's a SMART failing now attribute, you should also see it on Unraid, in doubt post your diags.

There is only an enable or disable for all drives. When enabled it comes back with the error message and the prompt hit F1 to run BIOS setup. In the BIOS I hit F8 to bring up the boot menu and you can only select any of the drives that are detected once I select the USB drive it just boots up the UnRaid OS and everything is then normal as it always has been with no indication in the UnRaid GUI of a drive with a SMART status bad.

I belive BIOS haven't detect wrong, only detail SMART report may figure out which disk's item cause this.

Thanks for the help and I believe I found the drive that is failing it is the parity drive here is the log that was generated from the diagnostics.

 

 

HGST_HDN724040ALE640_PK2338P4H44EXC-20190129-1444.txt

Yep, failing now attribute:

 

  5 Reallocated_Sector_Ct   0x0033   001   001   005    Pre-fail  Always   FAILING_NOW 1952

 

2 minutes ago, One2go said:

I believe I found the drive that is failing

Yes

Edited January 29, 20197 yr by Benson

OK ordering a new drive now. Just replace the parity drive and then run a parity check or what else do I need to do?

 

In my array setup I do have 2 parity drives. 2nd one is fine.

Just replace and rebuild. （ not hotplug disk ）

No need parity check again in general.

Edited January 29, 20197 yr by Benson

Thanks for all the quick replies. On Thursday I will have a new drive same size. Now here are a few questions for replacing the suspect drive and I am running Unraid version 6.3.2

 

1. Do I need to unassign the old parity drive first or is just replacing the drive enough?

2. Do I need to preclear the new drive first?

3. Or do I just take the old drive out replace it with the new drive and then after powering up the server just start the array, tick the box for starting the parity check.

 

Any help with an easy step by step procedure after powering down the server and replacing the parity drive would be appreciated.

 

Thanks

O2G

Power off, replace parity, power on, assign parity, start array to begin parity sync.

 

Using preclear or any other disk test utility is good to make sure disk is good before using it.