Firstly this is on 5.0 RC3. 

 

I recently had some drive issues, and ended up doing an RMA with Western Digital for a 1TB EARS with some read errors.  The drive I received in return was a 2.5 TB EZRX (very generous of WD to upgrade for me).  I started out with a 3 pass preclear that came up all good, and for kicks I decided to torture test the drive with a 4 pass destructive badblocks test (thx for the help WeeboTech).  Everything worked out great, zero errors on everything.

 

This morning I removed my old parity drive as it was only 2TB replaced with the larger 2.5TB and started a rebuild.  Not sure if this would be anything of concern, but Unmenu shows "Warning: Detected non-standard drive size - may contain and HPA.  Set hpa_ok attribute to 1 to ignore"  (.jpg http://img444.imageshack.us/img444/3417/unmenuwarning.jpg)

 

I have checked the syslog, and see no entries showing "atax.00: HPA detected: current xxxxxxxxxx, native xxxxxxxxxx"  (drive related syslog entries attached).  sdb in the log is the new 2.5tb drive.

 

Is this normal, and after my parity is rebuilt, and a reboot, will it show as normal?  Or should I stop the rebuild, reinstall the old parity, and or deal with this issue before time is wasted on a full rebuild? 

driverelatedsyslog.txt

Firstly this is on 5.0 RC3. 

 

I recently had some drive issues, and ended up doing an RMA with Western Digital for a 1TB EARS with some read errors.  The drive I received in return was a 2.5 TB EZRX (very generous of WD to upgrade for me).  I started out with a 3 pass preclear that came up all good, and for kicks I decided to torture test the drive with a 4 pass destructive badblocks test (thx for the help WeeboTech).  Everything worked out great, zero errors on everything.

 

This morning I removed my old parity drive as it was only 2TB replaced with the larger 2.5TB and started a rebuild.  Not sure if this would be anything of concern, but Unmenu shows "Warning: Detected non-standard drive size - may contain and HPA.  Set hpa_ok attribute to 1 to ignore"  (.jpg http://img444.imageshack.us/img444/3417/unmenuwarning.jpg)

 

I have checked the syslog, and see no entries showing "atax.00: HPA detected: current xxxxxxxxxx, native xxxxxxxxxx"  (drive related syslog entries attached).  sdb in the log is the new 2.5tb drive.

 

Is this normal, and after my parity is rebuilt, and a reboot, will it show as normal?  Or should I stop the rebuild, reinstall the old parity, and or deal with this issue before time is wasted on a full rebuild?

Don't worry about the warning from in unMENU, it is just because your disk has a size it does not recognize. (2.5TB drives are not common)