s0b
-
Posts
13 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by s0b
-
-
@JorgeB do you know if the 9211 can handle the server (at a lower speed) while I get the 9300?
-
Hello!
Im working on an evolution of my current Unraid server which currently is setted up in a regular tower PC heavily modified to host 12 HDDs. For now Im going to focus on case + SATA controller.
For the case I have choose this one and as you can read in the case description:
QuoteThis has 3 x 8643 Mini SAS connectors. 2 Input and 1 output.
Requires only 4/8 port HBA or raid card to run all 24 drives with built in expander.
12GB Backplane With Expander Built In
So I been looking into options for the SATA controller and I'm kind of lost choosing which one is a better option:
Broadcom SAS 9300-8i - 400$
Broadcom 9400-8i8e - 600$ (what means the 8e?)Broadcom HBA 9500-8i - 430$
Seems like the 9300 is the go-to option in some other users build in the forum but Im tempted about getting the 9500 as I understand that its newer technology and seems like its supported since 6.9.0.My problem is that I don't know enough about SATA controller cards, I only owned a 9211 which is plugged in my current Unraid server. Would like to get your opinion about what could be a good match for the new server thinking on the long term even if that means a bigger investment.
Thanks! -
18 minutes ago, ich777 said:
Also from what I see the transcoding is working perfectly fine with your card, try a few other files please and report back.
I been playing a bit with files and configs and seems like disabling the option "Enable HDR tone mapping" in the Plex transcode options reduces a lot the CPU load. Will keep chasing this issue in the Docker side as seems like the drivers are working as expected.
Thanks again for this plugin and your support!-
1
-
-
I been using Unraid 6.8.3 with the old Unraid-Nvidia plugin until a few hours ago and I upgraded this morning to Unraid 6.9.1 and this plugin (thanks for doing it!).
Im having a weird problem, hopefully you can see what Im doing wrong. Plex is detecting my GPU and seems to do some transcoding with it but the CPU is impacted heavily while the GPU is under a low work load. This wasn't the case before, the CPU usage rarely went up of 10% while transcoding. This are a few screenshots that I took:
I have tried using the official and LinuxServer.io Plex docker images and both shows the same problem so Im coming here just in case you get some ideas about what could be happening -
Thanks! Just downloaded the latest version and created a user script to execute it. Will sleep better now
-
1
-
-
After checking the script seems like adding single quotes on the line 164 solves my issue reported above
From:eval "find ${media_shares_match} -type f ${include_folders_cmd} ${include_extensions_cmd} ${exclude_folders_cmd} ${exclude_extensions_cmd} -exec ${chattr_cmd} {} \;"To:
eval "find '${media_shares_match}' -type f ${include_folders_cmd} ${include_extensions_cmd} ${exclude_folders_cmd} ${exclude_extensions_cmd} -exec ${chattr_cmd} {} \;"@binhex can create a pull request if you prefer
-
Truly appreciate this script. I never had problems with ransomware but heard enough stories to fear them.
Mistakes were made when I setted up my shares and I used spaces in some of them, when I try to run the scripts this is the output:
root@Fone:~# /mnt/user/appdata/no_ransom/no_ransom.sh --lock-files 'yes' --media-shares 'short films' --debug 'yes' [info] Running no_ransom.sh script... [info] Checking we have all required parameters before running... [info] Finding share that match 'short films' on disk '/mnt/disk1'... [debug] find /mnt/disk1 -maxdepth 1 -type d -name short films [info] Share found, processing media share '/mnt/disk1/short films' using 'chattr' recursively... [debug] find /mnt/disk1/short films -type f \( -name "*.*" \) -exec chattr +i {} \; find: ‘/mnt/disk1/short’: No such file or directory find: ‘films’: No such file or directory [info] Processing finished for disk '/mnt/disk1' [info] [info] Finding share that match 'short films' on disk '/mnt/disk2'... [debug] find /mnt/disk2 -maxdepth 1 -type d -name short films [debug] No matching media share for disk '/mnt/disk2' [info] Processing finished for disk '/mnt/disk2' [info] [info] Finding share that match 'short films' on disk '/mnt/disk3'... [debug] find /mnt/disk3 -maxdepth 1 -type d -name short films [info] Share found, processing media share '/mnt/disk3/short films' using 'chattr' recursively... [debug] find /mnt/disk3/short films -type f \( -name "*.*" \) -exec chattr +i {} \; find: ‘/mnt/disk3/short’: No such file or directory find: ‘films’: No such file or directory [info] Processing finished for disk '/mnt/disk3' [info] [info] Finding share that match 'short films' on disk '/mnt/disk4'... [debug] find /mnt/disk4 -maxdepth 1 -type d -name short films [info] Share found, processing media share '/mnt/disk4/short films' using 'chattr' recursively... [debug] find /mnt/disk4/short films -type f \( -name "*.*" \) -exec chattr +i {} \; find: ‘/mnt/disk4/short’: No such file or directory find: ‘films’: No such file or directory [info] Processing finished for disk '/mnt/disk4' [info] [info] Finding share that match 'short films' on disk '/mnt/disk5'... [debug] find /mnt/disk5 -maxdepth 1 -type d -name short films [debug] No matching media share for disk '/mnt/disk5' [info] Processing finished for disk '/mnt/disk5' [info] [info] Finding share that match 'short films' on disk '/mnt/disk6'... [debug] find /mnt/disk6 -maxdepth 1 -type d -name short films [info] Share found, processing media share '/mnt/disk6/short films' using 'chattr' recursively... [debug] find /mnt/disk6/short films -type f \( -name "*.*" \) -exec chattr +i {} \; find: ‘/mnt/disk6/short’: No such file or directory find: ‘films’: No such file or directory [info] Processing finished for disk '/mnt/disk6' [info] [info] Finding share that match 'short films' on disk '/mnt/disk7'... [debug] find /mnt/disk7 -maxdepth 1 -type d -name short films [info] Share found, processing media share '/mnt/disk7/short films' using 'chattr' recursively... [debug] find /mnt/disk7/short films -type f \( -name "*.*" \) -exec chattr +i {} \; find: ‘/mnt/disk7/short’: No such file or directory find: ‘films’: No such file or directory [info] Processing finished for disk '/mnt/disk7' [info] [info] Finding share that match 'short films' on disk '/mnt/disk8'... [debug] find /mnt/disk8 -maxdepth 1 -type d -name short films [info] Share found, processing media share '/mnt/disk8/short films' using 'chattr' recursively... [debug] find /mnt/disk8/short films -type f \( -name "*.*" \) -exec chattr +i {} \; find: ‘/mnt/disk8/short’: No such file or directory find: ‘films’: No such file or directory [info] Processing finished for disk '/mnt/disk8' [info] [info] Finding share that match 'short films' on disk '/mnt/disks'... [debug] find /mnt/disks -maxdepth 1 -type d -name short films [debug] No matching media share for disk '/mnt/disks' [info] Processing finished for disk '/mnt/disks' [info] [info] no_ransom.sh script finished
After running it I have verified running "lsattr /mnt/user/short\ films/" that the files are still unprotected. Can I run the script somehow without changing my share names? -
Defnitely you were right, I been going crazy the whole morning and the lock state was the issue. Adding the drive back to the Synology, running again the secure erase and finally adding the drive to a storage pool unlocked everything. Its working again.
In the following link there is a discussion about how to unlock a drive with a few commands whick was locked with a Synology secure erase but I didnt wanted to take shortcuts: https://community.synology.com/enu/forum/17/post/77120?page=1&sort=oldest
-
Synology reported that the security erase was finished. I will put a 1tb drive in the first bay of Synology to install the system and the failing drive in the second bay to redo the secure erase. Will report back.
Appreciate it Benson, I missed that locked state, hopefully this will fix it.
-
Yes, I haven't finished the zeroing with dd because Synology did the whole process. If remember correctly it took about ~5h for Synology to wipe the hard drive, that was the last time that the drive was running properly.
This is the SMART report extracted from the Unraid server this morming right before moving it to the USB enclosure:
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.19.107-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD60EFRX-68L0BN1 Serial Number: WD-WX11D37XXX09 LU WWN Device Id: 5 0014ee 26401077b Firmware Version: 82.00A82 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5700 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Sun Jul 19 09:43:49 2020 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: ENABLED, PW level HIGH, **LOCKED** [SEC4] Wt Cache Reorder: Unknown (SCT not supported if ATA Security is LOCKED) === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: ( 4424) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 698) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303d) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 0 3 Spin_Up_Time POS--K 197 196 021 - 9116 4 Start_Stop_Count -O--CK 095 095 000 - 5206 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 200 200 000 - 0 9 Power_On_Hours -O--CK 094 094 000 - 4678 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 096 096 000 - 4086 192 Power-Off_Retract_Count -O--CK 200 200 000 - 25 193 Load_Cycle_Count -O--CK 199 199 000 - 5232 194 Temperature_Celsius -O---K 120 107 000 - 32 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 100 253 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 100 253 000 - 0 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 5 Comprehensive SMART error log 0x03 GPL R/O 6 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 8 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x0c GPL R/O 2048 Pending Defects log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0-0xa7 GPL,SL VS 16 Device vendor specific log 0xa8-0xb6 GPL,SL VS 1 Device vendor specific log 0xb7 GPL,SL VS 54 Device vendor specific log 0xbd GPL,SL VS 1 Device vendor specific log 0xc0 GPL,SL VS 1 Device vendor specific log 0xc1 GPL VS 93 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (6 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 4482 - # 2 Short offline Completed without error 00% 4067 - # 3 Short offline Completed without error 00% 3655 - # 4 Short offline Completed without error 00% 3279 - # 5 Short offline Completed without error 00% 3141 - # 6 Short offline Completed without error 00% 2853 - # 7 Short offline Completed without error 00% 2763 - # 8 Short offline Completed without error 00% 2685 - # 9 Short offline Completed without error 00% 2552 - #10 Short offline Completed without error 00% 2469 - #11 Short offline Completed without error 00% 2394 - #12 Short offline Completed without error 00% 2316 - #13 Short offline Completed without error 00% 2202 - #14 Short offline Completed without error 00% 2125 - #15 Short offline Completed without error 00% 1844 - #16 Short offline Completed without error 00% 1771 - #17 Short offline Completed without error 00% 1712 - #18 Short offline Completed without error 00% 1371 - 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. SCT Commands not supported if ATA Security is LOCKED Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 2) == 0x01 0x008 4 4086 --- Lifetime Power-On Resets 0x01 0x010 4 4678 --- Power-on Hours 0x01 0x018 6 23391117118 --- Logical Sectors Written 0x01 0x020 6 31056331 --- Number of Write Commands 0x01 0x028 6 82571805118 --- Logical Sectors Read 0x01 0x030 6 255971251 --- Number of Read Commands 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 4570 --- Spindle Motor Power-on Hours 0x03 0x010 4 4502 --- Head Flying Hours 0x03 0x018 4 5258 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 0 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 131074 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 32 --- Current Temperature 0x05 0x010 1 38 --- Average Short Term Temperature 0x05 0x018 1 35 --- Average Long Term Temperature 0x05 0x020 1 45 --- Highest Temperature 0x05 0x028 1 18 --- Lowest Temperature 0x05 0x030 1 40 --- Highest Average Short Term Temperature 0x05 0x038 1 22 --- Lowest Average Short Term Temperature 0x05 0x040 1 35 --- Highest Average Long Term Temperature 0x05 0x048 1 26 --- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 60 --- Specified Maximum Operating Temperature 0x05 0x060 4 0 --- Time in Under-Temperature 0x05 0x068 1 0 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 5389 --- Number of Hardware Resets 0x06 0x010 4 1277 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) No Defects Logged SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 16 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 17 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FIS 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x8000 4 146057 Vendor specificEdit: Forgot to mention that this report is extracted after Synology's secure erase
-
Hi all,
Recently I started migrating everything from a 2 bay Synology to an Unraid server. As I got some new drives, I migrated all the data over the network from the Synology drives to the new Unraid drives and, for some reason, I decided to run a secure erase in one of the Synology drives. Then I plugged the two old drives from Synology to Unraid. I was able to run a preclear on the drive that I hadn't secure erased and right now is ready to be included in the array. The problem is in the secure erased disk (a WD Red 6Tb drive).
When I plugged the failing drive in the Unraid server along with the other one, I was able to start the preclear process but it finished in ~5mins. Then I wasn't able to move it into the array because it was giving failing reads in every sector.
I have moved the drive to a USB enclosure and plugged it into a Linux machine, this is the result of a "parted -l"
Error: /dev/sdb: unrecognised disk label Model: ASMT 2115 (scsi) Disk /dev/sdb: 6001GB Sector size (logical/physical): 512B/4096B Partition Table: unknown Disk Flags:
I'm able to run a "sudo dd if=/dev/zero of=/dev/sdb status=progress" but I haven't let it finish as I suppose that this is was the Synology secure erase did. Every other command like "fdisk -l /dev/sdb" returns:
fdisk: cannot open /dev/sdb: Input/output errorIm pretty confident that in terms of hardware the drive is ok. I have checked it with the WD diagnosis tool and it says that the drive is healthy. Do you have any suggestion that what could be happening?
Thanks!
[Script] binhex - no_ransom.sh
in User Customizations
Posted
I really need this. Im tempted to do it myself even if I never did an Unraid plugin, will give it a go.