Timbiotic
-
Posts
209 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Timbiotic
-
-
Again I think something is whacky , another 4tb sas drive is doing the background scan thing and spins down just fine ... same model, same firmware, same settings... wtf
-
nevermind i downloaded the smart report and its running a background smart scan. i didnt trigger it, is that normal when adding new drive? or is it just a disk timer that says now is the time?
-
i know its “sas” and unraid doesnt spin down sas. But i just put in an identical 4tb drive with same firmware as my others and unraid will spin down the others but not this one. is it possible these m1015 controllers get weird with both ports connected? or maybe its the disk settings themselves in the pa page.
-
I can’t monitor so how do you know when done? Also I couldn’t tell it was going so I started mover twice...
-
BEnson found it in the diag from earlier i posted
Sep 8 15:00:43 lillis emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/startScript.sh /tmp/user.scripts/tmpScripts/IDLE SAS/script
Sep 8 15:04:52 lillis kernel: mdcmd (55): ?
Sep 8 15:05:23 lillis kernel: mdcmd (56): spindown 0 -
Do you think me manually spinning down the drive could have caused it? Is there anytime only parity would be active legitimately? I only spun it down when all other members were spun down.
-
12 hours ago, johnnie.black said:
In the SMART report.
Does anything in here jump out to you? It says it healthy in the smart column on the main dashboard. But it still is disabled. I think i will swap out the drive now. But its "new" from ebay. I can see by the smart report that the reseller just pulled it from something and resold it .
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: ST6000NM0285
Revision: EF02
Compliance: SPC-4
User Capacity: 6,001,175,126,016 bytes [6.00 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LU is fully provisioned
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Logical Unit id: 0x5000c5008696d16b
Serial number: ZAD0Q1E70000C721BAUY
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Tue Sep 10 15:00:10 2019 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
Read Cache is: Enabled
Writeback Cache is: Enabled=== START OF READ SMART DATA SECTION ===
SMART Health Status: OKGrown defects during certification <not available>
Total blocks reassigned during format <not available>
Total new blocks reassigned <not available>
Power on minutes since format <not available>
Current Drive Temperature: 28 C
Drive Trip Temperature: 60 CManufactured in week 07 of year 2017
Specified cycle count over device lifetime: 10000
Accumulated start-stop cycles: 715
Specified load-unload count over device lifetime: 300000
Accumulated load-unload cycles: 1679
Elements in grown defect list: 0Vendor (Seagate Cache) information
Blocks sent to initiator = 2973709184
Blocks received from initiator = 2118791472
Blocks read from cache and sent to initiator = 48672929
Number of read and write commands whose size <= segment size = 271022
Number of read and write commands whose size > segment size = 30068Vendor (Seagate/Hitachi) factory information
number of hours powered up = 664.45
number of minutes until next internal SMART test = 12Error 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: 3967346996 0 0 3967346996 0 8119.609 0
write: 0 0 0 0 0 12080.227 0Non-medium error count: 0
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Completed - 648 - [- - -]
# 2 Background short Completed - 529 - [- - -]
# 3 Background long Completed - 503 - [- - -]
# 4 Background short Completed - 493 - [- - -]
# 5 Background short Aborted (by user command) - 460 - [- - -]Long (extended) Self-test duration: 28041 seconds [467.4 minutes]
Background scan results log
Status: no scans active
Accumulated power on time, hours:minutes 664:27 [39867 minutes]
Number of background scans performed: 0, scan progress: 0.00%
Number of background medium scans performed: 0Protocol Specific port log page for SAS SSP
relative target port id = 1
generation code = 0
number of phys = 1
phy identifier = 0
attached device type: SAS or SATA device
attached reason: unknown
reason: unknown
negotiated logical link rate: phy enabled; 6 Gbps
attached initiator port: ssp=1 stp=1 smp=1
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000c5008696d169
attached SAS address = 0x500605b0094e6eb2
attached phy identifier = 6
Invalid DWORD count = 8
Running disparity error count = 8
Loss of DWORD synchronization = 21
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 8
Running disparity error count: 8
Loss of dword synchronization count: 21
Phy reset problem count: 0
relative target port id = 2
generation code = 0
number of phys = 1
phy identifier = 1
attached device type: no device attached
attached reason: unknown
reason: unknown
negotiated logical link rate: phy enabled; unknown
attached initiator port: ssp=0 stp=0 smp=0
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000c5008696d16a
attached SAS address = 0x0
attached phy identifier = 0
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronization = 0
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 0
Running disparity error count: 0
Loss of dword synchronization count: 0
Phy reset problem count: 0 -
15 hours ago, Benson said:
Suggest disable the "IDLE SAS" script
Sep 8 15:00:43 lillis emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/startScript.sh /tmp/user.scripts/tmpScripts/IDLE SAS/script
Sep 8 15:04:52 lillis kernel: mdcmd (55): ?
Sep 8 15:05:23 lillis kernel: mdcmd (56): spindown 0it is disabled i only run it manually, trying to figure it out still. The mdcmd spindown 0 was me manually doing it in cli to see if the sas drive responded. Surprisingly it did.
-
12 hours ago, johnnie.black said:
Looks more like a connection problem, replace/swap cables/backplane slot and try again, you can also run an extended SMART test.
I ran an extended smart test but how do you see results? It says completed in the download report but not much else. I’ll try swapping the disk tomorrow to rule out cables.
-
When you say try again do you mean rebuild parity ? I reseated everything and made sure cable was tight. Do I need to remove and re add it again for a whole new rebuild ?
-
it rebuilt and everything seemed fine then it disabled again. attaching recent before reboot
-
stopped array
set no device for parity
started array
stopped array
set back parity
started array and its rebuilding...
hopefully there isnt anything more serious wrong.
im wondering if it was the manual sdparm spin down i did before shutting down array. sure hope they figure out sas spin down.
if someone wants to check diagnostic and can explain to me why parity was disabled that would be helpful.
-
On latest unraid 6.7.2 and just moved hardware to upgrade. everything came up great except parity which is disabled. any ideas why? attaching diagnostics
-
So it is the spin down attempt that is triggering that error nothing else? I don't get why all my other SAS disks spin down fine. I think it is firmware.
And i thought SAS was supported now based on the RC of 6.7.0
-
I recently added a new SAS 6tb parity drive that refuses to spin down unless i manually use sg_start --stop command on it. I am also getting a ton of these errors in syslog. I am working on a script to spin down the drive but cannot figure out a way to determine its inactive.
Here is the errors are they just confirming HDPARM cannot spin down the drive?
Sep 5 04:40:01 lillis kernel: mdcmd (161166): spindown 0
Sep 5 04:40:01 lillis kernel: md: do_drive_cmd: disk0: ATA_OP e0 ioctl error: -5
Sep 5 04:40:01 lillis emhttpd: error: mdcmd, 2640: Input/output error (5): write
Sep 5 04:40:02 lillis kernel: mdcmd (161167): spindown 0
Sep 5 04:40:02 lillis kernel: md: do_drive_cmd: disk0: ATA_OP e0 ioctl error: -5
Sep 5 04:40:02 lillis emhttpd: error: mdcmd, 2640: Input/output error (5): write
Sep 5 04:40:03 lillis emhttpd: error: mdcmd, 2640: Input/output error (5): write
Sep 5 04:40:03 lillis kernel: mdcmd (161168): spindown 0
Sep 5 04:40:03 lillis kernel: md: do_drive_cmd: disk0: ATA_OP e0 ioctl error: -5
Sep 5 04:40:04 lillis kernel: mdcmd (161169): spindown 0
Sep 5 04:40:04 lillis emhttpd: error: mdcmd, 2640: Input/output error (5): write
Sep 5 04:40:04 lillis kernel: md: do_drive_cmd: disk0: ATA_OP e0 ioctl error: -5
Sep 5 04:40:05 lillis kernel: mdcmd (161170): spindown 0
Sep 5 04:40:05 lillis kernel: md: do_drive_cmd: disk0: ATA_OP e0 ioctl error: -5
Sep 5 04:40:05 lillis emhttpd: error: mdcmd, 2640: Input/output error (5): write
Sep 5 04:40:06 lillis kernel: mdcmd (161171): spindown 0
Sep 5 04:40:06 lillis kernel: md: do_drive_cmd: disk0: ATA_OP e0 ioctl error: -5
Sep 5 04:40:06 lillis emhttpd: error: mdcmd, 2640: Input/output error (5): write
Sep 5 04:40:07 lillis kernel: mdcmd (161172): spindown 0
Sep 5 04:40:07 lillis emhttpd: error: mdcmd, 2640: Input/output error (5): write
Sep 5 04:40:07 lillis kernel: md: do_drive_cmd: disk0: ATA_OP e0 ioctl error: -5
Sep 5 04:40:08 lillis kernel: mdcmd (161173): spindown 0
Sep 5 04:40:08 lillis emhttpd: error: mdcmd, 2640: Input/output error (5): write
Sep 5 04:40:08 lillis kernel: md: do_drive_cmd: disk0: ATA_OP e0 ioctl error: -5
Sep 5 04:40:09 lillis kernel: mdcmd (161174): spindown 0I am on 6.7.2
-
that method didnt work it appears only sg utils will spin down this disk. or parity is sending "in use flag?"
-
Hopefully it wont mess with anything else but I see that he is working with sdparm in upcoming releases.
gonna try this to manually set the standby spin down for now will update if it works https://zackreed.me/spindown-sas-disks/
-
Ok I found I can spin down the disk with this command sg_start —stop /dev/sde
im wondering if there is an APM setting I need to change. Unfortunately hdparam doesn’t seem to work and I’m not real familiar with sg tools
-
I’m wondering if it’s a controller issue. From the wiki it even says it supports sas spin down on my controller but only mentions 3tb drives
This cards are rebranded LSI 9240-8i cards. They can be cross-flashed with the 9211-8i firmware.
IBM ServeRAID M1015
Intel RS2WC080
Dell Perc H310 dedicated instructions will be included in the wiki later on
Dell Perc H200 dedicated instructions will be included in the wiki later on
Lenovo RAID 500 dedicated instructions will be included in the wiki later on
20.10.1-0037 (APP-2.120.54-1235) / 15-APR-11
Only iMR mode available.
LSI MegaRAID SAS2008 Controller.zip - 5.32 MB (Windows)
Linux Driver: megaraid_sas - supports the LSI SAS1078, SAS1078 GEN2, SAS1079 GEN2, SAS0073 and SAS0071 chipsets. Though is is an old version indeed. (Thanks to "BRiT"s prior post)
unRAID Support: Driver not included at this point.
Drive Spin Down support: YES (UPDATE: Added as of 5.0Beta7)
Drive Temp Readings: YES
3TB Drive Support with this card: YES (UPDATE: 5.0Beta7 added 3TB Drive support)
Update: Convert your LSI MegaRAID controller card with LSI SAS2008 chipset to a Plain SAS2008 controller card (IT or IR mode), will look and feel like a LSI SAS9211-8i, and will be ready to use with unRAID (BIG THANKS to KKM for creating the empty.bin, so you dont need to have to worry about which sbr to obtain and use.)
IBM ServeRAID M1015 (tested successfully)
Intel RS2WC080 (tested successfully)
LSI MegaRAID to SAS2008(P10).zip - 6.38 MB (DOS, via bootable usb key)
LSI MegaRAID to SAS2008(P11).zip - 5.87 MB (DOS, via bootable usb key)
LSI MegaRAID to SAS2008(P20).zip - 4.1 MB (FREEDOS, via bootable usb key)
Please read the __READMEFIRST.txt file so you are clear as to all the steps and why it is important not to skip any steps.
Converting it follows all details in the post above for the LSI SAS2008 chipset (firmware release, support, etc.)
-
Yes I just had to upgrade the firmware on them.
ST33000650SS - 3tb
ST4000NM0023 - 4tb
both work fine with “0005” firmware
ST6000NM0285 - 6tb
is not spinning down and I can’t find any other firmware than the ”ef02” that came on it.
-
Ok I’ll just let er rebuild. Thanks!
-
I have 8 seagate sas 3 and 4 tb drives that spin down fine on 005 firmware. Is there a parameter I can check to see if it’s set right? Using m1015 in it mode
-
In the past I’ve had to upgrade the firmware then I can spin down my sas drives. I’m guessing it’s just a flag that isn’t set. But I got a much larger drive now for parity and can’t find any new firmware for it. Does anyone know sas seagate drives and how to allow them to spin down? The model is ST6000NM0285 and I can’t find any firmware for it. No matter what I try I can’t get it to spin down. It’s on a m1015 lsa 2008 controller.
-
Uggg this is killing me 9 hours yesterday to rebuild 33mb empty drive. Then today I was trying to figure out how to spin down my new 6tb parity disk and was practicing on the new blank drive but got it in the red x state in the process. Now the only way I could bring it back was unassigning and reassign. Now another 9 hour rebuild for 0 data?!! Isn’t there a way to just remove it and add it without rebuilding blank data?
[Support] Aria2 + WebUI
in Docker Containers
Posted
I am not familiar with aria2 but im having issues with sonarr passing to rutorrent when encrypted. I hear aria2 can fix the magnet links so it will work. Its even going to be added to sonarr eventually. Will this docker be able to monitor my rutorrent docker and fix the magnet links? And if so can someone point me to how to do this? Sorry if this is the wrong place to ask.