FreakStyleee

Thanks Squid!

I am seeing the following log messages. Sep 17 11:47:43 DeadPool root: error: plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token These occur about one per second. I have uninstalled and reinstalled Unassigned Devices. Obviously the error goes away when the plugin is removed, but it returns when reinstalled. UnRaid version is 6.3.5 Also note I see the same error for PreClear plugin as well.

Thanks johnnie. I didn't see your reply until after I had worked my way through it, but those were the exact steps I used. Your post also saved me from writing out the steps should someone else run into the same problem and need the reassurance of knowing exactly what to do. Thanks to all the took the time to respond and provide assistance. It is much appreciated. Marking this as [sOLVED].

Where do I tell it to "trust parity" so that i rebuilds the data that was written directly to parity during the time the disk was offline? I don't see an option on the start array section. Currently it say "Stopped. new parity disk installed" I assume this is done via the Tools==>New Config. Reassign drives as before but now I should see the option. Scary based on the warning on the New Config page. But I take it this will force the drive in question to start reconstructing off the parity information.

trurl, thank you. I was just about to post how incorrect my comment was in this regard. I was looking through the files on the questionable drive. I can see via a NextCloud nginx syslog file entry stored on that disk that the drive stopped functioning in the array on Oct. 23. It happened to be the drive with the least used space and was getting all the new array data. I can also see that no new files were added to the drive after Oct.23. I will let parity do its thing and rebuild the drive. I assume that I don't need to get the drive order exactly the same as it was prior as long as my parity disk is accounted for correctly. Although I think I can piece together most of the drive order from the bits of information I have been able to find. I will just need to repopulate which disks should be included/excluded with shares.

I think I will mount the suspect disk with unassigned devices and see if it truly has problems (assuming that is possible). SMART test, is the file system readable, etc. If there are issue I will junk the drive and replace with a hot spare.

Thanks for your response. A1: No, unfortunately my backup is normally on my second licensed USB drive. I typically copy the the current prior to upgrades so that I can roll back easily, but I had used that for drive for spinning up a beta release of 6.2 a few month on a different box. I had not restored the current production configs to that drive. That said, I may have one on my cache drive or on the array, but until I spin up the drives I won't know. A2: No, I have had so few problems I have never run the diagnostics before last night. I do have a SMART report from the drive that showed offline that was taken 5 days ago. A3: No, as stated in the title I am running 6.1.9 so no dual parity. My apologies for not attaching the diag when creating the thread. Attached now. deadpool-diagnostics-20161108-2221.zip deadpool-smart-20161103-1951.zip

So... I have seen read through several threads about this same issue. And I just need confirmation that what I plan to do to recover is the best option. History I had noticed a drive mark X on the main page and a comment stating the data was being emulated. SMART showed passed so I figured I would get to it when time permitted. I ended up not getting to it before I suffered an unclean reboot. What I now see is a 0-byte super.dat and not drives assigned. Question Should I follow the steps from HERE? Note: I have not been able to find the exact drives assignments. I DO know which drive was parity. I see info in my disk.cfg that lists: diskComment.1="S/N: 9QJ6D0S000009022A1LG" diskComment.2="S/N: 9QJ6AJT300009021N373" diskComment.3="S/N: 9WK0FR710000C038DKM1" diskComment.4="S/N: 9QJ6EGPT00009019T6AB" diskComment.5="S/N: 9QJ669CY00009020YYCE" diskComment.6="S/N: 9QJ6EEBJ000090206DZ1" diskComment.7="S/N: 9QJ643VA00009019RQ3D" diskComment.8="S/N: 9QJ6D0S300009022Y6A3" cacheComment="S/N: OCZ-7139ICMP6O4OG353" Can I trust this as the assignments? I should also note these are all SAS drives and that I have 5 other drives (SATA) installed. Those 5 SATA drives don't show up in the disk.cfg. Plan [*]Assign SAS drives based on the disk.cfg (disk 8 in the original array was the drive with the X prior to reboot) [*]Assign SATA drives as best I can from memory and info from Server Layout plugin info [*]Upgrade to 6.2 (as this has fixes for a known cause of this type of issue) [*]Assign Parity drive and rebuild [*]Hope for the best Anything I should check first or do differently? Thanks

