I/O Error on QNAP TS469U-SP internal drive

benalexau · Post by **benalexau** » Thu Sep 12, 2013 9:20 am

Hi

I have a TS469U-SP with 4 x Hitachi Ultrastar 7K4000 drives configured as a single RAID 5 volume. Today the QNAP reported:

[Harddisk 4] I/O error, sense_key=0xb, asc=0x0, ascq=0x0, CDB=88 00 00 00 00 01 ce a0 5c 58 00 00 00 08 00 00

In HDD Smart summary, the QNAP reports, "HDD I/O Status Abnormal". A "quick test" completed without finding any errors. A "full test" is running but incomplete. A copy of the dmesg from an SSH session into the QNAP is below.

Any suggestions?

Thanks
Ben

Code: Select all

[242892.288133] ata10.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 frozen
[242892.288142] ata10.00: failed command: READ FPDMA QUEUED
[242892.288154] ata10.00: cmd 60/08:78:48:5e:a0/00:00:ce:01:00/40 tag 15 ncq 4096 in
[242892.288157]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[242892.288162] ata10.00: status: { DRDY }
[242892.288170] ata10: hard resetting link
[242892.749145] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[242892.753874] ata10.00: configured for UDMA/133
[242892.753883] ata10.00: device reported invalid CHS sector 0
[242892.753896] ata10: EH complete
[242938.288133] ata10.00: exception Emask 0x0 SAct 0x7e000000 SErr 0x0 action 0x6 frozen
[242938.288143] ata10.00: failed command: READ FPDMA QUEUED
[242938.288155] ata10.00: cmd 60/08:c8:58:5c:a0/00:00:ce:01:00/40 tag 25 ncq 4096 in
[242938.288158]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[242938.288163] ata10.00: status: { DRDY }
[242938.288168] ata10.00: failed command: READ FPDMA QUEUED
[242938.288179] ata10.00: cmd 60/08:d0:60:5c:a0/00:00:ce:01:00/40 tag 26 ncq 4096 in
[242938.288181]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[242938.288187] ata10.00: status: { DRDY }
[242938.288191] ata10.00: failed command: READ FPDMA QUEUED
[242938.288202] ata10.00: cmd 60/08:d8:68:5c:a0/00:00:ce:01:00/40 tag 27 ncq 4096 in
[242938.288204]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[242938.288210] ata10.00: status: { DRDY }
[242938.288214] ata10.00: failed command: READ FPDMA QUEUED
[242938.288225] ata10.00: cmd 60/08:e0:78:5c:a0/00:00:ce:01:00/40 tag 28 ncq 4096 in
[242938.288227]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[242938.288232] ata10.00: status: { DRDY }
[242938.288237] ata10.00: failed command: READ FPDMA QUEUED
[242938.288248] ata10.00: cmd 60/08:e8:80:5c:a0/00:00:ce:01:00/40 tag 29 ncq 4096 in
[242938.288250]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[242938.288255] ata10.00: status: { DRDY }
[242938.288260] ata10.00: failed command: READ FPDMA QUEUED
[242938.288271] ata10.00: cmd 60/08:f0:40:5c:a0/00:00:ce:01:00/40 tag 30 ncq 4096 in
[242938.288273]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[242938.288278] ata10.00: status: { DRDY }
[242938.288285] ata10: hard resetting link
[242938.748138] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[242938.752850] ata10.00: configured for UDMA/133
[242938.752861] ata10.00: device reported invalid CHS sector 0
[242938.752866] ata10.00: device reported invalid CHS sector 0
[242938.752871] ata10.00: device reported invalid CHS sector 0
[242938.752875] ata10.00: device reported invalid CHS sector 0
[242938.752880] ata10.00: device reported invalid CHS sector 0
[242938.752885] ata10.00: device reported invalid CHS sector 0
[242938.752898] sd 9:0:0:0: [sdd]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[242938.752905] sd 9:0:0:0: [sdd]  Sense Key : Aborted Command [current] [descriptor]
[242938.752913] Descriptor sense data with sense descriptors (in hex):
[242938.752916]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
[242938.752932]         00 00 00 00 
[242938.752938] sd 9:0:0:0: [sdd]  Add. Sense: No additional sense information
[242938.752946] sd 9:0:0:0: [sdd] CDB: Read(16): 88 00 00 00 00 01 ce a0 5c 58 00 00 00 08 00 00
[242938.752969] end_request: I/O error, dev sdd, sector 7761583192
[242938.752992] sd 9:0:0:0: [sdd]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[242938.752998] sd 9:0:0:0: [sdd]  Sense Key : Aborted Command [current] [descriptor]
[242938.753005] Descriptor sense data with sense descriptors (in hex):
[242938.753009]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
[242938.753023]         00 00 00 00 
[242938.753030] sd 9:0:0:0: [sdd]  Add. Sense: No additional sense information
[242938.753037] sd 9:0:0:0: [sdd] CDB: Read(16): 88 00 00 00 00 01 ce a0 5c 60 00 00 00 08 00 00
[242938.753056] end_request: I/O error, dev sdd, sector 7761583200
[242938.753068] sd 9:0:0:0: [sdd]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[242938.753073] sd 9:0:0:0: [sdd]  Sense Key : Aborted Command [current] [descriptor]
[242938.753080] Descriptor sense data with sense descriptors (in hex):
[242938.753084]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
[242938.753115]         00 00 00 00 
[242938.753124] sd 9:0:0:0: [sdd]  Add. Sense: No additional sense information
[242938.753131] sd 9:0:0:0: [sdd] CDB: Read(16): 88 00 00 00 00 01 ce a0 5c 68 00 00 00 08 00 00
[242938.753154] end_request: I/O error, dev sdd, sector 7761583208
[242938.753167] sd 9:0:0:0: [sdd]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[242938.753174] sd 9:0:0:0: [sdd]  Sense Key : Aborted Command [current] [descriptor]
[242938.753181] Descriptor sense data with sense descriptors (in hex):
[242938.753185]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
[242938.753202]         00 00 00 00 
[242938.753209] sd 9:0:0:0: [sdd]  Add. Sense: No additional sense information
[242938.753217] sd 9:0:0:0: [sdd] CDB: Read(16): 88 00 00 00 00 01 ce a0 5c 78 00 00 00 08 00 00
[242938.753238] end_request: I/O error, dev sdd, sector 7761583224
[242938.753250] sd 9:0:0:0: [sdd]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[242938.753256] sd 9:0:0:0: [sdd]  Sense Key : Aborted Command [current] [descriptor]
[242938.753264] Descriptor sense data with sense descriptors (in hex):
[242938.753268]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
[242938.753285]         00 00 00 00 
[242938.753292] sd 9:0:0:0: [sdd]  Add. Sense: No additional sense information
[242938.753300] sd 9:0:0:0: [sdd] CDB: Read(16): 88 00 00 00 00 01 ce a0 5c 80 00 00 00 08 00 00
[242938.753321] end_request: I/O error, dev sdd, sector 7761583232
[242938.753332] ata10: EH complete

