June 17, 20251 yr Hi,I have just picked up a old R730XD server and it has 16 x 3.5" HGST 0F27003 4Tb drives, but when I add it to my Unraid server it reports as being a HITACHI HUS72604CLAR3000 3Tb drive.There is some wrinting on the drive in marker pen saying 3Tb.What's going on here?
June 17, 20251 yr Community Expert The serial number as reported by Unraid does not match what is on that paper label! (Remember that anyone can print a label!!!!)
June 17, 20251 yr Community Expert I would run a SMART test (short one) and post it here. Will be interesting to compare the SMART to the label.
June 17, 20251 yr Author Could it be anything to do with these being SAS drives. I know HDPARM doesn't work properly with SAS drives so maybe UNRAID likewise cannot read them properly?
June 17, 20251 yr Author 7 minutes ago, ConnerVT said:I would run a SMART test (short one) and post it here. Will be interesting to compare the SMART to the label.Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF INFORMATION SECTION ===Vendor: HITACHIProduct: HUS72604CLAR3000Revision: N9C0Compliance: SPC-4User Capacity: 3,000,592,982,016 bytes [3.00 TB]Logical block size: 512 bytesLU is fully provisionedRotation Rate: 7200 rpmForm Factor: 3.5 inchesLogical Unit id: 0x5000cca25c3f08fcSerial number: K3H3NP2LDevice type: diskTransport protocol: SAS (SPL-4)Local Time is: Tue Jun 17 23:52:35 2025 BSTSMART support is: Available - device has SMART capability.SMART support is: EnabledTemperature Warning: Disabled or Not SupportedRead Cache is: EnabledWriteback Cache is: Disabled=== START OF READ SMART DATA SECTION ===SMART Health Status: OKCurrent Drive Temperature: 39 CDrive Trip Temperature: 60 CManufactured in week 38 of year 2018Specified cycle count over device lifetime: 50000Accumulated start-stop cycles: 46Specified load-unload count over device lifetime: 600000Accumulated load-unload cycles: 1995Elements in grown defect list: 0Vendor (Seagate Cache) information Blocks sent to initiator = 39210350280704Error counter log: Errors Corrected by Total Correction Gigabytes Total ECC rereads/ errors algorithm processed uncorrected fast | delayed rewrites corrected invocations [10^9 bytes] errorsread: 0 0 0 0 5847 416.687 0write: 0 0 0 0 70643 3316.168 0verify: 0 0 0 0 142824 332.254 0Non-medium error count: 0SMART Self-test logNum Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours)# 1 Background short Completed - 46716 - [- - -]# 2 Background short Completed - 46714 - [- - -]# 3 Background short Completed - 46714 - [- - -]# 4 Background short Completed - 46669 - [- - -]Long (extended) Self-test duration: 6 seconds [0.1 minutes]Background scan results log Status: scan is active Accumulated power on time, hours:minutes 46716:23 [2802983 minutes] Number of background scans performed: 652, scan progress: 18.08% Number of background medium scans performed: 652General statistics and performance log page: General access statistics and performance: Number of read commands: 2408620 Number of write commands: 2337119 number of logical blocks received: 6476890766 number of logical blocks transmitted: 813841561 read command processing intervals: 0 write command processing intervals: 0 weighted number of read commands plus write commands: 0 weighted read command processing plus write command processing: 0 Idle time: Idle time intervals: 3359026124 in seconds: 167951306.200 in hours: 46653.140Protocol Specific port log page for SAS SSPrelative target port id = 1 generation code = 3 number of phys = 1 phy identifier = 0 attached device type: SAS or SATA device attached reason: unknown reason: unknown negotiated logical link rate: phy enabled; 6 Gbps attached initiator port: ssp=1 stp=1 smp=1 attached target port: ssp=0 stp=0 smp=0 SAS address = 0x5000cca25c3f08fd attached SAS address = 0x544a8420246b8e06 attached phy identifier = 5 Invalid DWORD count = 0 Running disparity error count = 0 Loss of DWORD synchronization count = 0 Phy reset problem count = 0relative target port id = 2 generation code = 3 number of phys = 1 phy identifier = 1 attached device type: no device attached attached reason: unknown reason: power on negotiated logical link rate: phy enabled; unknown attached initiator port: ssp=0 stp=0 smp=0 attached target port: ssp=0 stp=0 smp=0 SAS address = 0x5000cca25c3f08fe attached SAS address = 0x0 attached phy identifier = 0 Invalid DWORD count = 0 Running disparity error count = 0 Loss of DWORD synchronization count = 0 Phy reset problem count = 0
June 17, 20251 yr Community Expert 9 minutes ago, ridley said:Could it be anything to do with these being SAS drives. I know HDPARM doesn't work properly with SAS drives so maybe UNRAID likewise cannot read them properly?Not unless Unraid can look up valid HGST model number, report them in a SMART test, and write on the drive with a Sharpie marker. 😜Best guess it is really a HUS72604CLAR3000 3TB drive, and it was mislabeled at some point. It is a "White Label" label, so potentially a RMA or manufacturer refurbished drive. (Nothing wrong with that, both of my servers are full of them).SMART doesn't show any real issues, other than the mismatch with the label and 5+ years of power on. Edited June 17, 20251 yr by ConnerVT
June 17, 20251 yr Community Expert Found this. You are welcome to go down the rabbit hole chasing it. https://forums.servethehome.com/index.php?threads/strange-hd-what-is-this-thing.35003/
June 18, 20251 yr Author 1 hour ago, ConnerVT said:Found this. You are welcome to go down the rabbit hole chasing it.https://forums.servethehome.com/index.php?threads/strange-hd-what-is-this-thing.35003/Thanks.I had read that thread before asking here.I cannot see why a clipped drive would report a different serial number though.The serial number returned by the drive is a 3Tb drive and the serial number on the label is for a 4Tb one. So unless the serial number was changed during a firmware flash, which seems unlikely I really don't know what's going on.2 hours ago, ConnerVT said:Found this. You are welcome to go down the rabbit hole chasing it.https://forums.servethehome.com/index.php?threads/strange-hd-what-is-this-thing.35003/Thanks for that.I read that before asking here, it's the closest thing that I could find alsom
June 18, 20251 yr Community Expert It is a 7 year old mystery. Unless you know someone who works at Hitachi (WD) handling non-standard processing of drives, we probably won't find an answer.Changing the serial number could be that they have a defined range of numbers they use for each model/size. Or maybe they wanted to start a fresh history record for the drive once it started its new life as a 3TB. Me? I would have put a new label on it. Perhaps someone forgot, or maybe that was their plan for some reason.The drive is old, small, and of questionable heritage. I don't know how much time I would commit to it.
June 22, 20251 yr Author Actually, I am not sure why on the original "Unassigned devices" screen shot that it reported a different serial number.On this one the serial numbers reported in "preclear" match those on the drive labels, and they are reported on WD website as being 4Tb but as you can see UNRAID says 3Tb and they were sold to me as 3Tb, the vendor says it was a "manufacturing fault", are these "clipped"? and is there anyway to flash them etc to get back to 4Tb?So, serial numbers match those on the label and are serial numbers for 4Tb drives, but the system reports them as 3Tb.Whatever the cause this is weird.smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.24-Unraid] (local build)Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF INFORMATION SECTION ===Vendor: HITACHIProduct: HUS72604CLAR3000Revision: N9C0Compliance: SPC-4User Capacity: 3,000,592,982,016 bytes [3.00 TB]Logical block size: 512 bytesLU is fully provisionedRotation Rate: 7200 rpmForm Factor: 3.5 inchesLogical Unit id: 0x5000cca25c4b9064Serial number: K3HAK8UBDevice type: diskTransport protocol: SAS (SPL-4)Local Time is: Sun Jun 22 14:47:32 2025 BSTSMART support is: Available - device has SMART capability.SMART support is: EnabledTemperature Warning: EnabledRead Cache is: EnabledWriteback Cache is: Disabled=== START OF READ SMART DATA SECTION ===SMART Health Status: OKCurrent Drive Temperature: 40 CDrive Trip Temperature: 60 CManufactured in week 38 of year 2018Specified cycle count over device lifetime: 50000Accumulated start-stop cycles: 58Specified load-unload count over device lifetime: 600000Accumulated load-unload cycles: 1559Elements in grown defect list: 0Vendor (Seagate Cache) informationBlocks sent to initiator = 6388000976011264Error counter log:Errors Corrected by Total Correction Gigabytes TotalECC rereads/ errors algorithm processed uncorrectedfast | delayed rewrites corrected invocations [10^9 bytes] errorsread: 0 106 0 106 25715027 646191.823 0write: 0 48 0 48 359395 152320.552 0verify: 0 5 0 5 48518 324.524 0Non-medium error count: 0SMART Self-test logNum Test Status segment LifeTime LBA_first_err [SK ASC ASQ]Description number (hours)# 1 Background short Completed - 46714 - [- - -]# 2 Background short Completed - 46713 - [- - -]# 3 Background short Completed - 46669 - [- - -]Long (extended) Self-test duration: 6 seconds [0.1 minutes]Background scan results logStatus: scan is activeAccumulated power on time, hours:minutes 46736:18 [2804178 minutes]Number of background scans performed: 120, scan progress: 5.75%Number of background medium scans performed: 120General statistics and performance log page:General access statistics and performance:Number of read commands: 4922116038Number of write commands: 380754529number of logical blocks received: 297501077460number of logical blocks transmitted: 1262093404755read command processing intervals: 0write command processing intervals: 0weighted number of read commands plus write commands: 0weighted read command processing plus write command processing: 0Idle time:Idle time intervals: 2190971181in seconds: 109548559.050in hours: 30430.155Protocol Specific port log page for SAS SSPrelative target port id = 1generation code = 3number of phys = 1phy identifier = 0attached device type: expander deviceattached reason: SMP phy control functionreason: unknownnegotiated logical link rate: phy enabled; 12 Gbpsattached initiator port: ssp=0 stp=0 smp=0attached target port: ssp=0 stp=0 smp=1SAS address = 0x5000cca25c4b9065attached SAS address = 0x500056b3025d90ffattached phy identifier = 11Invalid DWORD count = 0Running disparity error count = 0Loss of DWORD synchronization count = 0Phy reset problem count = 0relative target port id = 2generation code = 3number of phys = 1phy identifier = 1attached device type: no device attachedattached reason: unknownreason: power onnegotiated logical link rate: phy enabled; unknownattached initiator port: ssp=0 stp=0 smp=0attached target port: ssp=0 stp=0 smp=0SAS address = 0x5000cca25c4b9066attached SAS address = 0x0attached phy identifier = 0Invalid DWORD count = 0Running disparity error count = 0Loss of DWORD synchronization count = 0Phy reset problem count = 0 Edited June 22, 20251 yr by ridley
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.