Thank you interwebtech! I knew I had to be missing something simple, but I am a simple minded simple man. I obviously didn't find that info anywhere. Guess I was looking in the wrong place, as always. Maybe it could be added to the plugin description in the first post here and in the Community App description.

I just installed the SSD Trim plugin, but could not find any way to configure settings in the GUI. Basically no icon for it on the settings page (or anywhere else I looked). Which prompted a removal, reboot and reinstall. Still no luck. A quick search lead me to the above comment. I do have a SSD cache drive but it is not creating the ssd-trim.cron you mention a few posts up. Any ideas as to why I am seeing this behavior? I am sure more information about my setup is required. I just don't know which outputs to provide

Please retry with the latest plugin version. The latest update fixed my issue! You truly are THEONE! All my SAS drives are now visible and can be assigned in the 'Data' tab. Manufacturer, Model, S/N, Firmware and Capacity fields populate correctly. Thank you once again for outstanding plugin and all the extra work to accommodate my particular use case.

Please test new version and post screenshot of Layout and DATA tab if possible. First off, Big thanks for the plugin and especially for working to add a fix for this non-typical device type. It is very much appreciated. So... I now see one of the SAS devices on the "Data" page. Yaaaay!!! But, not the other 7 that are currently installed. Here is what I have done so far: 1 - updated Server Layout plugin (SAS drive sde shows up on data page) 2 - rebooted & clicked "update Smartmontools Database" (sde is still present but no other SAS drives) 2 - updated unRaid to 6.1.3 & reboot & clicked "update Smartmontools Database" (sde is still present but no other SAS drives) I should also note, and this is not related to this plugin, but I think it may be relevant. When my array is started and the disks show 'green' on the Main page, I never see drive temps. Also, when I select a disk from the main page it always says the SAS drives are "Unavailable - disk must be spun up". When I select spin-up the page refreshes but nothing changes. I think support of SAS drives in unRaid as a whole is minimal. - EDIT - I forgot to mention that even when drives show active all 'smart' option buttons are greyed out with the exception of the afore mentioned 'spin-up' and the 'download'. Please post output of "ls -las /dev/disk/by-id". and "lsscsi" and "lsscsi -t" and "smartctl --all /dev/sdx" of one of the drives connected to the SAS. Are you using an Areca controller? Starting with the last question first then I will get to the outputs of the requested commands. The controller is a SuperMicro AOC-SAS2LP-MV8. Not sure which firmware rev., but I will check when I have a chance. I will also try adding a couple more SAS drives but connect them with a reverse cable directly to the MB SATA ports (been meaning to do that any way). Now for the requested command outputs: ls -las /dev/disk/by-id total 0 0 drwxr-xr-x 2 root root 800 Sep 22 14:50 ./ 0 drwxr-xr-x 6 root root 120 Sep 22 14:50 ../ 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 ata-OCZ-VERTEX2_OCZ-7139ICMP6O4OG353 -> ../../sdb 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 ata-OCZ-VERTEX2_OCZ-7139ICMP6O4OG353-part1 -> ../../sdb1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 scsi-35000c50010176e8f -> ../../sdg 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 scsi-35000c50010176e8f-part1 -> ../../sdg1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 scsi-35000c5001019aadb -> ../../sdi 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 scsi-35000c5001019aadb-part1 -> ../../sdi1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 scsi-35000c500101d1def -> ../../sdd 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 scsi-35000c500101d1def-part1 -> ../../sdd1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 scsi-35000c50010202287 -> ../../sdc 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 scsi-35000c50010202287-part1 -> ../../sdc1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 scsi-35000c5001020228f -> ../../sdh 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 scsi-35000c5001020228f-part1 -> ../../sdh1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 scsi-35000c500102089a7 -> ../../sdf 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 scsi-35000c500102089a7-part1 -> ../../sdf1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 scsi-35000c5001020c6ff -> ../../sdj 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 scsi-35000c5001020c6ff-part1 -> ../../sdj1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 scsi-35000c50020e5c55b -> ../../sde 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 scsi-35000c50020e5c55b-part1 -> ../../sde1 0 lrwxrwxrwx 1 root root 9 Sep 22 21:42 usb-SanDisk_Cruzer_Fit_4C532000040713109330-0:0 -> ../../sda 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 usb-SanDisk_Cruzer_Fit_4C532000040713109330-0:0-part1 -> ../../sda1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 wwn-0x5000c50010176e8f -> ../../sdg 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 wwn-0x5000c50010176e8f-part1 -> ../../sdg1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 wwn-0x5000c5001019aadb -> ../../sdi 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 wwn-0x5000c5001019aadb-part1 -> ../../sdi1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 wwn-0x5000c500101d1def -> ../../sdd 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 wwn-0x5000c500101d1def-part1 -> ../../sdd1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 wwn-0x5000c50010202287 -> ../../sdc 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 wwn-0x5000c50010202287-part1 -> ../../sdc1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 wwn-0x5000c5001020228f -> ../../sdh 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 wwn-0x5000c5001020228f-part1 -> ../../sdh1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 wwn-0x5000c500102089a7 -> ../../sdf 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 wwn-0x5000c500102089a7-part1 -> ../../sdf1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 wwn-0x5000c5001020c6ff -> ../../sdj 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 wwn-0x5000c5001020c6ff-part1 -> ../../sdj1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 wwn-0x5000c50020e5c55b -> ../../sde 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 wwn-0x5000c50020e5c55b-part1 -> ../../sde1 0 lrwxrwxrwx 1 root root 9 Sep 22 14:50 wwn-0x5e83a97f59908210 -> ../../sdb 0 lrwxrwxrwx 1 root root 10 Sep 22 14:50 wwn-0x5e83a97f59908210-part1 -> ../../sdb1 lsscsi [0:0:0:0] disk SanDisk Cruzer Fit 1.26 /dev/sda [1:0:0:0] disk HP DB1000BABFF HPD5 /dev/sdc [1:0:1:0] disk HP DB1000BABFF HPD8 /dev/sdd [1:0:2:0] disk HP MB1000FAMYU HPD2 /dev/sde [1:0:3:0] disk HP DB1000BABFF HPD5 /dev/sdf [1:0:4:0] disk HP DB1000BABFF HPD5 /dev/sdg [1:0:5:0] disk HP DB1000BABFF HPD5 /dev/sdh [1:0:6:0] disk HP DB1000BABFF HPD5 /dev/sdi [1:0:7:0] disk HP DB1000BABFF HPD5 /dev/sdj [2:0:0:0] disk ATA OCZ-VERTEX2 1.37 /dev/sdb lsscsi -t [0:0:0:0] disk usb: 1-1:1.0 /dev/sda [1:0:0:0] disk sas:0x5000c50010202285 /dev/sdc [1:0:1:0] disk sas:0x5000c500101d1ded /dev/sdd [1:0:2:0] disk sas:0x5000c50020e5c559 /dev/sde [1:0:3:0] disk sas:0x5000c500102089a5 /dev/sdf [1:0:4:0] disk sas:0x5000c50010176e8d /dev/sdg [1:0:5:0] disk sas:0x5000c5001020228d /dev/sdh [1:0:6:0] disk sas:0x5000c5001019aad9 /dev/sdi [1:0:7:0] disk sas:0x5000c5001020c6fd /dev/sdj [2:0:0:0] disk ata: /dev/sdb smartctl --all /dev/sdc - for a SAS drive that does not show up in the plugin smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.7-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: HP Product: DB1000BABFF Revision: HPD5 User Capacity: 1,000,204,886,016 bytes [1.00 TB] Logical block size: 512 bytes Rotation Rate: 7200 rpm Logical Unit id: 0x5000c50010202287 Serial number: 9QJ6D0S000009022A1LG Device type: disk Transport protocol: SAS Local Time is: Thu Sep 24 10:58:57 2015 MDT 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: 37 C Drive Trip Temperature: 68 C Elements in grown defect list: 0 Vendor (Seagate) cache information Blocks sent to initiator = 2540508505 Blocks received from initiator = 3437671110 Blocks read from cache and sent to initiator = 606203452 Number of read and write commands whose size <= segment size = 6325773 Number of read and write commands whose size > segment size = 0 Vendor (Seagate/Hitachi) factory information number of hours powered up = 6514.35 number of minutes until next internal SMART test = 43 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: 0 No self-tests have been logged smartctl --all /dev/sde - for a SAS drive that DOES show up in the plugin smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.7-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: HP Product: MB1000FAMYU Revision: HPD2 User Capacity: 1,000,204,886,016 bytes [1.00 TB] Logical block size: 512 bytes Rotation Rate: 7200 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000c50020e5c55b Serial number: 9WK0FR710000C038DKM1 Device type: disk Transport protocol: SAS Local Time is: Thu Sep 24 10:59:02 2015 MDT 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: 37 C Drive Trip Temperature: 65 C Manufactured in week 19 of year 2010 Specified cycle count over device lifetime: 10000 Accumulated start-stop cycles: 11 Specified load-unload count over device lifetime: 300000 Accumulated load-unload cycles: 11 Elements in grown defect list: 0 Vendor (Seagate) cache information Blocks sent to initiator = 263640184 Blocks received from initiator = 1514716588 Blocks read from cache and sent to initiator = 32749626 Number of read and write commands whose size <= segment size = 143666 Number of read and write commands whose size > segment size = 0 Vendor (Seagate/Hitachi) factory information number of hours powered up = 825.18 number of minutes until next internal SMART test = 42 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 5903552 0 134.984 0 write: 0 0 0 0 0 776.068 0 verify: 0 0 0 30575 0 0.000 0 Non-medium error count: 333 No self-tests have been logged

