Currently I have R710 with perc 6/i and one sata drive attached. Today i booted the server and it went fine at first - it did load Proxmox VE and I attempted to log in it via web interface. It did show the usual ssl certificate warning but then failed to load the page. I saw one of the two hdd indicators blinking constantly in orange and the second indicator staying green. iDRAC showed that drive 0 have failed and LCD screen was orange. I did log via virtual console and there were linux messages showing some i/o errors for dev mapped device. I did warm reboot couple of times but it was stopping the boot process at the raid controller with message that there is some chached data for a drive that is been missing. The drive was missing in the perc bios too. For a few minutes the orange blinking indicator went away on its own as well as the LCD turned blue and the status in iDRAC changed to normal but despite that and the warm reboots, the drive was still missing. Few minutes later the error showed up again.
I did perform cold cycle reboot and it did fix the problem and i did backed up my data. I also went to check SMART data - both in perc bios and in Proxmox - status was showing the drive is fine even if i did not like some of the SMART data but i'm not an expert.
So what is happening? Am I looking at bad drive, bad connection for the drive or cable or worse - problem with the raid controller or backplane?
Here is S.M.A.R.T. data readings. Let me know if other information is needed.
root@vm:~# smartctl -a -d megaraid,0 /dev/sda
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.18-9-pve] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.10
Device Model: ST3320620AS
Serial Number: 6QF0A6XK
Firmware Version: 3.AAK
User Capacity: 320,071,851,520 bytes [320 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
Local Time is: Sat Mar 23 00:59:46 2019 EET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Status not supported: ATA return descriptor not supported by controller firmware
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
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: ( 430) 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: ( 115) minutes.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 111 082 006 Pre-fail Always - 31984970
3 Spin_Up_Time 0x0003 096 095 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 095 095 020 Old_age Always - 5511
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 34884441781
9 Power_On_Hours 0x0032 055 055 000 Old_age Always - 39772
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 096 096 020 Old_age Always - 4759
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 069 052 045 Old_age Always - 31 (Min/Max 23/32)
194 Temperature_Celsius 0x0022 031 048 000 Old_age Always - 31 (0 16 0 0 0)
195 Hardware_ECC_Recovered 0x001a 059 054 000 Old_age Always - 57635888
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 11
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 86 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 86 occurred at disk power-on lifetime: 11392 hours (474 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
10 51 01 6e e2 42 e5
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
37 ff 01 6e e2 42 e5 00 00:03:24.806 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 ff 00 6e e2 42 e0 00 00:03:22.710 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 ff 00 6e e2 42 e5 00 00:03:22.676 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 ff 01 6e e2 42 e0 00 00:03:22.676 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 ff 01 6e e2 42 e5 00 00:03:22.644 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 85 occurred at disk power-on lifetime: 11392 hours (474 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
10 51 01 6e e2 42 e5
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
37 ff 01 6e e2 42 e5 00 00:03:24.806 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 ff 00 6e e2 42 e0 00 00:03:22.710 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 ff 00 6e e2 42 e5 00 00:03:22.676 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 ff 01 af ea 42 e0 00 00:03:22.676 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
29 00 01 af ea 42 e0 00 00:03:22.644 READ MULTIPLE EXT
Error 84 occurred at disk power-on lifetime: 297 hours (12 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
10 51 01 6e e2 42 e5
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
37 ff 01 6e e2 42 e5 00 00:03:50.497 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 ff 00 6e e2 42 e0 00 00:03:50.437 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 ff 00 6e e2 42 e5 00 00:03:50.221 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 ff 01 6e e2 42 e0 00 00:03:50.153 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 ff 01 6e e2 42 e5 00 00:03:50.013 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 83 occurred at disk power-on lifetime: 297 hours (12 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
10 51 01 6e e2 42 e5
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
37 ff 01 6e e2 42 e5 00 00:03:50.497 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 ff 00 6e e2 42 e0 00 00:03:50.437 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 ff 00 6e e2 42 e5 00 00:03:50.221 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 ff 01 af ea 42 e0 00 00:03:50.153 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
29 00 01 af ea 42 e0 00 00:03:50.013 READ MULTIPLE EXT
Error 82 occurred at disk power-on lifetime: 297 hours (12 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
10 51 01 6e e2 42 e5
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
37 ff 01 6e e2 42 e5 00 03:27:43.317 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 ff 00 6e e2 42 e0 00 03:27:43.266 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 ff 00 6e e2 42 e5 00 03:27:43.017 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
27 ff 01 6e e2 42 e0 00 03:27:42.954 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
37 ff 01 6e e2 42 e5 00 03:27:40.455 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 39505 -
# 2 Extended offline Completed without error 00% 39504 -
# 3 Short offline Completed without error 00% 39492 -
# 4 Short offline Completed without error 00% 39489 -
# 5 Short offline Completed without error 00% 39476 -
# 6 Short offline Completed without error 00% 39464 -
# 7 Short offline Completed without error 00% 39452 -
# 8 Short offline Completed without error 00% 39441 -
# 9 Short offline Completed without error 00% 39429 -
#10 Short offline Completed without error 00% 39416 -
#11 Short offline Completed without error 00% 39412 -
#12 Short offline Completed without error 00% 39401 -
#13 Short offline Completed without error 00% 39388 -
#14 Short offline Completed without error 00% 39380 -
#15 Short offline Completed without error 00% 39377 -
#16 Short offline Completed without error 00% 39374 -
#17 Short offline Completed without error 00% 39364 -
#18 Short offline Completed without error 00% 39352 -
#19 Short offline Completed without error 00% 39341 -
#20 Short offline Completed without error 00% 39332 -
#21 Short offline Completed without error 00% 39321 -
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.
I'm unable to post SMART data because its been marked as spam by the forum. I can only post the iDRAC error message. This is from today, it happend again:
I apologize that the spam filter was blocking your posts, I have removed them so they're now visible. Would you do me a favor a clarify the specific cache error you were referring to, as well would you clarify if the server is up to date on firmware?
Would you let me know what cache error is being displayed, as well as I would suggest updating the server to current. With how far back the BIOS is I would recommend walking it up to current, don't just jump the latest as that can cause issues. I would also walk the idrac up at the same time as the BIOS.
Perc 6/i cache error was (can't reproduce exactly) referring to the drive being missing while some information that is cached was not yet written to the drive. When i went to the perc's bios i had the option to dismiss the cached data if i want but i didn't do it. This message went away automatically when I did cycle boot (cold) which seems to clear the error for the drive and drive starts functioning normally again.
As for firmware updates, I know i have the iDRAC at its latest version since I updated it mid january. I did have issue with that update since it reported an error at around 20-30 percent midupgrade, then i read that after uploading the new firmware to the iDRAC is good idea to wait few minutes before starting the update process and then everything went fine after that. Perc's firmware seems to be one of the latest revisions so I didnt touch that. As for the bios i intentionally avoid updating it for two reasons:
1) I dont have redundant power (power supplies - yes, but not power) 2) version 6.4.0 which i currently have is one of last versions before specter and meltdown mitigations; from what i read, those mitigations can hurt performance and in my use case, this server is not going to surf the internet and execute scripts - it is mainly going to host services like firewall, proxy, svn, nas and transcoding video, and the last one can be pretty intensive.
Georgi_
22 Posts
0
March 21st, 2019 21:00
Greetings.
Currently I have R710 with perc 6/i and one sata drive attached. Today i booted the server and it went fine at first - it did load Proxmox VE and I attempted to log in it via web interface. It did show the usual ssl certificate warning but then failed to load the page. I saw one of the two hdd indicators blinking constantly in orange and the second indicator staying green. iDRAC showed that drive 0 have failed and LCD screen was orange. I did log via virtual console and there were linux messages showing some i/o errors for dev mapped device. I did warm reboot couple of times but it was stopping the boot process at the raid controller with message that there is some chached data for a drive that is been missing. The drive was missing in the perc bios too. For a few minutes the orange blinking indicator went away on its own as well as the LCD turned blue and the status in iDRAC changed to normal but despite that and the warm reboots, the drive was still missing. Few minutes later the error showed up again.
I did perform cold cycle reboot and it did fix the problem and i did backed up my data. I also went to check SMART data - both in perc bios and in Proxmox - status was showing the drive is fine even if i did not like some of the SMART data but i'm not an expert.
So what is happening? Am I looking at bad drive, bad connection for the drive or cable or worse - problem with the raid controller or backplane?
DELL-Chris H
Moderator
Moderator
•
8.4K Posts
0
March 22nd, 2019 08:00
Georgi_,
We would need you to provide more details to be able to assist you.
Georgi_
22 Posts
0
March 22nd, 2019 16:00
Here is S.M.A.R.T. data readings. Let me know if other information is needed.
root@vm:~# smartctl -a -d megaraid,0 /dev/sda smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.18-9-pve] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 Device Model: ST3320620AS Serial Number: 6QF0A6XK Firmware Version: 3.AAK User Capacity: 320,071,851,520 bytes [320 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA/ATAPI-7 (minor revision not indicated) Local Time is: Sat Mar 23 00:59:46 2019 EET SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART Status not supported: ATA return descriptor not supported by controller firmware SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check. General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. 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: ( 430) 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: ( 115) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 111 082 006 Pre-fail Always - 31984970 3 Spin_Up_Time 0x0003 096 095 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 095 095 020 Old_age Always - 5511 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 34884441781 9 Power_On_Hours 0x0032 055 055 000 Old_age Always - 39772 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 096 096 020 Old_age Always - 4759 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 069 052 045 Old_age Always - 31 (Min/Max 23/32) 194 Temperature_Celsius 0x0022 031 048 000 Old_age Always - 31 (0 16 0 0 0) 195 Hardware_ECC_Recovered 0x001a 059 054 000 Old_age Always - 57635888 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 11 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 86 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 86 occurred at disk power-on lifetime: 11392 hours (474 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 01 6e e2 42 e5 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 ff 01 6e e2 42 e5 00 00:03:24.806 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] 27 ff 00 6e e2 42 e0 00 00:03:22.710 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] 37 ff 00 6e e2 42 e5 00 00:03:22.676 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] 27 ff 01 6e e2 42 e0 00 00:03:22.676 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] 37 ff 01 6e e2 42 e5 00 00:03:22.644 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] Error 85 occurred at disk power-on lifetime: 11392 hours (474 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 01 6e e2 42 e5 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 ff 01 6e e2 42 e5 00 00:03:24.806 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] 27 ff 00 6e e2 42 e0 00 00:03:22.710 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] 37 ff 00 6e e2 42 e5 00 00:03:22.676 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] 27 ff 01 af ea 42 e0 00 00:03:22.676 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] 29 00 01 af ea 42 e0 00 00:03:22.644 READ MULTIPLE EXT Error 84 occurred at disk power-on lifetime: 297 hours (12 days + 9 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 01 6e e2 42 e5 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 ff 01 6e e2 42 e5 00 00:03:50.497 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] 27 ff 00 6e e2 42 e0 00 00:03:50.437 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] 37 ff 00 6e e2 42 e5 00 00:03:50.221 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] 27 ff 01 6e e2 42 e0 00 00:03:50.153 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] 37 ff 01 6e e2 42 e5 00 00:03:50.013 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] Error 83 occurred at disk power-on lifetime: 297 hours (12 days + 9 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 01 6e e2 42 e5 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 ff 01 6e e2 42 e5 00 00:03:50.497 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] 27 ff 00 6e e2 42 e0 00 00:03:50.437 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] 37 ff 00 6e e2 42 e5 00 00:03:50.221 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] 27 ff 01 af ea 42 e0 00 00:03:50.153 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] 29 00 01 af ea 42 e0 00 00:03:50.013 READ MULTIPLE EXT Error 82 occurred at disk power-on lifetime: 297 hours (12 days + 9 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 01 6e e2 42 e5 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 ff 01 6e e2 42 e5 00 03:27:43.317 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] 27 ff 00 6e e2 42 e0 00 03:27:43.266 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] 37 ff 00 6e e2 42 e5 00 03:27:43.017 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] 27 ff 01 6e e2 42 e0 00 03:27:42.954 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] 37 ff 01 6e e2 42 e5 00 03:27:40.455 SET NATIVE MAX ADDRESS EXT [OBS-ACS-3] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 39505 - # 2 Extended offline Completed without error 00% 39504 - # 3 Short offline Completed without error 00% 39492 - # 4 Short offline Completed without error 00% 39489 - # 5 Short offline Completed without error 00% 39476 - # 6 Short offline Completed without error 00% 39464 - # 7 Short offline Completed without error 00% 39452 - # 8 Short offline Completed without error 00% 39441 - # 9 Short offline Completed without error 00% 39429 - #10 Short offline Completed without error 00% 39416 - #11 Short offline Completed without error 00% 39412 - #12 Short offline Completed without error 00% 39401 - #13 Short offline Completed without error 00% 39388 - #14 Short offline Completed without error 00% 39380 - #15 Short offline Completed without error 00% 39377 - #16 Short offline Completed without error 00% 39374 - #17 Short offline Completed without error 00% 39364 - #18 Short offline Completed without error 00% 39352 - #19 Short offline Completed without error 00% 39341 - #20 Short offline Completed without error 00% 39332 - #21 Short offline Completed without error 00% 39321 - 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.theflash1932
7 Technologist
7 Technologist
•
16.3K Posts
0
March 23rd, 2019 14:00
By far, most likely a bad drive.
Georgi_
22 Posts
0
March 23rd, 2019 14:00
I'm unable to post SMART data because its been marked as spam by the forum. I can only post the iDRAC error message. This is from today, it happend again:
DELL-Chris H
Moderator
Moderator
•
8.4K Posts
0
March 26th, 2019 05:00
I apologize that the spam filter was blocking your posts, I have removed them so they're now visible. Would you do me a favor a clarify the specific cache error you were referring to, as well would you clarify if the server is up to date on firmware?
Thanks.
Georgi_
22 Posts
0
March 27th, 2019 13:00
I'm using write-back write caching and adaptive for reading caching policy. BIOS version 6.4.0, Perc firmware as follows:
package: 6.3.1-0003
fw version: 1.22.32-1371
bios version: 2.04.00
ctrIR version: 1.02-015B
boot block: 1.00.00.01-0011
DELL-Chris H
Moderator
Moderator
•
8.4K Posts
0
March 29th, 2019 08:00
Would you let me know what cache error is being displayed, as well as I would suggest updating the server to current. With how far back the BIOS is I would recommend walking it up to current, don't just jump the latest as that can cause issues. I would also walk the idrac up at the same time as the BIOS.
Georgi_
22 Posts
0
March 29th, 2019 10:00
Perc 6/i cache error was (can't reproduce exactly) referring to the drive being missing while some information that is cached was not yet written to the drive. When i went to the perc's bios i had the option to dismiss the cached data if i want but i didn't do it. This message went away automatically when I did cycle boot (cold) which seems to clear the error for the drive and drive starts functioning normally again.
As for firmware updates, I know i have the iDRAC at its latest version since I updated it mid january. I did have issue with that update since it reported an error at around 20-30 percent midupgrade, then i read that after uploading the new firmware to the iDRAC is good idea to wait few minutes before starting the update process and then everything went fine after that. Perc's firmware seems to be one of the latest revisions so I didnt touch that. As for the bios i intentionally avoid updating it for two reasons:
1) I dont have redundant power (power supplies - yes, but not power)
2) version 6.4.0 which i currently have is one of last versions before specter and meltdown mitigations; from what i read, those mitigations can hurt performance and in my use case, this server is not going to surf the internet and execute scripts - it is mainly going to host services like firewall, proxy, svn, nas and transcoding video, and the last one can be pretty intensive.