QNAP_YH · Post by **QNAP_YH** » Fri Sep 13, 2013 6:05 am

Hi,

ata10 of TS469U-SP indicates Bay 4 and/or drive 4.
And I/O error, dev sdd, sector 7761583224, means your drive 4 w/ bad sector.
sda = drive 1, sdb = drive 2....

You have to replace your drive 4, please refer following compatibility list.
http://www.qnap.com/useng/index.php?sn=4085&lang=en-us
Please must refer note behind hard drives before purchasing.

benalexau · Post by **benalexau** » Fri Sep 13, 2013 6:55 am

Hi

QNAP_YH wrote:You have to replace your drive 4, please refer following compatibility list.

The disks in the NAS (and the NAS itself) are only 10 months old. They are Hitachi Ultrastars (with 5 year warranties) and appear on the compatibility list. I ran the QNAP "complete test" and it reported, "Status: Test completed and no errors found". There are no new errors in dmesg. So if I return this drive, is this dmesg alone enough to prove there is a problem? I don't want to lose redundancy (it's RAID 5) to return a drive that will be returned to me as no fault found. Is there some other test that can be run which will demonstrate a fault with the drive, as the quick test and complete test have failed to identify any issues?

Thanks
Ben

QNAP_YH · Post by **QNAP_YH** » Fri Sep 13, 2013 7:35 am