Please test new version and post screenshot of Layout and DATA tab if possible. First off, Big thanks for the plugin and especially for working to add a fix for this non-typical device type. It is very much appreciated. So... I now see one of the SAS devices on the "Data" page. Yaaaay!!! But, not the other 7 that are currently installed. Here is what I have done so far: 1 - updated Server Layout plugin (SAS drive sde shows up on data page) 2 - rebooted & clicked "update Smartmontools Database" (sde is still present but no other SAS drives) 2 - updated unRaid to 6.1.3 & reboot & clicked "update Smartmontools Database" (sde is still present but no other SAS drives) I should also note, and this is not related to this plugin, but I think it may be relevant. When my array is started and the disks show 'green' on the Main page, I never see drive temps. Also, when I select a disk from the main page it always says the SAS drives are "Unavailable - disk must be spun up". When I select spin-up the page refreshes but nothing changes. I think support of SAS drives in unRaid as a whole is minimal. - EDIT - I forgot to mention that even when drives show active all 'smart' option buttons are greyed out with the exception of the afore mentioned 'spin-up' and the 'download'.

I would love to see IPv6 support added. Don't get me wrong, I love NATing as much as the next guy, but I am really looking forward to allocating an IPv6 address to every cell in my body (and my wife's body, and my kids, and...).

