Leaderboard

I've just run a non-correcting parity check. There's actually been some discussion recently on whether checks should be correcting or not, but in the event you want to run a non-correcting one, it seems a bit strange that I should have to bog down my server for another ~20 hours to write (in this case) 6 corrections that unRAID is already aware of. There isn't much helpful info in the logs either, or at least there doesn't appear to be much user-facing data about where these errors were located. A nice thing to have would be a dialog box pop up if a user clicks on the last parity check display on the dashboard, showing at least something about the errors, and a button to write corrections to parity, rather than having to scan the entire system again.

Notice: You must be running unRAID version 6.9 or later to use these plugins The easiest way of installing plugins is thru Community Applications. This is an apps installation manager developed by Squid and needs to be installed separately. The alternative way of installing an optional plugin is from the Plugin page in the WebGui and use the tab Install Pugin. The URLs of the optional plugins as mentioned below can be copied and pasted in the install box. Available Dynamix plugins Active Streams shows in real-time any open SMB and AFP network streams. This allows instant view of who is accessing the server - either by IP address or name - and see what content is opened. Optionally streams can be stopped from the GUI. Cache Dirs keeps folder information in memory to prevent unnecessary disk spin up. Dynamix builds a GUI front-end to allow entering of parameters for the cache_dirs script which is running in the background. S3 Sleep defines the conditions under which the system will go to S3 sleep mode. It also adds an unconditional 'sleep' button on the Array Operation page. System Info shows various details of your system hardware and BIOS. This includes processor, memory and sub-system components. System Stats shows in real-time the disk utilizations and critical system recources, such CPU usage, memory usage, interface bandwidth and disk I/O bandwidth. System Temp shows in real-time the temperature of the system CPU and motherboard. Temperatures can be displayed in Celsius or Fahrenheit. Your hardware must support the necessary probes, and additional software drivers may be required too. This plugin requires PERL, this package needs to be installed on Unraid versions lower than 6.11 System AutoFan allows automatic fan control based on the system temperature. High and low thresholds are used to speed up or speed down the fan. This is a new plugin and still under development. Schedules is a front-end utility for the built-in hourly, daily, weekly and monthly schedules. It allows the user to alter the schedule execution times using the GUI. See Settings -> Scheduler -> Fixed Schedules. System Buttons adds an one-click button to the header which allows for instant sleep, reboot, shutdown of the system or array start/stop. Local Master supports detection of the local master browser in an SMB network. It will display an icon in the header at the top-right when unRAID is elected as local master browser. Under SMB Workgroup settings more information about the current elected local master browser is given. SSD TRIM allows the creation of a cronjob to do regular SSD TRIM operations on the cache device(s). The command 'fstrim -v /mnt/cache' is executed at the given interval. This plugin is now built-in with Unraid version 6.11.0 and higher File Integrity Real-time hashing and verification of files stored on the data disks of the array. This plugin reports on failed file content integrity and detects silent file corruption (aka bit-rot). WARNING: USING THIS PLUGIN ON DISKS FORMATTED IN REISERFS MAY LEAD TO SYSTEM INSTABILITY. IT IS RECOMMENDED TO USE XFS. SCSI Devices updates the udev persistent storage devices rules file (courtesy of bubbaQ), which allows proper naming of SCSI attached disks. Please by aware that after installation of this plugin, it might be necessary to re-assign disks due to their changed names! Date Time adds an interactive world map to the date and time settings. This allows the user to simply click on his/her country and select the corresponding time zone. In addition the world map highlights the countries in the currently selected time zone. Stop Shell adds a script which gets invoked when the array is stopped. This script looks for any open shells in /mnt/... and terminate them. This ensures the array can be stopped. Be aware that automatic terminating of open shells may lead to data loss if an active process is writing to the array. Day Night automatically toggles between a day theme and a night theme. Based on the sunrise and sunset times of your location. Share Floor creates a cronjob to do a regular scan on user shares and change the minimum share floor value according to the largest file found in the share. Factory Reset resets the system to default settings and let it start like a new installation. Optionally array and pool assignments can be preserved. In either case USER DATA IS NEVER LOST Installation URLs (copy & paste) Active Streams - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.active.streams.plg Cache Dirs - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.cache.dirs.plg S3 Sleep - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.s3.sleep.plg System Info - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.info.plg System Stats - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg System Temp - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.temp.plg System AutoFan - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.autofan.plg Schedules - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.schedules.plg System Buttons - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.buttons.plg Local Master - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.local.master.plg SSD TRIM - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.ssd.trim.plg File Integrity - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.file.integrity.plg SCSI Devices - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.scsi.devices.plg Date Time - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.date.time.plg Stop Shell - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.stop.shell.plg Day Night - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.day.night.plg Share Floor - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.share.floor.plg Factory Reset - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.factory.reset.plg gridrunner aka Spaceinvader One has made a very nice video tutorial about several Dynamix plugins. A recommended watch when you like to learn more. You like my Dynamix plugins?