Hi,

The disks in the NAS (and the NAS itself) are only 10 months old

QNAP does't sell hard drives, if you bought QNAP w/ hard drives inside, it should be bounded by re-seller or distributor.

They are Hitachi Ultrastars (with 5 year warranties) and appear on the compatibility list

I believe it is under compatibility list, however, please give me the hard drive model#, so I can double check for you.

I ran the QNAP "complete test" and it reported, "Status: Test completed and no errors found"
In HDD Smart summary, the QNAP reports, "HDD I/O Status Abnormal"
s there some other test that can be run which will demonstrate a fault with the drive

As you described, SMART has shown "abnormal" on QNAP web interface, however the SMART exam result actually is from the firmware of hard drive,
which is from Hitachi hard drive firmware.
Of course, you can go to Hitachi's website to download their diagnose software, connect drive 4 on your PC and run "detail diagnose".
Using this method, you can get more accurate result than SMART.

Additional information, if you go to [Control Panel], [Storage manager], and physical disks, choose hard drive 4 and run [scan now].
It may show bad block information.

I don't want to lose redundancy (it's RAID 5) to return a drive that will be returned to me as no fault found

If I were you, I will backup my data first, then I will not worried about losing RAID5 redundancy during hard drive replacement window.

benalexau · Post by **benalexau** » Fri Sep 13, 2013 11:40 am

QNAP_YH wrote:I believe it is under compatibility list, however, please give me the hard drive model#, so I can double check for you.

I installed the Optware QPKG and then used Optware to install smartmontools. Results below (including model details):

Code: Select all

[~] # smartctl -d ata -a /dev/sdd
smartctl 5.40 2010-10-16 r3189 [i686-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     Hitachi HUS724040ALE640
Serial Number:    PK1361PAG9RHXV
Firmware Version: MJAOA3B0
User Capacity:    4,000,787,030,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Fri Sep 13 13:16:19 2013 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x85)	Offline data collection activity
					was aborted by an interrupting command from host.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		 (  24) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 255) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   084   084   016    Pre-fail  Always       -       398
  2 Throughput_Performance  0x0005   137   137   054    Pre-fail  Offline      -       78
  3 Spin_Up_Time            0x0007   100   100   024    Pre-fail  Always       -       502
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       8
  5 Reallocated_Sector_Ct   0x0033   092   092   005    Pre-fail  Always       -       316
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   121   121   020    Pre-fail  Offline      -       34
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       7106
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       7
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       208
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       208
194 Temperature_Celsius     0x0002   171   171   000    Old_age   Always       -       35 (Min/Max 23/44)
196 Reallocated_Event_Count 0x0032   084   084   000    Old_age   Always       -       427
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%      7096         -
# 2  Short offline       Completed without error       00%      7080         -
# 3  Short offline       Completed without error       00%      7080         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

As you described, SMART has shown "abnormal" on QNAP web interface, however the SMART exam result actually is from the firmware of hard drive, which is from Hitachi hard drive firmware.

What's puzzling is the smartctl result above does not show any errors either. I would have imagined whatever QNAP's web admin GUI is saying is coming from the drive's SMART feature, but it doesn't seem to be. The only two indications of a problem are the dmesg log posted earlier and the web admin GUI telling me "HDD I/O Status Abnormal". No quick test, full test, smartctl or new dmesg indicates an issue.

Of course, you can go to Hitachi's website to download their diagnose software, connect drive 4 on your PC and run "detail diagnose". Using this method, you can get more accurate result than SMART.

Only problem with that is I don't have Windows, and I don't have a workstation with a 6 GB/sec SATA interface in any event (only 3 GB). I am also reluctant to knowingly eliminate redundancy (by removing the drive from a production QNAP) just to run a test of a drive that doesn't seem to be that critical. Are there any commands or packages I can install on the QNAP to investigate this further? Past experience tells me if I ship this drive back to Hitachi without hard evidence of a problem, they'll just send it back to me with "no fault found" -- especially given I can't find a fault locally with any commands.