Here is the lsscsi. @DeadPool:~# lsscsi [0:0:0:0] disk SanDisk Cruzer Fit 1.26 /dev/sda [1:0:0:0] disk HP DB1000BABFF HPD5 /dev/sdc [1:0:1:0] disk HP DB1000BABFF HPD8 /dev/sdd [1:0:2:0] disk HP MB1000FAMYU HPD2 /dev/sde [1:0:3:0] disk HP DB1000BABFF HPD5 /dev/sdf [1:0:4:0] disk HP DB1000BABFF HPD5 /dev/sdg [1:0:5:0] disk HP DB1000BABFF HPD5 /dev/sdh [1:0:6:0] disk HP DB1000BABFF HPD5 /dev/sdi [1:0:7:0] disk HP DB1000BABFF HPD5 /dev/sdj [2:0:0:0] disk ATA OCZ-VERTEX2 1.37 /dev/sdb And here is an ls -las /dev/disk/by-id as well just for good measure. DeadPool:~# ls -las /dev/disk/by-id total 0 0 drwxr-xr-x 2 root root 720 Aug 24 09:25 ./ 0 drwxr-xr-x 6 root root 120 Aug 24 09:25 ../ 0 lrwxrwxrwx 1 root root 9 Aug 24 09:25 ata-OCZ-VERTEX2_OCZ-7139ICMP6O4OG353 -> ../../sdb 0 lrwxrwxrwx 1 root root 9 Aug 24 09:25 scsi-35000c50010176e8f -> ../../sdg 0 lrwxrwxrwx 1 root root 10 Aug 24 09:25 scsi-35000c50010176e8f-part1 -> ../../sdg1 0 lrwxrwxrwx 1 root root 9 Aug 24 09:25 scsi-35000c5001019aadb -> ../../sdi 0 lrwxrwxrwx 1 root root 10 Aug 24 09:25 scsi-35000c5001019aadb-part1 -> ../../sdi1 0 lrwxrwxrwx 1 root root 9 Aug 24 09:25 scsi-35000c500101d1def -> ../../sdd 0 lrwxrwxrwx 1 root root 10 Aug 24 09:25 scsi-35000c500101d1def-part1 -> ../../sdd1 0 lrwxrwxrwx 1 root root 9 Aug 24 09:25 scsi-35000c50010202287 -> ../../sdc 0 lrwxrwxrwx 1 root root 10 Aug 24 09:25 scsi-35000c50010202287-part1 -> ../../sdc1 0 lrwxrwxrwx 1 root root 9 Aug 24 09:25 scsi-35000c5001020228f -> ../../sdh 0 lrwxrwxrwx 1 root root 9 Aug 24 09:25 scsi-35000c500102089a7 -> ../../sdf 0 lrwxrwxrwx 1 root root 10 Aug 24 09:25 scsi-35000c500102089a7-part1 -> ../../sdf1 0 lrwxrwxrwx 1 root root 9 Aug 24 09:25 scsi-35000c5001020c6ff -> ../../sdj 0 lrwxrwxrwx 1 root root 10 Aug 24 09:25 scsi-35000c5001020c6ff-part1 -> ../../sdj1 0 lrwxrwxrwx 1 root root 9 Aug 24 09:25 scsi-35000c50020e5c55b -> ../../sde 0 lrwxrwxrwx 1 root root 10 Aug 24 09:25 scsi-35000c50020e5c55b-part1 -> ../../sde1 0 lrwxrwxrwx 1 root root 9 Aug 24 10:44 usb-SanDisk_Cruzer_Fit_4C532000040713109330-0:0 -> ../../sda 0 lrwxrwxrwx 1 root root 10 Aug 24 09:25 usb-SanDisk_Cruzer_Fit_4C532000040713109330-0:0-part1 -> ../../sda1 <further lines omitted>

Hey Guys, I seem to have a similar problem to those early on that experienced drives not showing up. In my case I believe the issue relates to my use of SAS drives. The discovery string "ata-" works fine for my cache SSD, but I believe i need an additional "if else" statement to identify SCSI (i.e. "scsi-") Any chance adding that is a possibility? Thanks!

Nice clean build! I have been trying to decide between the ASUS C60M1-I and the ASUS E45M1-M PRO. Just not sure how the dual-1Ghz will fair with multiple Plex steams. Does the Cruzer Fit have a valid GUID? As in can it be registered for Plus/Pro licenses? It was my understanding that the Fit was just a MicroSD in a usb shell. If it does have a valid GUID I am off to spend some of my wife's money.