Pull your flash drive. Stick in another computer. Go to the config folder. Delete the passwd , smbpasswd , shadow files. Eject the flash drive. Put the flash drive back in the server and start it back up. This procedure should leave all passwords blank. You can now reassign new ones.

That feature is in unRAID and I can't implement it for UD. I would recommend you post a feature request for that to be added by LT.

I have made a guide for how to setup ISCSI targets on unRAID.

One thing to note is that the user filesystem (/mnt/user/Share) does not support the operations but the raw disk shares do (/mnt/disk#/Share)

@Bjonness406 Has anyone tried using chattr? chattr +i "Try to edit.txt" To remove it you need to do: chattr -i "Try to edit.txt" To view attributes: lsattr "Try to edit.txt" https://en.wikipedia.org/wiki/Chattr

unRAID OS does not support RAID cards operating in anything but pass-through (or JBOD) mode. I realize it would be "nice" for you to run a bunch of drives behind a RAID-5 controller and have unRAID manage it all. However, there a numerous RAID cards out there. Most with proprietary drivers and management interfaces. There might be a tweak here or there we can do to quiet down messages, but don't expect "full support" for these cards. For example, 'spin up', 'spin down' creating message: our workaround: don't use spin-up/spin-down with devices attached to these cards.

There are many nice things with btrfs, but the free-space administration seems developed by the bastard developer from hell. It's almost impossible to move to btrfs without having to learn the hard way.

Use the unbalance plugin to scatter the data from the dying drive. It makes it pretty simple to do this with just a few clicks and a nice GUI interface to make it obvious what you're doing at each step of the way

Because executing bash within a container by default means that its interactive, and the system is effectively waiting for you to enter in the commands Try this docker exec -t apache Step 0 docker exec -t apache Step 1 docker exec -t apache Step 2

Your Areca controller configuration is incorrect. This is from the smartctl man page: ------ areca,N - [FreeBSD, Linux, Windows and Cygwin only] the device consists of one or more SATA disks connected to an Areca SATA RAID controller. The positive integer N (in the range from 1 to 24 inclusive) denotes which disk on the controller is monitored. On Linux use syntax such as: smartctl -a -d areca,2 /dev/sg2 smartctl -a -d areca,3 /dev/sg3 On FreeBSD use syntax such as: smartctl -a -d areca,2 /dev/arcmsr1 smartctl -a -d areca,3 /dev/arcmsr2 On Windows and Cygwin use syntax such as: smartctl -a -d areca,2 /dev/arcmsr0 smartctl -a -d areca,3 /dev/arcmsr1 The first line above addresses the second disk on the first Areca RAID controller. The second line addresses the third disk on the second Areca RAID controller. To help identify the correct device on Linux, use the command: cat /proc/scsi/sg/device_hdr /proc/scsi/sg/devices to show the SCSI generic devices (one per line, starting with /dev/sg0). The correct SCSI generic devices to address for smartmontools are the ones with the type field equal to 3. If the incorrect device is addressed, please read the warning/error messages carefully. They should provide hints about what devices to use. Important: the Areca controller must have firmware version 1.46 or later. Lower-numbered firmware versions will give (harmless) SCSI error messages and no SMART information. ------- Also install the Dynamix SCSI devices plugin for a proper update of the udev storage rules needed for SCSI controllers, such as Areca. This topic is a bit outdated, but may help (skip steps 1-3)

That's why I said you need to start small, I though that since it reallocated one chunk with 5 you could go straight to a much higher number, try d-usage=10, then 20 and you should be able to go to 80, if it still fails, try smaller increasing values until it works or you'll need to clear more space, when it's done schedule a weekly balance so it doens't happen again.

Is there a difference with browser opened or closed? I have seen this kind of messages when the hdparm program is executed. Any of your plugins using that? (or perhaps start in safemode)

Please type this command and note if it causes those messages to be immediately logged: smartctl -A /dev/sdc

RC12a uploaded earlier, RC13 compiling....

Hi - Yes, you should be able to add the disks and USB stick to a new system and boot it up. To support 2 Plex streams and a VM I'd suggest a relatively recent Core i7 or Xeon E3 with at least 8000 Passmarks, although the newest 6 core Coffee Lake Core i5 would work as well. 16GB of RAM. It's hard to suggest a full configuration, though. All pricing and availability is local so I'd look to see what motherboards and cases are available where you are and post back.

Without thinking too much: #!/bin/bash hdparm -C /dev/sdb >> /mnt/user/sharename/status.txt #change path to suit smartctl -a /dev/sdb | grep Temperature >> /mnt/user/sharename/status.txt #repeat for more disks sensors | grep Fan >> /mnt/user/sharename/status.txt And running at whatever schedule you choose.

I was testing today my OpenVPN access and found out I wasn't able to connect. Banged my head against my car's window for a while, but that didn't solve anything. When I got back home, I looked at my vyos logs and found out it was a matter of my client's certificate being expired Nov 17 09:49:46 xxxxxxx openvpn-vtun0[3205]: 1xx.1xx.xxx.xxx:47946 VERIFY ERROR: depth=0, error=certificate has expired: /C=xx/ST=xxxxxx/O=xxxxxx/OU=xxxxxxxxx/CN=client1 I'm setting my next certificates to have 5yrs expiration (previous had 1yr). So, this post is just a heads up !

I have some of these, the 5 disk model, they are hard to find though, I bought some on ebay for $50. http://www.xtore.com/downloads/datasheet/XJ100_PUB-00040-D_Final.pdf

IMO the only reliable external enclosure is one with a SAS connection, eSata with port multiplier and USB should be avoided as array devices, doesn't mean it can't work, but most often than not it will be a headache. You can try again after disabling VT-d, it may work better, but would really recommend a setup change if possible.

You should have kept the LSI, you're using two not recommend things, a Marvell controller and a port multiplier, disk 1 is disable but if you look at the main page all your disks have errors, you'll need to change your setup, it will never be reliable as is.

Works perfectly for me too so far, many thanks.

The general idea of a CSRF token is to have an unguessable string that is generated by the server and submitted as part of any sensitive action. It is essentially an automated second password, required in addition to the standard authentication, before action can be taken. Unguessable is key, otherwise it adds no value. The main strategy to make it hard to guess/steal is to make it unique and short-lived. If the token expires with the session, then any work the bad guys put in to determine the token is lost when the session closes. That makes it a very tough target for an attack. In our case, a single token is shared across all browsers, all sessions, all users (well, there is really only one "user"), all plugins, and all apps (such as ControlR), until a reboot. So clearly at this point we are not relying on uniqueness or a short lifetime to help keep the token secure. But where a short lifetime would discourage hackers from looking for the token, our multiple-month lifetime would probably do the opposite. Admittedly, I'm having a hard time coming up with a concrete example of how they might take advantage of this, beyond the log files idea. But that doesn't mean there isn't a way! Based on my (limited) understanding of how unRAID works, it seems like it would be difficult to move to a true session-based system that would allow unique tokens. That's why I was suggesting to come up with a way to change the global token on a regular basis. To minimize disruption, the system could accept the previous token and transparently send the current one back to the client. Overall to me it just "feels" wrong to have a global CSRF token that doesn't expire until the server is rebooted. I realize security is done in layers, but this layer feels weak.

# /usr/local/emhttp/webGui/scripts/notify notify [-e "event"] [-s "subject"] [-d "description"] [-i "normal|warning|alert"] [-m "message"] [-x] [-t] [add] create a notification use -e to specify the event use -s to specify a subject use -d to specify a short description use -i to specify the severity use -m to specify a message (long description) use -x to create a single notification ticket use -t to force send email only (for testing) all options are optional notify init Initialize the notification subsystem. notify smtp-init Initialize sendmail configuration (ssmtp in our case). notify get Output a json-encoded list of all the unread notifications. notify archive file Move file from 'unread' state to 'archive' state.

Drive failure on ARC-1200 I have been using my ARC-1200 with two Hitachi 3T drives (total of 6T in a RAID0 configuration) as parity. It has been a great setup. The Hitachi drives have outstanding long-term reliability characteristics, and this setup has served me well for more than 5 years. This weekend I was doing a bit of housecleaning and copying some data to my array. Suddenly the array became largely unresponsive, and several minutes later I determined that the parity drive had been kicked from the array. Upon further investigation, I discovered that the drive was offline from the controller and was invisible to the OS. Here is what was in the syslog: (previous log message was several hours old) Jan 1 13:59:13 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0 Jan 1 13:59:14 Shark kernel: arcmsr1: scsi id = 0 lun = 0 ccb = '0xffff88041acb1280' poll command abort successfully Jan 1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0 Jan 1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0 Jan 1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0 Jan 1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0 Jan 1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0 Jan 1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0 Jan 1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0 Jan 1 13:59:39 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0 Jan 1 13:59:39 Shark kernel: arcmsr1: scsi id = 0 lun = 0 ccb = '0xffff88041ac8e380' poll command abort successfully Jan 1 13:59:39 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0 Jan 1 13:59:39 Shark kernel: arcmsr: executing bus reset eh.....num_resets = 0, num_aborts = 10 Jan 1 13:59:39 Shark kernel: sd 1:0:0:0: Device offlined - not ready after error recovery ... repeated lines removed ... Jan 1 13:59:39 Shark kernel: sd 1:0:0:0: Device offlined - not ready after error recovery Jan 1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 Jan 1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] CDB: opcode=0x8a 8a 00 00 00 00 01 ad 7d db c8 00 00 04 00 00 00 Jan 1 13:59:39 Shark kernel: blk_update_request: I/O error, dev sdb, sector 7205673928 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673864 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673872 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673880 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673888 Jan 1 13:59:39 Shark kernel: md: recovery thread woken up ... Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673896 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673904 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673912 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673920 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673928 Jan 1 13:59:39 Shark kernel: sd 1:0:0:0: rejecting I/O to offline device Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673936 Jan 1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] killing request Jan 1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673944 Jan 1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] CDB: opcode=0x8a 8a 00 00 00 00 01 45 e9 ec d0 00 00 00 20 00 00 Jan 1 13:59:39 Shark kernel: blk_update_request: I/O error, dev sdb, sector 5467925712 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673952 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673960 Jan 1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 Jan 1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] CDB: opcode=0x8a 8a 00 00 00 00 01 ad 7d aa 68 00 00 01 08 00 00 Jan 1 13:59:39 Shark kernel: blk_update_request: I/O error, dev sdb, sector 7205661288 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673968 Jan 1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673976 ... repeated write errors ... I was able to stop the array and powerdown/reboot. Upon rebooting I expected to find the ARC-1200 to have some information about the incident, but found nothing hunting through its BIOS. I ran smartctl checks on both of the drives in Areca RAIDset, and learned that both were exhibiting some concerning issues. Member Disk1 smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Hitachi Deskstar 7K3000 Device Model: Hitachi HDS723030ALA640 Serial Number: MK0311YHG5xxxx LU WWN Device Id: 5 000cca 225c26876 Firmware Version: MKAOA3B0 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 2.6, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Mon Jan 2 21:13:06 2017 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 093 093 016 Pre-fail Always - 34 2 Throughput_Performance 0x0005 136 136 054 Pre-fail Offline - 83 3 Spin_Up_Time 0x0007 126 126 024 Pre-fail Always - 613 (Average 615) 4 Start_Stop_Count 0x0012 099 099 000 Old_age Always - 4745 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 56 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 133 133 020 Pre-fail Offline - 27 9 Power_On_Hours 0x0012 094 094 000 Old_age Always - 47675 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 188 192 Power-Off_Retract_Count 0x0032 096 096 000 Old_age Always - 5220 193 Load_Cycle_Count 0x0012 096 096 000 Old_age Always - 5220 194 Temperature_Celsius 0x0002 206 206 000 Old_age Always - 29 (Min/Max 8/38) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 61 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. Member Disk2 smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Hitachi Deskstar 7K3000 Device Model: Hitachi HDS723030ALA640 Serial Number: MK0311YHG4xxxx LU WWN Device Id: 5 000cca 225c1f2ca Firmware Version: MKAOA3B0 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 2.6, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Mon Jan 2 21:13:22 2017 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 132 132 054 Pre-fail Offline - 94 3 Spin_Up_Time 0x0007 125 125 024 Pre-fail Always - 616 (Average 615) 4 Start_Stop_Count 0x0012 099 099 000 Old_age Always - 4746 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 1 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 133 133 020 Pre-fail Offline - 27 9 Power_On_Hours 0x0012 094 094 000 Old_age Always - 47652 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 191 192 Power-Off_Retract_Count 0x0032 096 096 000 Old_age Always - 5209 193 Load_Cycle_Count 0x0012 096 096 000 Old_age Always - 5209 194 Temperature_Celsius 0x0002 222 222 000 Old_age Always - 27 (Min/Max 8/36) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 1 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 10 (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 10 occurred at disk power-on lifetime: 47487 hours (1978 days + 15 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 80 08 fc 9d 07 Error: UNC at LBA = 0x079dfc08 = 127794184 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 20 08 35 9f 40 08 04:05:26.311 READ FPDMA QUEUED 60 00 18 08 34 9f 40 08 04:05:26.302 READ FPDMA QUEUED 60 00 d8 08 33 9f 40 08 04:05:26.293 READ FPDMA QUEUED 60 00 c8 08 32 9f 40 08 04:05:26.284 READ FPDMA QUEUED 60 00 f0 08 31 9f 40 08 04:05:26.274 READ FPDMA QUEUED Error 9 occurred at disk power-on lifetime: 47487 hours (1978 days + 15 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 08 fc 9d 07 Error: WP at LBA = 0x079dfc08 = 127794184 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 f0 08 6e 9d 40 08 04:05:20.750 WRITE FPDMA QUEUED 61 00 e8 08 6d 9d 40 08 04:05:20.745 WRITE FPDMA QUEUED 61 00 e0 08 6c 9d 40 08 04:05:20.745 WRITE FPDMA QUEUED 61 00 d8 08 6b 9d 40 08 04:05:20.745 WRITE FPDMA QUEUED 61 00 d0 08 6a 9d 40 08 04:05:20.741 WRITE FPDMA QUEUED Error 8 occurred at disk power-on lifetime: 47483 hours (1978 days + 11 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 08 89 b4 07 Error: UNC at LBA = 0x07b48908 = 129272072 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 f0 08 a4 b4 40 08 00:25:45.071 READ FPDMA QUEUED 60 00 e8 08 a3 b4 40 08 00:25:45.071 READ FPDMA QUEUED 60 00 e0 08 a2 b4 40 08 00:25:45.046 READ FPDMA QUEUED 60 00 d8 08 a1 b4 40 08 00:25:45.046 READ FPDMA QUEUED 60 00 d0 08 a0 b4 40 08 00:25:45.046 READ FPDMA QUEUED Error 7 occurred at disk power-on lifetime: 44041 hours (1835 days + 1 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 08 d8 45 06 Error: UNC at LBA = 0x0645d808 = 105240584 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 78 08 dd 45 40 08 1d+16:31:50.071 READ FPDMA QUEUED 60 00 70 08 dc 45 40 08 1d+16:31:50.071 READ FPDMA QUEUED 60 00 68 08 db 45 40 08 1d+16:31:50.071 READ FPDMA QUEUED 60 00 60 08 da 45 40 08 1d+16:31:50.071 READ FPDMA QUEUED 60 00 58 08 d9 45 40 08 1d+16:31:50.071 READ FPDMA QUEUED Error 6 occurred at disk power-on lifetime: 44041 hours (1835 days + 1 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 ff 09 2a 22 0e Error: UNC at LBA = 0x0e222a09 = 237120009 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 78 08 2d 22 40 08 1d+15:59:13.488 READ FPDMA QUEUED 60 00 70 08 2c 22 40 08 1d+15:59:13.488 READ FPDMA QUEUED 60 00 68 08 2b 22 40 08 1d+15:59:13.488 READ FPDMA QUEUED 60 00 60 08 2a 22 40 08 1d+15:59:13.488 READ FPDMA QUEUED 60 00 58 08 29 22 40 08 1d+15:59:13.488 READ FPDMA QUEUED SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. If you look closely, Member Disk1 you'll see that there are 56 reallocated sectors. Not a good thing but not a disaster. This was checked not more than a month ago, so all of these are new. But Member Disk2 has other problems. There is a single reallocated sector, and another pending sector. But there are several items in the SMART log, the first 2 are very very recent (look at power on hours). The drives have been powered on for over 5 years (physical age probably closer to 6). I am no longer going to keep these in my array - maybe will look to move them into backup service. But the interesting thing, and reason I am posting here, is how the Areca controller reacted. I would have expected that it would have detected the drive issues and logged something. Suppose I had had a parity1 RAID, I would have expected it would have noticed "bad things happening" and dropped one of the drives, leaving the single drive and asking for a replacement for the bad one. I was disappointed, leaving me feeling just a bit shaky as to whether the controller did what it was supposed to in this situation. I happened to have a precleared 6T drive available, and popped it in as parity. The build is nearing completion and it is working fine. It is going considerably faster than with the RAID0 parity pair. For now, the ARC-1200 and its two drives are still installed and idle. I decided to post this as this type of information is hard to come by, and thought someone might find it useful. Even after owning my ARC-1200 for 6 years, this is the first opportunity to witness how it behaves when drives start to fail. Cheers!

You can do that with the "docker buttons" plugin

Agreed especially when it's so easily implemented with a plugin. Also I think sometimes we forget the merit of having plugins that not only we can add, but also remove, being able to easily strip the os down to bare bones makes troubleshooting much easier for one. Also not everyone wants or needs the functionality of a particular plugin on their Unraid box (I for the record am a sucker for these things though) Sent from my LG-H815 using Tapatalk

There is a licensing issue with simply merging this plugin due to the way statistics are displayed. This will not be a simple merge so while I love this plugin, it will have to wait a bit before we can consider formal inclusion.

http://www.linuxatemyram.com Sent from my LG-D852 using Tapatalk