If I were you, I will backup my data first, then I will not worried about losing RAID5 redundancy during hard drive replacement window.

I have ongoing backups of important data with ElephantDrive (great interop with the QNAP BTW). I'd hate to see how long it takes to restore many hundreds of gigabytes over an Internet connection though!

Is there anything else I can try on the QNAP itself? Are you sure an I/O error is indeed a drive problem as opposed to a SATA interface issue? I read a few comments elsewhere that suggested I/O errors could be a faulty cable or connector. Does this seem plausible given what we're seeing here with no SMART errors?

QNAP_YH · Post by **QNAP_YH** » Fri Sep 13, 2013 2:54 pm

The only two indications of a problem are the dmesg log posted earlier and the web admin GUI telling me "HDD I/O Status Abnormal"
Are there any commands or packages I can install on the QNAP to investigate this further?

Please also try

Code: Select all

/etc/init.d/klogd.sh | grep error

and

Code: Select all

/etc/init.d/klogd.sh | grep ERROR

dmesg only contains logs after start-up, you can find more logs by klogd.sh

Did you also try bad block scan?
Go to [Control Panel], [Storage manager], and physical disks, choose hard drive 4 and run [scan now].

doktornotor · Post by **doktornotor** » Fri Sep 13, 2013 3:20 pm

benalexau wrote: What's puzzling is the smartctl result above does not show any errors either.

Did you even bother to read the SMART info?

Code: Select all

  5 Reallocated_Sector_Ct   0x0033   092   092   005    Pre-fail  Always       -       316
196 Reallocated_Event_Count 0x0032   084   084   000    Old_age   Always       -       427

You have 316 bad blocks there and triggered an attempt to reallocate them 427 times. The disk is sure like hell faulty and to be replaced! It absolutely does not matter that they are "only 10 months old". RMA it!

benalexau · Post by **benalexau** » Fri Sep 13, 2013 5:46 pm

doktornotor wrote:Did you even bother to read the SMART info?

Yes. I followed the first Google result for "smartmon tutorial" and it pointed me to the lines of my output which said, "SMART overall-health self-assessment test result: PASSED". Unfortunately I didn't read the lines you identified.

doktornotor wrote:You have 316 bad blocks there and triggered an attempt to reallocate them 427 times. The disk is sure like ** faulty and to be replaced! It absolutely does not matter that they are "only 10 months old". RMA it!

I really appreciate you interpreting the output for me. Thanks!

QNAP_YH wrote:Please also try
Code: Select all
/etc/init.d/klogd.sh | grep error
and
Code: Select all
/etc/init.d/klogd.sh | grep ERROR
dmesg only contains logs after start-up, you can find more logs by klogd.sh

Result (I modified the command and only included lines since the last boot):

Code: Select all

