Jump to content

xtrap225

Members
  • Content Count

    23
  • Joined

  • Last visited

Everything posted by xtrap225

  1. put that in my go file and started another smartctl long test on a different drive that i have less faith in while witing for my preclear to finish on sdp. sdp and sdm (the one i am running long test on now) are the only drives that when the system is rebooted lose their write-cache setting, and i have to use hdparm -W1 /dev/sdm and sdp to turn it back on. ( i have also now added that to the go file). i am only making note of these things now so that people can benefit form this experience and i will have the commands noted in this thread. root@WORK-PC:~# smartctl -d sat -t long -C /dev/sdm smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.56-Unraid] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART Extended self-test routine immediately in captive mode". Drive command "Execute SMART Extended self-test routine immediately in captive mode" successful. Testing has begun. Please wait 369 minutes for test to complete. Test will complete after Mon Sep 9 23:29:45 2019 and here is a copy of my /boot/config/go file. root@WORK-PC:~# cat /boot/config/go #Setup smartd.conf mv /etc/smartd.conf /etc/smartd.conf.backup cp -p /boot/smartd.conf.bak /etc/smartd.conf chmod 644 /etc/smartd.conf chmod 755 /etc/rc.d/rc.smartd /etc/rc.d/rc.smartd start #enable write cache on sdm and sdp hdparm -W1 /dev/sdm hdparm -W1 /dev/sdp #Setup drivers for hardware transcoding in Plex modprobe i915 chown -R nobody:users /dev/dri chmod -R 777 /dev/dri #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & and for anyone with a netapp here is the /etc/smartd.conf i will be using. root@WORK-PC:~# cat /etc/smartd.conf #DEVICESCAN # Monitor LSI's disk SMART through SCSI generic /dev/sdb -d sat -a -s L/../../3/02 /dev/sdc -d sat -a -s L/../../3/03 /dev/sdd -d sat -a -s L/../../3/04 /dev/sde -d sat -a -s L/../../3/05 /dev/sdf -d sat -a -s L/../../3/06 /dev/sdg -d sat -a -s L/../../3/07 /dev/sdh -d sat -a -s L/../../3/08 /dev/sdi -d sat -a -s L/../../3/09 /dev/sdj -d sat -a -s L/../../3/10 /dev/sdk -d sat -a -s L/../../3/11 /dev/sdl -d sat -a -s L/../../3/12 /dev/sdm -d sat -a -s L/../../3/13 /dev/sdn -d sat -a -s L/../../3/14 /dev/sdo -d sat -a -s L/../../3/15 /dev/sdp -d sat -a -s L/../../3/16 /dev/sdq -d sat -a -s L/../../3/17 /dev/sdr -d sat -a -s L/../../3/18 /dev/sds -d sat -a -s L/../../3/19 /dev/sdt -d sat -a -s L/../../3/20 /dev/sdu -d sat -a -s L/../../3/21 /dev/sdv -d sat -a -s L/../../3/22 /dev/sdw -d sat -a -s L/../../3/23 /dev/sdx -d sat -a -s L/../../3/24 /dev/sdy -d sat -a -s L/../../3/25 /dev/sdz -d sat -a -s L/../../3/26 here is the /var/log/syslog of the smartd loading up with the new config root@WORK-PC:~# less /var/log/syslog Sep 9 17:12:01 WORK-PC smartd[9481]: Device: /dev/sdu [SAT], not found in smartd database. Sep 9 17:12:01 WORK-PC smartd[9481]: Device: /dev/sdu [SAT], not capable of SMART Health Status check Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdu [SAT], is SMART capable. Adding to "monitor" list. Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdv [SAT], opened Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdv [SAT], SEAGATE ST3000NM0033, S/N:Z1Y1T5V8, WWN:5-000c50-0675c7981, FW:NS00, 3.00 TB Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdv [SAT], not found in smartd database. Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdv [SAT], not capable of SMART Health Status check Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdv [SAT], is SMART capable. Adding to "monitor" list. Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdw [SAT], opened Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdw [SAT], SEAGATE ST3000NM0033, S/N:Z1Y1X2MN, WWN:5-000c50-0675c76b3, FW:NS00, 3.00 TB Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdw [SAT], not found in smartd database. Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdw [SAT], not capable of SMART Health Status check Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdw [SAT], is SMART capable. Adding to "monitor" list. Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdx [SAT], opened Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdx [SAT], SEAGATE ST3000NM0033, S/N:Z1Y1X2JX, WWN:5-000c50-0675c876f, FW:NS00, 3.00 TB Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdx [SAT], not found in smartd database. Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdx [SAT], not capable of SMART Health Status check Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdx [SAT], is SMART capable. Adding to "monitor" list. Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdy [SAT], opened Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdy [SAT], SEAGATE ST3000NM0033, S/N:Z1Y1X2NR, WWN:5-000c50-0675c859a, FW:NS00, 3.00 TB Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdy [SAT], not found in smartd database. Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdy [SAT], not capable of SMART Health Status check Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdy [SAT], is SMART capable. Adding to "monitor" list. Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdz [SAT], opened Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdz [SAT], SEAGATE ST3000NM0033, S/N:Z1Y1T69A, WWN:5-000c50-0675c6f7d, FW:NS00, 3.00 TB Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdz [SAT], not found in smartd database. Sep 9 17:12:02 WORK-PC smartd[9481]: Device: /dev/sdz [SAT], not capable of SMART Health Status check Sep 9 17:12:03 WORK-PC smartd[9481]: Device: /dev/sdz [SAT], is SMART capable. Adding to "monitor" list. Sep 9 17:12:03 WORK-PC smartd[9481]: Monitoring 25 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices Sep 9 17:12:04 WORK-PC smartd[9481]: Device: /dev/sdm [SAT], previous self-test was interrupted by the host with a reset Sep 9 17:12:05 WORK-PC smartd[9481]: Device: /dev/sdp [SAT], previous self-test was interrupted by the host with a reset Sep 9 17:12:06 WORK-PC smartd[10307]: smartd has fork()ed into background mode. New PID=10307. Sep 9 17:12:06 WORK-PC smartd[10307]: file /run/smartd.pid written containing PID 10307
  2. now if i figure out how to properly modify the smartd.conf to properly detect the drives with the -d sat instead of doing DEVICESCAN which is putting in scsi maybe i can have a better unraid smart experience in general. not sure if i should use /dev/sdp or the equivalent /dev/sgX but assuming ill stick with 'sd' here is what my /etc/smartd.conf would look like. #DEVICESCAN # Monitor LSI's disk SMART through SCSI generic /dev/sdb -d sat -a -s L/../../3/02 /dev/sdc -d sat -a -s L/../../3/03 /dev/sdd -d sat -a -s L/../../3/04 /dev/sde -d sat -a -s L/../../3/05 /dev/sdf -d sat -a -s L/../../3/06 /dev/sdg -d sat -a -s L/../../3/07 /dev/sdh -d sat -a -s L/../../3/08 /dev/sdi -d sat -a -s L/../../3/09 /dev/sdj -d sat -a -s L/../../3/10 /dev/sdk -d sat -a -s L/../../3/11 /dev/sdl -d sat -a -s L/../../3/12 /dev/sdm -d sat -a -s L/../../3/13 /dev/sdn -d sat -a -s L/../../3/14 /dev/sdo -d sat -a -s L/../../3/15 /dev/sdp -d sat -a -s L/../../3/16 /dev/sdq -d sat -a -s L/../../3/17 /dev/sdr -d sat -a -s L/../../3/18 /dev/sds -d sat -a -s L/../../3/19 /dev/sdt -d sat -a -s L/../../3/20 /dev/sdu -d sat -a -s L/../../3/21 /dev/sdv -d sat -a -s L/../../3/22 /dev/sdw -d sat -a -s L/../../3/23 /dev/sdx -d sat -a -s L/../../3/24 /dev/sdy -d sat -a -s L/../../3/25 /dev/sdz -d sat -a -s L/../../3/26
  3. actually how does this look w/ regards to smart output done through the netapp still but using proper LSI Fusion MPT SAS2 driver settings? does this look like it has the full output? root@WORK-PC:~# smartctl -d sat -a /dev/sdp smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.56-Unraid] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: SEAGATE ST3000NM0033 Serial Number: Z1Y1X1PX LU WWN Device Id: 5 000c50 0675cb0e7 Firmware Version: NS00 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Mon Sep 9 13:10:00 2019 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART Status not supported: Incomplete response, ATA output registers missing 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: ( 105) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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: ( 369) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x50bf) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. 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 081 063 044 Pre-fail Always - 156604416 3 Spin_Up_Time 0x0003 097 096 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 56 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 5 7 Seek_Error_Rate 0x000f 086 060 030 Pre-fail Always - 406887179 9 Power_On_Hours 0x0032 072 072 000 Old_age Always - 24771 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 23 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 095 095 000 Old_age Always - 5 188 Command_Timeout 0x0032 100 098 000 Old_age Always - 8590065667 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 064 053 045 Old_age Always - 36 (Min/Max 34/36) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 20 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1083 194 Temperature_Celsius 0x0022 036 047 000 Old_age Always - 36 (0 21 0 0 0) 195 Hardware_ECC_Recovered 0x001a 034 019 000 Old_age Always - 156604416 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 - 0 SMART Error Log Version: 1 ATA Error Count: 8 (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 8 occurred at disk power-on lifetime: 24721 hours (1030 days + 1 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 00 00 00 00 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 00 00 00 00 00 ff 15d+17:03:05.309 NOP [Abort queued commands] b0 d4 00 82 4f c2 00 00 15d+12:00:01.038 SMART EXECUTE OFF-LINE IMMEDIATE ec 00 01 00 00 00 00 00 15d+12:00:00.942 IDENTIFY DEVICE ec 00 01 00 00 00 00 00 15d+12:00:00.941 IDENTIFY DEVICE e5 00 00 00 00 00 00 00 15d+11:59:00.770 CHECK POWER MODE Error 7 occurred at disk power-on lifetime: 24708 hours (1029 days + 12 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 00 00 00 00 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 00 00 00 00 00 ff 15d+04:40:50.041 NOP [Abort queued commands] b0 d4 00 82 4f c2 00 00 14d+23:37:45.768 SMART EXECUTE OFF-LINE IMMEDIATE ec 00 01 00 00 00 00 00 14d+23:37:45.673 IDENTIFY DEVICE ec 00 01 00 00 00 00 00 14d+23:37:45.672 IDENTIFY DEVICE e5 00 00 00 00 00 00 00 14d+23:18:07.902 CHECK POWER MODE Error 6 occurred at disk power-on lifetime: 24687 hours (1028 days + 15 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 00 00 00 00 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 00 00 00 00 00 ff 14d+07:40:17.431 NOP [Abort queued commands] b0 d4 00 82 4f c2 00 00 14d+02:37:13.161 SMART EXECUTE OFF-LINE IMMEDIATE ec 00 01 00 00 00 00 00 14d+02:37:13.066 IDENTIFY DEVICE ec 00 01 00 00 00 00 00 14d+02:37:13.065 IDENTIFY DEVICE e5 00 00 00 00 00 00 00 14d+02:31:51.028 CHECK POWER MODE Error 5 occurred at disk power-on lifetime: 24675 hours (1028 days + 3 hours) When the command that caused the error occurred, the device was in standby mode. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 13d+19:52:05.743 READ FPDMA QUEUED e2 00 00 00 00 00 00 00 13d+19:52:04.691 STANDBY b0 d6 01 e0 4f c2 00 00 13d+19:52:04.691 SMART WRITE LOG b0 d6 01 e0 4f c2 00 00 13d+19:52:04.690 SMART WRITE LOG ef 10 02 00 00 00 00 00 13d+19:52:04.690 SET FEATURES [Enable SATA feature] Error 4 occurred at disk power-on lifetime: 24675 hours (1028 days + 3 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 -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 13d+19:52:00.514 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 13d+19:52:00.487 READ FPDMA QUEUED 61 00 80 ff ff ff 4f 00 13d+19:52:00.483 WRITE FPDMA QUEUED 61 00 f0 ff ff ff 4f 00 13d+19:52:00.481 WRITE FPDMA QUEUED 61 00 78 ff ff ff 4f 00 13d+19:52:00.480 WRITE FPDMA QUEUED 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% 24748 - # 2 Extended captive Interrupted (host reset) 00% 24748 - # 3 Short captive Completed without error 00% 24748 - # 4 Short offline Aborted by host 30% 24748 - # 5 Extended captive Interrupted (host reset) 20% 24721 - # 6 Extended captive Interrupted (host reset) 20% 24708 - # 7 Extended captive Interrupted (host reset) 20% 24687 - # 8 Short captive Completed without error 00% 24681 - # 9 Short offline Completed without error 00% 24681 - 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.
  4. okay thanks, once it is done its first pre-clear i will remove it again and plug it in via usb and try that command again. does running a pre-clear 'verify all disk' help increase your confidence in the drive, or is a 'normal' clear sufficient?
  5. you are correct it was there i just didn't find it due to my own stupidity. is this the smart output? root@WORK-PC:~# smartctl -a /dev/sdp smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.56-Unraid] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: SEAGATE Product: ST3000NM0033 SA Revision: NA00 Compliance: SPC-3 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Logical block size: 512 bytes Rotation Rate: 7200 rpm Form Factor: 3.5 inches Logical Unit id: 0x50000c900064ff5c Serial number: Z1Y1X1PX Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Mon Sep 9 09:47:42 2019 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Enabled === START OF READ SMART DATA SECTION === SMART Health Status: OK Current Drive Temperature: 36 C Drive Trip Temperature: <not available> Manufactured in week of year Specified cycle count over device lifetime: 0 Accumulated start-stop cycles: 56 Read defect list: asked for grown list but didn't get it Vendor (Seagate Cache) information Blocks sent to initiator = 62 Blocks received from initiator = 0 Blocks read from cache and sent to initiator = 12 Number of read and write commands whose size <= segment size = 0 Number of read and write commands whose size > segment size = 0 Vendor (Seagate/Hitachi) factory information number of hours powered up = 24761.00 number of minutes until next internal SMART test = 28 Error counter log: Errors Corrected by Total Correction Gigabytes Total ECC rereads/ errors algorithm processed uncorrected fast | delayed rewrites corrected invocations [10^9 bytes] errors read: 0 0 0 0 0 0.000 0 write: 0 0 0 0 0 0.000 0 Non-medium error count: 88 [GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on'] SMART Self-test log Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background short Completed - 24748 - [- - -] # 2 Foreground long Aborted (device reset ?) - 24748 0 [0xb 0x82 0x0] # 3 Foreground short Completed - 24748 - [- - -] # 4 Background short Aborted (by user command) - 24748 0 [0xb 0x81 0x0] # 5 Foreground long Aborted (device reset ?) - 24721 0 [0xb 0x82 0x0] # 6 Foreground long Aborted (device reset ?) - 24708 0 [0xb 0x82 0x0] # 7 Foreground long Aborted (device reset ?) - 24687 0 [0xb 0x82 0x0] # 8 Foreground short Completed - 24681 - [- - -] # 9 Background short Completed - 24681 - [- - -] Long (extended) Self-test duration: 22140 seconds [369.0 minutes]
  6. may i ask you smart folks, do you know how to re-detect that drive i put in without rebooting? i have a SAS2008 card connecting my desktop computer to that netapp previously discussed. Dell LSI SAS 9202-16e 6Gb/s SAS Host Bus Adapter from lspci 03:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) from dmesg 303.920071] mdcmd (13): import 12 [ 303.920072] md: import_slot: 12 missing root@WORK-PC:~# dmesg |grep -B2 -A2 SAS2008 [ 13.633974] mpt2sas_cm0: Current Controller Queue Depth(1948),Max Controller Queue Depth(2040) [ 13.634737] mpt2sas_cm0: Scatter Gather Elements per IO(128) [ 13.681883] mpt2sas_cm0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00) [ 13.683391] mpt2sas_cm0: Protocol=( [ 13.683391] Initiator -- [ 13.871549] mpt2sas_cm1: Current Controller Queue Depth(1948),Max Controller Queue Depth(2040) [ 13.872281] mpt2sas_cm1: Scatter Gather Elements per IO(128) [ 13.919956] mpt2sas_cm1: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00) [ 13.921470] mpt2sas_cm1: Protocol=( [ 13.921471] Initiator
  7. so i used Seagate SeaTools for Windows with the drive plugged in via USB3 Asmedia ASM1053E. it passed all the tests in the program. S.M.A.R.T Check, Short Drive Self Test, Short Generic, and Long Generic. my next step is to put it back in the server and run the pre-check 3 times and then rebuild it from parity.
  8. oh just to build my trust in the process. im running a NetApp DS4246 and unraid doesn't love. seems to be some communications issues when it comes to for example putting drives to sleep.
  9. i am working on moving all the data off the drive so i can test it outside of the system with the manufacturers utility, and then i will of course be prepared to replace it, to a certain degree. of course i will likely want to do a parity swap, because all the drives in the storage shelf are 3TB and i certainly don't want to go out and buy a 3TB. one more interesting thing i found... this is the only drive with write-back cache disabled on it. i enabled write-back cache and found this morning it was disabled again. strange. is there a rc.d script that sets the write-back cache using hdparm at startup?
  10. booooo! same error. am i running that correctly? can you recommend any other smartclt or other tests i should/could run? root@WORK-PC:~# smartctl -t long -C /dev/sdp smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.56-Unraid] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org Long (extended) foreground self test failed [medium or hardware error (serious)]
  11. i guess its not bad blocks root@WORK-PC:~# badblocks -v /dev/sdp |tee -a bad-blocks-sdp.txt Checking blocks 0 to 2930266583 Checking for bad blocks (read-only test): done Pass completed, 0 bad blocks found. (0/0/0 errors)
  12. so i got this email from the server when i work up this morning. Event: Unraid array errors Subject: Warning [WORK-PC] - array has errors Description: Array has 1 disk with read errors Importance: warning Disk 12 - ST3000NM0033_SA_Z1Y1X1PX (sdp) (errors 341) however the drive is 'green' and nothing seems to be broken on the server. here is the 'disk log' and attached is the diagnostics Aug 17 16:25:46 WORK-PC emhttpd: ST3000NM0033_SA_Z1Y1X1PX (sdp) 512 5860533168 Aug 17 16:25:56 WORK-PC emhttpd: ST3000NM0033_SA_Z1Y1X1PX (sdp) 512 5860533168 Aug 17 16:26:01 WORK-PC emhttpd: ST3000NM0033_SA_Z1Y1X1PX (sdp) 512 5860533168 Aug 17 16:26:10 WORK-PC emhttpd: ST3000NM0033_SA_Z1Y1X1PX (sdp) 512 5860533168 Aug 17 16:26:10 WORK-PC kernel: mdcmd (13): import 12 sdp 64 2930266532 0 ST3000NM0033_SA_Z1Y1X1PX Aug 17 16:26:10 WORK-PC kernel: md: import disk12: (sdp) ST3000NM0033_SA_Z1Y1X1PX size: 2930266532 Aug 17 16:26:22 WORK-PC emhttpd: ST3000NM0033_SA_Z1Y1X1PX (sdp) 512 5860533168 Aug 17 16:26:22 WORK-PC kernel: mdcmd (13): import 12 sdp 64 2930266532 0 ST3000NM0033_SA_Z1Y1X1PX Aug 17 16:26:22 WORK-PC kernel: md: import disk12: (sdp) ST3000NM0033_SA_Z1Y1X1PX size: 2930266532 Aug 17 16:26:26 WORK-PC emhttpd: ST3000NM0033_SA_Z1Y1X1PX (sdp) 512 5860533168 Aug 17 16:26:26 WORK-PC kernel: mdcmd (13): import 12 sdp 64 2930266532 0 ST3000NM0033_SA_Z1Y1X1PX Aug 17 16:26:26 WORK-PC kernel: md: import disk12: (sdp) ST3000NM0033_SA_Z1Y1X1PX size: 2930266532 Aug 17 16:26:50 WORK-PC emhttpd: shcmd (327): /usr/local/sbin/set_ncq sdp 1 Aug 17 16:26:50 WORK-PC root: set_ncq: setting sdp queue_depth to 1 Aug 17 16:26:50 WORK-PC emhttpd: shcmd (328): echo 128 > /sys/block/sdp/queue/nr_requests Aug 17 17:01:44 WORK-PC emhttpd: shcmd (671): /usr/local/sbin/set_ncq sdp 1 Aug 17 17:01:44 WORK-PC emhttpd: shcmd (672): echo 128 > /sys/block/sdp/queue/nr_requests Aug 17 17:08:36 WORK-PC emhttpd: shcmd (1055): /usr/local/sbin/set_ncq sdp 1 Aug 17 17:08:36 WORK-PC emhttpd: shcmd (1056): echo 128 > /sys/block/sdp/queue/nr_requests Aug 17 23:15:50 WORK-PC emhttpd: writing GPT on disk (sdp), with partition 1 byte offset 32K, erased: 0 Aug 17 23:15:50 WORK-PC emhttpd: shcmd (1167): sgdisk -Z /dev/sdp Aug 17 23:15:50 WORK-PC kernel: sdp: sdp1 sdp2 Aug 17 23:15:51 WORK-PC emhttpd: shcmd (1168): sgdisk -o -a 8 -n 1:32K:0 /dev/sdp Aug 17 23:15:52 WORK-PC kernel: sdp: sdp1 Aug 25 18:02:47 WORK-PC root: #012/dev/sdp:#012 drive state is: unknown Aug 25 18:07:47 WORK-PC root: #012/dev/sdp:#012 drive state is: unknown Sep 5 08:50:06 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 5 08:50:06 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#15 Sense Key : 0x3 [current] [descriptor] Sep 5 08:50:06 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#15 ASC=0x11 ASCQ=0x0 Sep 5 08:50:06 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#15 CDB: opcode=0x88 88 00 00 00 00 00 ed 59 a9 48 00 00 04 00 00 00 Sep 5 08:50:06 WORK-PC kernel: print_req_error: critical medium error, dev sdp, sector 3982076882 Sep 5 08:50:09 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 5 08:50:09 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#0 Sense Key : 0x3 [current] [descriptor] Sep 5 08:50:09 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 08:50:09 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 ed 59 ad 48 00 00 04 00 00 00 Sep 5 08:50:09 WORK-PC kernel: print_req_error: critical medium error, dev sdp, sector 3982077532 Sep 5 08:50:12 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 5 08:50:12 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#0 Sense Key : 0x3 [current] [descriptor] Sep 5 08:50:12 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 08:50:12 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 ed 59 b1 48 00 00 04 00 00 00 Sep 5 08:50:12 WORK-PC kernel: print_req_error: critical medium error, dev sdp, sector 3982078413 Sep 5 08:50:21 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 5 08:50:21 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#0 Sense Key : 0x3 [current] [descriptor] Sep 5 08:50:21 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 08:50:21 WORK-PC kernel: sd 7:0:14:0: [sdp] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 ed 59 b9 48 00 00 04 00 00 00 Sep 5 08:50:21 WORK-PC kernel: print_req_error: critical medium error, dev sdp, sector 3982080653 Sep 5 14:31:28 WORK-PC emhttpd: shcmd (1403): /usr/local/sbin/set_ncq sdp 1 Sep 5 14:31:28 WORK-PC emhttpd: shcmd (1404): echo 128 > /sys/block/sdp/queue/nr_requests Sep 5 14:31:28 WORK-PC emhttpd: shcmd (1435): /usr/local/sbin/set_ncq sdp 1 Sep 5 14:31:28 WORK-PC emhttpd: shcmd (1436): echo 128 > /sys/block/sdp/queue/nr_requests Sep 5 14:31:36 WORK-PC emhttpd: shcmd (1467): /usr/local/sbin/set_ncq sdp 1 Sep 5 14:31:36 WORK-PC emhttpd: shcmd (1468): echo 128 > /sys/block/sdp/queue/nr_requests Sep 5 14:31:36 WORK-PC emhttpd: shcmd (1499): /usr/local/sbin/set_ncq sdp 1 Sep 5 14:31:36 WORK-PC emhttpd: shcmd (1500): echo 128 > /sys/block/sdp/queue/nr_requests Sep 5 14:31:38 WORK-PC emhttpd: shcmd (1531): /usr/local/sbin/set_ncq sdp 1 Sep 5 14:31:38 WORK-PC emhttpd: shcmd (1532): echo 128 > /sys/block/sdp/queue/nr_requests Sep 5 14:31:38 WORK-PC emhttpd: shcmd (1563): /usr/local/sbin/set_ncq sdp 1 Sep 5 14:31:38 WORK-PC emhttpd: shcmd (1564): echo 128 > /sys/block/sdp/queue/nr_requests i did a quick smart scan from command line and it came up fine. and i did a long scan it said this. root@WORK-PC:~# smartctl -t short -C /dev/sdp smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.56-Unraid] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org Short Foreground Self Test Successful root@WORK-PC:~# smartctl -t long -C /dev/sdp smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.56-Unraid] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org Long (extended) foreground self test failed [medium or hardware error (serious)] i am currently running the following but i don't have a result yet. root@WORK-PC:~# badblocks -v /dev/sdp |tee -a back-blocks-sdp.txt Checking blocks 0 to 2930266583 Checking for bad blocks (read-only test): all scans were done with the arrray up, so i don't know if that is bad or not. also some more more smart output that i saw was asked for in a similar situation when i was looking through the forums root@WORK-PC:~# smartctl -r ioctl,2 -i -H /dev/sdp smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.56-Unraid] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org sdp -> /sys/class/scsi_host/host7/proc_name: "mpt2sas" >>>> do_scsi_cmnd_io: sg_io_ver=3 [inquiry: 12 00 00 00 24 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=2 milliseconds resid=0 Incoming data, len=36: 00 00 00 05 02 73 01 30 02 53 45 41 47 41 54 45 20 10 53 54 33 30 30 30 4e 4d 30 30 33 33 20 20 53 41 20 4e 41 30 30 >>>> do_scsi_cmnd_io: sg_io_ver=3 [inquiry: 12 01 00 00 fc 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=0 milliseconds resid=235 Incoming data, len=17: 00 00 00 00 0d 00 80 83 86 88 89 90 b0 b1 d0 d1 d2 10 d3 >>>> do_scsi_cmnd_io: sg_io_ver=3 [inquiry: 12 00 00 00 24 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=1 milliseconds resid=0 Incoming data, len=36: 00 00 00 05 02 73 01 30 02 53 45 41 47 41 54 45 20 10 53 54 33 30 30 30 4e 4d 30 30 33 33 20 20 53 41 20 4e 41 30 30 === START OF INFORMATION SECTION === Vendor: SEAGATE Product: ST3000NM0033 SA Revision: NA00 Compliance: SPC-3 >>>> do_scsi_cmnd_io: sg_io_ver=3 [read capacity(16): 9e 10 00 00 00 00 00 00 00 00 00 00 00 20 00 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=0 milliseconds resid=0 Incoming data, len=32: 00 00 00 00 01 5d 50 a3 af 00 00 02 00 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Logical block size: 512 bytes >>>> do_scsi_cmnd_io: sg_io_ver=3 [inquiry: 12 01 b1 00 40 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=0 milliseconds resid=0 Incoming data, len=64: 00 00 b1 00 3c 1c 20 00 02 00 00 00 00 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Rotation Rate: 7200 rpm Form Factor: 3.5 inches >>>> do_scsi_cmnd_io: sg_io_ver=3 [mode sense(6): 1a 00 1c 00 40 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=0 milliseconds resid=40 Incoming data, len=24: 00 17 00 00 08 ff ff ff ff 00 00 02 00 9c 0a 10 06 10 00 00 00 00 00 00 00 01 >>>> do_scsi_cmnd_io: sg_io_ver=3 [mode sense(6): 1a 00 5c 00 40 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=1 milliseconds resid=40 Incoming data, len=24: 00 17 00 00 08 ff ff ff ff 00 00 02 00 9c 0a b9 0f 10 ff ff ff ff ff ff ff ff >>>> do_scsi_cmnd_io: sg_io_ver=3 [inquiry: 12 01 83 00 fc 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=0 milliseconds resid=216 Incoming data, len=36: 00 00 83 00 20 01 03 00 08 50 00 0c 90 00 64 ff 5c 10 61 93 00 08 50 00 0c 90 00 64 ff 5d 61 94 00 04 20 00 00 00 01 Logical Unit id: 0x50000c900064ff5c >>>> do_scsi_cmnd_io: sg_io_ver=3 [inquiry: 12 01 80 00 fc 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=0 milliseconds resid=228 Incoming data, len=24: 00 00 80 00 14 5a 31 59 31 58 31 50 58 20 20 20 20 10 20 20 20 20 20 20 20 20 Serial number: Z1Y1X1PX Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Thu Sep 5 22:25:21 2019 EDT >>>> do_scsi_cmnd_io: sg_io_ver=3 [test unit ready: 00 00 00 00 00 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=0 milliseconds resid=0 SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Enabled === START OF READ SMART DATA SECTION === >>>> do_scsi_cmnd_io: sg_io_ver=3 [log sense: 4d 00 40 00 00 00 00 00 04 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=0 milliseconds resid=0 Incoming data, len=4: 00 80 00 00 15 >>>> do_scsi_cmnd_io: sg_io_ver=3 [log sense: 4d 00 40 00 00 00 00 00 1a 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=0 milliseconds resid=1 Incoming data, len=25: 00 80 00 00 15 00 02 03 05 06 0d 0e 10 18 19 2f 30 10 31 32 33 34 35 36 37 38 3e scsiGetSupportedLogPages: number of unreported (standard) log pages: 1 (sub-pages: 0) >>>> do_scsi_cmnd_io: sg_io_ver=3 [log sense: 4d 00 6f 00 00 00 00 00 04 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=21 milliseconds resid=0 Incoming data, len=4: 00 af 00 00 08 >>>> do_scsi_cmnd_io: sg_io_ver=3 [log sense: 4d 00 6f 00 00 00 00 00 0c 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=17 milliseconds resid=0 Incoming data, len=12: 00 af 00 00 08 00 00 03 04 00 00 23 00 >>>> do_scsi_cmnd_io: sg_io_ver=3 [request sense: 03 00 00 00 12 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=0 milliseconds resid=0 Incoming data, len=18: 00 70 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 00 10 00 00 >>>> do_scsi_cmnd_io: sg_io_ver=3 [log sense: 4d 00 4d 00 00 00 00 00 04 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=0 milliseconds resid=0 Incoming data, len=4: 00 8d 00 00 0c >>>> do_scsi_cmnd_io: sg_io_ver=3 [log sense: 4d 00 4d 00 00 00 00 00 10 00 ] scsi_status=0x0, sg_transport_status=0x0, sg_driver_status=0x0 sg_info=0x0 sg_duration=1 milliseconds resid=0 Incoming data, len=16: 00 8d 00 00 0c 00 00 43 02 00 23 00 01 43 02 00 ff SMART Health Status: OK work-pc-diagnostics-20190906-0349.zip
  13. i want to ask if we can change the layout and generally make adjustments to the 'dashboard'. specifically i installed and setup 'disk layout' once it became compatible with Version 6.7.0 2019-05-08. it works now just as before. however it showed up on the dashboard which is fine, but its waaaaay down on the left column with a bunch of blank space above it before the next block of info, which happens to be power UPS.
  14. seems that unraid doesn't love my awesome setup as much as i do.
  15. i tried changing the following, then killing nginx and starting it back up again and it didn't help at all. same as original error and the file possibly regenerates as per the first line; negating the changes. root@WORK-PC:/etc/nginx/conf.d# head emhttp-servers.conf.backup # Generated by /etc/rc.d/rc.nginx # # set root directory for requests # root /usr/local/emhttp; # # limit the amount of failed auth requests per IP address # limit_req_zone $binary_remote_addr zone=authlimit:1m rate=30r/m; # root@WORK-PC:/etc/nginx/conf.d# head emhttp-servers.conf # Generated by /etc/rc.d/rc.nginx # # set root directory for requests # root /usr/local/emhttp; # # limit the amount of failed auth requests per IP address # limit_req_zone $binary_remote_addr zone=authlimit:10m rate=1r/s; # i looked in /etc/php-fpm/php-fpm.conf found nothing i wanted to mess with. so going back to .. i found ... grep '/usr/local/emhttp' /etc/nginx/conf.d/emhttp-servers.conf root /usr/local/emhttp; looking in /usr/local/emhttp/ i found ... root@WORK-PC:/usr/local/emhttp# ls -latrh total 28K lrwxrwxrwx 1 root root 15 Jun 19 2016 webGui -> plugins/dynamix/ lrwxrwxrwx 1 root root 17 Jun 19 2016 state -> /var/local/emhttp/ lrwxrwxrwx 1 root root 4 Jun 19 2016 mnt -> /mnt/ lrwxrwxrwx 1 root root 8 Jun 19 2016 log -> /var/log/ lrwxrwxrwx 1 root root 5 Jun 19 2016 boot -> /boot/ -rw-r--r-- 1 root root 4.3K Mar 13 2018 update.php -rw-r--r-- 1 root root 26 Sep 6 2018 robots.txt -rw-r--r-- 1 root root 330 Sep 27 2018 logout.htm -rw-r--r-- 1 root root 6.9K Sep 28 2018 logging.htm -rw-r--r-- 1 root root 3.4K Nov 1 22:42 update.htm lrwxrwxrwx 1 root root 39 Apr 15 17:59 work-pc-flash-backup-20190415-1756.zip -> /work-pc-flash-backup-20190415-1756.zip lrwxrwxrwx 1 root root 55 Apr 15 18:58 work-pc-flash-backup-20190415-1853.zip -> /mnt/user/system/work-pc-flash-backup-20190415-1853.zip drwxr-xr-x 31 root root 620 Apr 15 21:20 plugins/ drwxr-xr-x 10 root root 200 Apr 15 21:20 ../ lrwxrwxrwx 1 root root 55 Apr 19 12:58 work-pc-flash-backup-20190419-1251.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1251.zip lrwxrwxrwx 1 root root 55 Apr 19 13:07 work-pc-flash-backup-20190419-1301.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1301.zip lrwxrwxrwx 1 root root 55 Apr 19 13:13 work-pc-flash-backup-20190419-1308.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1308.zip lrwxrwxrwx 1 root root 55 Apr 19 17:41 work-pc-flash-backup-20190419-1734.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1734.zip lrwxrwxrwx 1 root root 55 Apr 19 17:49 work-pc-flash-backup-20190419-1743.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1743.zip lrwxrwxrwx 1 root root 55 Apr 19 17:56 work-pc-flash-backup-20190419-1750.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1750.zip lrwxrwxrwx 1 root root 55 Apr 19 18:01 work-pc-flash-backup-20190419-1754.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1754.zip drwxr-xr-x 3 root root 440 Apr 19 18:01 ./ so i temporarily enabled the system share and copied the latest usb backup off and deleted the rest. its not a perfect fix, but a good enough workaround for me.
  16. there doesn't seem to be anything in that diagnostic, anyone tell me what they would be looking for?
  17. fair enough, thank you for the response. does anyone have any experience talking to the iom6 controller from a non-netapp server. i believe i would telnet into it? no that can't be right, just connect on a serial terminal, maybe?
  18. thanks work-pc-diagnostics-20190415-2302.zip
  19. I wonder if anyone has any experience with this. so when i have spin down disabled i do not get these errors. i am running a Lenovo desktop, connected to NetApp DS4246 72TB 24x 3TB 7.2K SATA X308A-R5 with a Dell LSI SAS 9202-16e 6Gb/s SAS Host Bus Adapter. I am hoping to be able to figure out how to spin down drives without the error. (ill have to find my serial adapter and try to connect to the storage shelf but i also want to figure out how to properly send shutdown command to the shel when the ups shuts down the server in case of power outage). i only bring that up because i am wondering if they two could be solved with a similar fix. that is connecting usb to serial adapter to the server and figuring out how to tell unraid (or slackware) to issue commands to the netapp. Commands like spinning down and up drives, or shutting down or turning on the whole shelf. desktop details Model: Custom M/B: LENOVO - SHARKBAY CPU: Intel® Core™ i5-4570 CPU @ 3.20GHz HVM: Enabled IOMMU: Enabled Cache: 1024 kB, 256 kB, 6144 kB Memory: 32 GB (max. installable capacity 32 GB) Network: eth0: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.18.20-unRAID x86_64 OpenSSL: 1.1.1a Uptime: 0 days, 04:34:28 system log errors ErrorWarningSystemArrayLogin Apr 15 21:45:49 WORK-PC kernel: mdcmd (49): spindown 9 Apr 15 21:45:50 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:50 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:51 WORK-PC kernel: mdcmd (50): spindown 9 Apr 15 21:45:52 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:52 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:53 WORK-PC kernel: mdcmd (51): spindown 9 Apr 15 21:45:54 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:54 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:55 WORK-PC kernel: mdcmd (52): spindown 9 Apr 15 21:45:56 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:56 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:57 WORK-PC kernel: mdcmd (53): spindown 9 Apr 15 21:45:58 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:58 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:59 WORK-PC kernel: mdcmd (54): spindown 9 Apr 15 21:46:00 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:00 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:01 WORK-PC kernel: mdcmd (55): spindown 9 Apr 15 21:46:02 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:02 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:03 WORK-PC kernel: mdcmd (56): spindown 9 Apr 15 21:46:04 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:04 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:05 WORK-PC kernel: mdcmd (57): spindown 9 Apr 15 21:46:06 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:06 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:07 WORK-PC kernel: mdcmd (58): spindown 9 Apr 15 21:46:08 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:08 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:09 WORK-PC kernel: mdcmd (59): spindown 9 Apr 15 21:46:10 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:10 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:11 WORK-PC kernel: mdcmd (60): spindown 9 Apr 15 21:46:13 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:13 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:14 WORK-PC kernel: mdcmd (61): spindown 9 Apr 15 21:46:15 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:15 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:16 WORK-PC kernel: mdcmd (62): spindown 9
  20. Model: Custom M/B: LENOVO - SHARKBAY CPU: Intel® Core™ i5-4570 CPU @ 3.20GHz HVM: Enabled IOMMU: Enabled Cache: 1024 kB, 256 kB, 6144 kB Memory: 32 GB (max. installable capacity 32 GB) . <----------------------- DDR3 though i think. Network: eth0: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.18.20-unRAID x86_64 OpenSSL: 1.1.1a Uptime: 0 days, 02:48:02
  21. when I goto 'Main' and then 'Flash' and then click 'flash backup' it then says 'creating flash backup' . it just says 'Please wait... creating Flash backup zip file (this may take several minutes)' but it never completes. here is what the log say. Apr 15 17:58:52 WORK-PC nginx: 2019/04/15 17:58:52 [error] 8187#8187: *3235 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.109, server: , request: "POST /webGui/include/Download.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.107", referrer: "http://192.168.1.107/Main/Flash?name=flash" i made sure that popups blocker and ad blockers were disabled and enabled flash etc, so that the page should be able to do whatever it wants. i should also note i have tried from three different computers, two windows 10 , and one mac mojave. and i have tried rebooting the unraid server and trying again with minimal dockers and no vm's running. i have taken a backup using the Backup/Restore appdata plugin but i really want the zip file version that i could use with the usb creation tool if it ever became necessary. any help would be greatly appreciated.