# /etc/init.d/klogd.sh dump | grep -i error | tail -n 36
<6>[2649996.128618] btd[18166]: segfault at 81df590 ip 00000000f6d6d134 sp 00000000f62617c0 error 4 in libcrypto.so.0.9.8[f6d0a000+130000]
<6>[    0.322737]  pci0000:00: ACPI _OSC request failed (AE_ERROR), returned control mask: 0x1d
<3>[    1.205669] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
<3>[    1.205676] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
<3>[    1.319931] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0
<3>[    1.319938] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0
<3>[    1.380102] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
<3>[    1.380108] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
<3>[    1.440301] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
<3>[    1.440311] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
<3>[    1.631164] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0
<3>[    1.631169] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0
<6>[    0.323170]  pci0000:00: ACPI _OSC request failed (AE_ERROR), returned control mask: 0x1d
<3>[    1.207107] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
<3>[    1.207114] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
<3>[    1.321417] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0
<3>[    1.321424] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0
<3>[    1.381592] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
<3>[    1.381598] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
<3>[    1.441789] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
<3>[    1.441794] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
<3>[    1.632633] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0
<3>[    1.632638] [drm:psb_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0
<6>[39328.868919] btd[5450]: segfault at f5a42ffc ip 00000000f759e51f sp 00000000f5a43000 error 6 in libtorrent-0.15.9.so.nonenc[f7388000+409000]
<6>[44437.778492] btd[6313]: segfault at f5a6affc ip 00000000f75c651f sp 00000000f5a6b000 error 6 in libtorrent-0.15.9.so.nonenc[f73b0000+409000]
<6>[82519.981019] btd[17216]: segfault at f59d1ffc ip 00000000f752d51f sp 00000000f59d2000 error 6 in libtorrent-0.15.9.so.nonenc[f7317000+409000]
<6>[92769.809951] btd[14020]: segfault at f5a75ffc ip 00000000f75d151f sp 00000000f5a76000 error 6 in libtorrent-0.15.9.so.nonenc[f73bb000+409000]
<6>[108250.538624] btd[3091]: segfault at f5a74ffc ip 00000000f75d051f sp 00000000f5a75000 error 6 in libtorrent-0.15.9.so.nonenc[f73ba000+409000]
<6>[111395.468756] btd[32698]: segfault at f59efffc ip 00000000f754b51f sp 00000000f59f0000 error 6 in libtorrent-0.15.9.so.nonenc[f7335000+409000]
<6>[117471.618490] btd[7436]: segfault at f5a61ffc ip 00000000f75bd51f sp 00000000f5a62000 error 6 in libtorrent-0.15.9.so.nonenc[f73a7000+409000]
<6>[118739.687093] btd[20682]: segfault at f5900ffc ip 00000000f75d251f sp 00000000f5901000 error 6 in libtorrent-0.15.9.so.nonenc[f73bc000+409000]
<3>[242938.752969] end_request: I/O error, dev sdd, sector 7761583192
<3>[242938.753056] end_request: I/O error, dev sdd, sector 7761583200
<3>[242938.753154] end_request: I/O error, dev sdd, sector 7761583208
<3>[242938.753238] end_request: I/O error, dev sdd, sector 7761583224
<3>[242938.753321] end_request: I/O error, dev sdd, sector 7761583232

QNAP_YH wrote:Did you also try bad block scan? Go to [Control Panel], [Storage manager], and physical disks, choose hard drive 4 and run [scan now].

I am on firmware 3.8.3 Build 20130426. I have looked through the web admin interface but cannot find a Control Panel. Is it somewhere else? Apologies in advance if I am overlooking something really obvious.

In view of doktornotor's reply I am happy to RMA the drive.

Thanks for your help.

QNAP_YH · Post by **QNAP_YH** » Sat Sep 14, 2013 12:13 am

Hi,

Per your klog result,

Code: Select all

<3>[242938.752969] end_request: I/O error, dev sdd, sector 7761583192
<3>[242938.753056] end_request: I/O error, dev sdd, sector 7761583200
<3>[242938.753154] end_request: I/O error, dev sdd, sector 7761583208
<3>[242938.753238] end_request: I/O error, dev sdd, sector 7761583224
<3>[242938.753321] end_request: I/O error, dev sdd, sector 7761583232

There are more I/O errors indicate hard drive 4.

I am on firmware 3.8.3 Build 20130426

For firmware 3.8.3, you can find [Scan Now] under administration -> DiskManager -> volum management.
A reference picture is as following,

bad block scan.jpg

QNAP NAS Community Forum

I/O Error on QNAP TS469U-SP internal drive

I/O Error on QNAP TS469U-SP internal drive

Re: I/O Error on QNAP TS469U-SP internal drive

Re: I/O Error on QNAP TS469U-SP internal drive

Re: I/O Error on QNAP TS469U-SP internal drive

Re: I/O Error on QNAP TS469U-SP internal drive

Re: I/O Error on QNAP TS469U-SP internal drive

Re: I/O Error on QNAP TS469U-SP internal drive

Re: I/O Error on QNAP TS469U-SP internal drive

Re: I/O Error on QNAP TS469U-SP internal drive