Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

flaggart

Members
  • Joined

  • Last visited

Everything posted by flaggart

  1. Hi, Since unraid v 6.6.1 I have been having issues with auto updating of the system and plugins. This was because wget was unable to verify certificates, due to conflicting versions of openssl. I think this is because your plugin installs libssl1-1.1.0g. Unraid syslog shows "OpenSSL version mismatch. Built against 1010100f, you have 1010007f#015" Uninstalling the plugin resolved the issue. I have started using a tvheadend docker container, but if you still have the will/interest to maintain this, I would prefer the plugin. Thanks.
  2. There is a similar deal in the UK for a card with the same chipset. Reduced from £217 to £100 (confirmed by Camelizer which says the previous low was £180 in October). May be of use to some of you - I have just ordered. https://www.amazon.co.uk/gp/product/B0085FT2JC/ref=od_aui_detailpages00?ie=UTF8&psc=1
  3. Same issue here. I had to roll back to 4.2.3 - I had not updated for a while. Thanks for your efforts, much appreciated.
  4. I have an issue with tvheadend randomly stopping. Here is what seems to be the relevant log entry: Sep 15 04:32:49 TOWER kernel: Out of memory: Kill process 31524 (tvheadend) score 776 or sacrifice child Sep 15 04:32:49 TOWER kernel: Killed process 31524 (tvheadend) total-vm:14558828kB, anon-rss:13054820kB, file-rss:5664kB Sep 15 04:32:49 TOWER kernel: mc invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0 Sep 15 04:32:49 TOWER kernel: mc cpuset=/ mems_allowed=0 Sep 15 04:32:49 TOWER kernel: CPU: 5 PID: 6006 Comm: mc Tainted: P W O 4.1.15-unRAID #1 Sep 15 04:32:49 TOWER kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B75M-ITX, BIOS P1.90 07/17/2013 Sep 15 04:32:49 TOWER kernel: 0000000000000000 ffff880110bb79e8 ffffffff815f8950 0000000000007c48 Sep 15 04:32:49 TOWER kernel: ffff8803d9508000 ffff880110bb7a98 ffffffff815f4ecc ffff880110bb7a48 Sep 15 04:32:49 TOWER kernel: ffffffff810f6ce9 ffff880014007000 01ff880110bb7a08 ffff880110bb7a48 Sep 15 04:32:49 TOWER kernel: Call Trace: Sep 15 04:32:49 TOWER kernel: [<ffffffff815f8950>] dump_stack+0x4c/0x6e Sep 15 04:32:49 TOWER kernel: [<ffffffff815f4ecc>] dump_header+0x7a/0x20b Sep 15 04:32:49 TOWER kernel: [<ffffffff810f6ce9>] ? mem_cgroup_iter+0x2fd/0x3fb Sep 15 04:32:49 TOWER kernel: [<ffffffff810fac63>] ? vmpressure+0x1c/0x6f Sep 15 04:32:49 TOWER kernel: [<ffffffff81355273>] ? ___ratelimit+0xcf/0xe0 Sep 15 04:32:49 TOWER kernel: [<ffffffff810b3c52>] oom_kill_process+0xb7/0x37b Sep 15 04:32:49 TOWER kernel: [<ffffffff810b3957>] ? oom_badness+0xb6/0x100 Sep 15 04:32:49 TOWER kernel: [<ffffffff810b43a7>] __out_of_memory+0x441/0x463 Sep 15 04:32:49 TOWER kernel: [<ffffffff810b4508>] out_of_memory+0x4f/0x66 Sep 15 04:32:49 TOWER kernel: [<ffffffff810b850c>] __alloc_pages_nodemask+0x722/0x7b6 Sep 15 04:32:49 TOWER kernel: [<ffffffff810e4a14>] alloc_pages_current+0xb4/0xd5 Sep 15 04:32:49 TOWER kernel: [<ffffffff810b1a5e>] __page_cache_alloc+0x88/0x95 Sep 15 04:32:49 TOWER kernel: [<ffffffff810b25d5>] generic_file_read_iter+0x32e/0x551 Sep 15 04:32:49 TOWER kernel: [<ffffffff810fd847>] __vfs_read+0x89/0xad Sep 15 04:32:49 TOWER kernel: [<ffffffff810fdd33>] vfs_read+0x84/0x11d Sep 15 04:32:49 TOWER kernel: [<ffffffff810fe543>] SyS_read+0x42/0x86 Sep 15 04:32:49 TOWER kernel: [<ffffffff815fe06e>] system_call_fastpath+0x12/0x71 Sep 15 04:32:49 TOWER kernel: Mem-Info: Sep 15 04:32:49 TOWER kernel: active_anon:3730744 inactive_anon:108262 isolated_anon:0 Sep 15 04:32:49 TOWER kernel: active_file:9983 inactive_file:10619 isolated_file:290 Sep 15 04:32:49 TOWER kernel: unevictable:0 dirty:4528 writeback:831 unstable:0 Sep 15 04:32:49 TOWER kernel: slab_reclaimable:96842 slab_unreclaimable:29449 Sep 15 04:32:49 TOWER kernel: mapped:26683 shmem:205360 pagetables:12848 bounce:0 Sep 15 04:32:49 TOWER kernel: free:20239 free_pcp:0 free_cma:0 Sep 15 04:32:49 TOWER kernel: Node 0 DMA free:15104kB min:12kB low:12kB high:16kB active_anon:64kB inactive_anon:176kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15984kB managed:15360kB mlocked:0kB dirty:0kB writeback:0kB mapped:64kB shmem:240kB slab_reclaimable:16kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes Sep 15 04:32:49 TOWER kernel: lowmem_reserve[]: 0 3423 15939 15939 Sep 15 04:32:49 TOWER kernel: Node 0 DMA32 free:53496kB min:3444kB low:4304kB high:5164kB active_anon:3051428kB inactive_anon:102404kB active_file:10344kB inactive_file:11520kB unevictable:0kB isolated(anon):0kB isolated(file):200kB present:3581300kB managed:3506316kB mlocked:0kB dirty:5788kB writeback:680kB mapped:22072kB shmem:182956kB slab_reclaimable:175688kB slab_unreclaimable:28640kB kernel_stack:4208kB pagetables:11936kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:144228 all_unreclaimable? yes Sep 15 04:32:49 TOWER kernel: lowmem_reserve[]: 0 0 12516 12516 Sep 15 04:32:49 TOWER kernel: Node 0 Normal free:12356kB min:12600kB low:15748kB high:18900kB active_anon:11871484kB inactive_anon:330468kB active_file:29696kB inactive_file:30816kB unevictable:0kB isolated(anon):0kB isolated(file):832kB present:13080576kB managed:12816552kB mlocked:0kB dirty:12324kB writeback:2644kB mapped:84596kB shmem:638244kB slab_reclaimable:211664kB slab_unreclaimable:89156kB kernel_stack:8048kB pagetables:39456kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:433692 all_unreclaimable? yes Sep 15 04:32:49 TOWER kernel: lowmem_reserve[]: 0 0 0 0 Sep 15 04:32:49 TOWER kernel: Node 0 DMA: 0*4kB 0*8kB 2*16kB (EM) 1*32kB (E) 1*64kB (E) 1*128kB (E) 2*256kB (EM) 2*512kB (EM) 3*1024kB (UEM) 3*2048kB (UEM) 1*4096kB (R) = 15104kB Sep 15 04:32:49 TOWER kernel: Node 0 DMA32: 2868*4kB (UER) 3174*8kB (UEMR) 1000*16kB (UEMR) 5*32kB (R) 2*64kB (R) 3*128kB (R) 1*256kB (R) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 53792kB Sep 15 04:32:49 TOWER kernel: Node 0 Normal: 2815*4kB (UEM) 58*8kB (EM) 32*16kB (R) 8*32kB (R) 2*64kB (R) 3*128kB (R) 2*256kB (R) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 13516kB Sep 15 04:32:49 TOWER kernel: 226405 total pagecache pages Sep 15 04:32:49 TOWER kernel: 0 pages in swap cache Sep 15 04:32:49 TOWER kernel: Swap cache stats: add 0, delete 0, find 0/0 Sep 15 04:32:49 TOWER kernel: Free swap = 0kB Sep 15 04:32:49 TOWER kernel: Total swap = 0kB Sep 15 04:32:49 TOWER kernel: 4169465 pages RAM Sep 15 04:32:49 TOWER kernel: 0 pages HighMem/MovableOnly Sep 15 04:32:49 TOWER kernel: 84908 pages reserved Sep 15 04:32:49 TOWER kernel: [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name Sep 15 04:32:49 TOWER kernel: [ 1045] 0 1045 5395 598 15 3 0 -1000 udevd Sep 15 04:32:49 TOWER kernel: [ 1299] 0 1299 58398 850 25 3 0 0 rsyslogd Sep 15 04:32:49 TOWER kernel: [ 1572] 0 1572 1671 452 8 3 0 0 dhcpcd Sep 15 04:32:49 TOWER kernel: [ 1582] 1 1582 1714 369 9 3 0 0 rpc.portmap Sep 15 04:32:49 TOWER kernel: [ 1586] 32 1586 3209 448 11 3 0 0 rpc.statd Sep 15 04:32:49 TOWER kernel: [ 1596] 0 1596 1615 435 8 3 0 0 inetd <snip> Sep 15 04:32:49 TOWER kernel: [31386] 0 31386 11038 165 25 4 0 0 ssh Sep 15 04:32:49 TOWER kernel: [31395] 0 31395 11038 166 25 3 0 0 ssh Sep 15 04:32:49 TOWER kernel: [32019] 999 32019 243894 25320 123 4 0 0 Plex Script Hos Sep 15 04:32:49 TOWER kernel: [ 3295] 999 3295 297309 20457 123 4 0 0 Plex Script Hos Sep 15 04:32:49 TOWER kernel: [ 3410] 999 3410 242943 20734 117 4 0 0 Plex Script Hos Sep 15 04:32:49 TOWER kernel: [ 4908] 999 4908 261243 19817 117 4 0 0 Plex Script Hos Sep 15 04:32:49 TOWER kernel: [32178] 999 32178 397437 18226 126 4 0 0 Plex Script Hos Sep 15 04:32:49 TOWER kernel: [32181] 999 32181 315003 16144 115 4 0 0 Plex Script Hos Sep 15 04:32:49 TOWER kernel: [ 8082] 0 8082 1091 189 7 3 0 0 sleep Sep 15 04:32:49 TOWER kernel: [ 8129] 0 8129 2159 216 9 3 0 0 timeout Sep 15 04:32:49 TOWER kernel: [ 8130] 0 8130 2974 260 10 3 0 0 find Sep 15 04:32:49 TOWER kernel: [ 8149] 0 8149 1091 158 7 3 0 0 sleep Sep 15 04:32:49 TOWER kernel: Out of memory: Kill process 31526 (linuxdvb_fronte) score 776 or sacrifice child Sep 15 04:32:49 TOWER kernel: Killed process 31572 (mpegts_input_th) total-vm:14558828kB, anon-rss:13055084kB, file-rss:6388kB There is 16gb RAM in the server so with no VMs running so I wouldn't have expected to be out of memory...
  5. Thanks! Fixed it.
  6. Might be worth trying the tips on this page: http://blog.yohanliyanage.com/2015/05/docker-clean-up-after-yourself/ In particular, deleting "dangling" images and unwanted volumes left behind after deleting containers: docker rmi $(docker images -f "dangling=true" -q) docker run -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/docker:/var/lib/docker --rm martin/docker-cleanup-volumes
  7. When I stop this plugin from the webinterface, it spams a constant stream of "y y y y y y y y y y y y y y y y y....." which continues until I close the tab and re-open it, at which point tvheadend has stopped. The same thing happens when I stop the array and I have to SSH in and "killall yes" then wait a few mins for it to recover. Really annoying!
  8. Hi, Does this version support transcoding? I have installed it - but no options for this under Configuration / General
  9. The webserver has stopped working properly. It loads, and for a brief moment I see the user/password boxes, but then they vanish and all I see at the top is the word "Quassel" with a blue background..
  10. This works great, however.. I use /setkey in quassel client to set the blowfish key for an encrypted channel.. which works fine to start with. But after the container is restarted, all of the keys that were set are gone and have to be set again. /showkey #channel returns "No key has been set".
  11. Unfortunately the NewerTech G5 3-drive bay is a few mm too tall which means it will not fit in the main chamber beneath the controller card. So realistically all I can do is fit two more drives in the drive chamber using another OWC multimount - that would mean 13 data + parity + cache. Still not too shabby for such a tiny box!
  12. root@BIGBOX:~# smartctl -a -A /dev/sdh smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green Device Model: WDC WD20EADS-00R6B0 Serial Number: WD-WCAVY1187400 LU WWN Device Id: 5 0014ee 2ae3ff9f8 Firmware Version: 01.00A01 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Sun Mar 15 12:51:26 2015 GMT 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 General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (41580) 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: ( 473) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303f) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 149 147 021 Pre-fail Always - 9508 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1637 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 077 077 000 Old_age Always - 16822 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 481 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 75 193 Load_Cycle_Count 0x0032 194 194 000 Old_age Always - 18501 194 Temperature_Celsius 0x0022 121 102 000 Old_age Always - 31 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 16812 - # 2 Short offline Completed without error 00% 16800 - # 3 Short captive Completed without error 00% 24 - 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.
  13. I ran an extended SMART test from unRAID gui on drive 10. Not sure if there is a log for that, but the GUI reports no errors: Num Test Description Status Remaining LifeTime(hours) LBA of first error 1 Extended offline Completed without error 00% 16812 None 2 Short offline Completed without error 00% 16800 None 3 Short captive Completed without error 00% 24 None
  14. The console log is verbatim. With regards to having removed the drive, connected to another PC etc, I think this step was totally unnecessary. I was unaware of the procedure to re-enable a disabled device. The drive red-balled at the exact same moment as I ran HDSentinal so it would be an amazing coincidence if a cable became loose! Data has finished rebuilding and all seems OK. Here is the syslog in case anyone is interested: Mar 13 21:34:00 BIGBOX in.telnetd[24059]: connect from 192.168.0.10 (192.168.0.10) Mar 13 21:34:03 BIGBOX login[24060]: ROOT LOGIN on '/dev/pts/0' from 'FRACTAL.home.net' Mar 13 21:34:53 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sde drive state is: active/idle Mar 13 21:35:54 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sde drive state is: active/idle Mar 13 21:36:58 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle Mar 13 21:37:17 BIGBOX kernel: sd 2:0:1:0: command f7250600 timed out Mar 13 21:37:17 BIGBOX kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Mar 13 21:37:17 BIGBOX kernel: sas: trying to find task 0xe2b1d900 Mar 13 21:37:17 BIGBOX kernel: sas: sas_scsi_find_task: aborting task 0xe2b1d900 Mar 13 21:37:17 BIGBOX kernel: sas: sas_scsi_find_task: task 0xe2b1d900 is aborted Mar 13 21:37:17 BIGBOX kernel: sas: sas_eh_handle_sas_errors: task 0xe2b1d900 is aborted Mar 13 21:37:17 BIGBOX kernel: sas: ata8: end_device-2:1: cmd error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata7: end_device-2:0: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata8: end_device-2:1: dev error handler Mar 13 21:37:17 BIGBOX kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 13 21:37:17 BIGBOX kernel: ata8.00: failed command: SMART Mar 13 21:37:17 BIGBOX kernel: ata8.00: cmd b0/d8:00:01:4f:c2/00:00:00:00:00/00 tag 0 Mar 13 21:37:17 BIGBOX kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 13 21:37:17 BIGBOX kernel: ata8.00: status: { DRDY } Mar 13 21:37:17 BIGBOX kernel: ata8: hard resetting link Mar 13 21:37:17 BIGBOX kernel: sas: ata9: end_device-2:2: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata10: end_device-2:3: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata11: end_device-2:4: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata12: end_device-2:5: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata13: end_device-2:6: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata14: end_device-2:7: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! Mar 13 21:37:19 BIGBOX kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[1]:rc= 0 Mar 13 21:37:25 BIGBOX kernel: ata8.00: qc timeout (cmd 0x27) Mar 13 21:37:25 BIGBOX kernel: ata8.00: failed to read native max address (err_mask=0x4) Mar 13 21:37:25 BIGBOX kernel: ata8.00: HPA support seems broken, skipping HPA handling Mar 13 21:37:25 BIGBOX kernel: ata8.00: revalidation failed (errno=-5) Mar 13 21:37:25 BIGBOX kernel: ata8: hard resetting link Mar 13 21:37:25 BIGBOX kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! Mar 13 21:37:27 BIGBOX kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[1]:rc= 0 Mar 13 21:37:32 BIGBOX kernel: ata8.00: qc timeout (cmd 0xef) Mar 13 21:37:32 BIGBOX kernel: ata8.00: failed to set xfermode (err_mask=0x4) Mar 13 21:37:32 BIGBOX kernel: ata8.00: limiting speed to UDMA/133:PIO3 Mar 13 21:37:32 BIGBOX kernel: ata8: hard resetting link Mar 13 21:37:32 BIGBOX kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! Mar 13 21:37:34 BIGBOX kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[1]:rc= 0 Mar 13 21:37:44 BIGBOX kernel: ata8.00: qc timeout (cmd 0xef) Mar 13 21:37:44 BIGBOX kernel: ata8.00: failed to set xfermode (err_mask=0x4) Mar 13 21:37:44 BIGBOX kernel: ata8.00: disabled Mar 13 21:37:44 BIGBOX kernel: ata8: hard resetting link Mar 13 21:37:45 BIGBOX kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! Mar 13 21:37:47 BIGBOX kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[1]:rc= 0 Mar 13 21:37:47 BIGBOX kernel: ata8: EH complete Mar 13 21:37:47 BIGBOX kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] READ CAPACITY(16) failed Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Mar 13 21:37:47 BIGBOX kernel: Result: hostbyte=0x04 driverbyte=0x00 Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Sense not available. Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] READ CAPACITY failed Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Mar 13 21:37:47 BIGBOX kernel: Result: hostbyte=0x04 driverbyte=0x00 Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Sense not available. Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Truncating mode parameter data from 3330 to 512 bytes Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Got wrong page Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Assuming drive cache: write through Mar 13 21:37:47 BIGBOX kernel: sdh: detected capacity change from 2000398934016 to 0 Mar 13 21:37:48 BIGBOX kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 13 21:38:03 BIGBOX last message repeated 14 times Mar 13 21:38:10 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdi drive state is: active/idle /dev/sdj drive state is: active/idle /dev/sdk drive state is: active/idle Mar 13 21:38:11 BIGBOX kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 13 21:38:56 BIGBOX last message repeated 32 times Mar 13 21:38:59 BIGBOX last message repeated 9 times Mar 13 21:39:11 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdi drive state is: active/idle /dev/sdj drive state is: active/idle /dev/sdk drive state is: active/idle /dev/sdl drive state is: active/idle /dev/sdm drive state is: active/idle /dev/sdn drive state is: active/idle Mar 13 21:40:11 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdi drive state is: active/idle /dev/sdj drive state is: active/idle /dev/sdk drive state is: active/idle /dev/sdl drive state is: active/idle /dev/sdm drive state is: active/idle /dev/sdn drive state is: active/idle Mar 13 21:41:11 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdi drive state is: active/idle /dev/sdj drive state is: active/idle /dev/sdk drive state is: active/idle /dev/sdl drive state is: active/idle /dev/sdm drive state is: active/idle /dev/sdn drive state is: active/idle Mar 13 21:42:11 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdi drive state is: active/idle /dev/sdj drive state is: active/idle /dev/sdk drive state is: active/idle /dev/sdl drive state is: active/idle /dev/sdm drive state is: active/idle /dev/sdn drive state is: active/idle Mar 13 21:43:11 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdi drive state is: active/idle /dev/sdj drive state is: active/idle /dev/sdk drive state is: active/idle /dev/sdl drive state is: active/idle /dev/sdm drive state is: active/idle /dev/sdn drive state is: active/idle Mar 13 21:43:18 BIGBOX kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 13 21:43:23 BIGBOX last message repeated 46 times Mar 13 21:43:38 BIGBOX kernel: md: disk10 read error, sector=1871085816 Mar 13 21:43:39 BIGBOX kernel: md: disk10 write error, sector=1871085816 Mar 13 21:43:39 BIGBOX kernel: md: recovery thread woken up ... Mar 13 21:43:39 BIGBOX kernel: md: recovery thread has nothing to resync Mar 13 21:44:06 BIGBOX emhttp: shcmd (69): /usr/local/sbin/emhttp_event stopping_svcs Mar 13 21:44:06 BIGBOX kernel: mdcmd (88): nocheck Mar 13 21:44:06 BIGBOX kernel: md: nocheck_array: check not active
  15. I have removed the drive and connected it to a Windows PC - it powers up, partitions are still there, and I can access the data using RFSTool - so basically the drive seems fine. However it refuses to work in unRAID. It powers up and is detected but the array config page says it is disabled. The temperature is also not displayed. There is no option to rebuilt data to the drive, so essentially it now seems to be useless in unRAID. Edit: Followed the procedure at http://lime-technology.com/wiki/index.php/Troubleshooting#Re-enable_the_drive Now the data is being rebuilt. But this seems silly, since the data was still OK!
  16. What I am about to describe might be purely a coincidence, but it does not feel like it. I ran HDSentinal on my 5.0.6 box and afterwards a disk showed as "disabled" in the devices list. Stopping and restarting the array did not fix it, nor did rebooting. Here is the complete output from running HDSentinal - you can see that it could not read temp data from /dev/hdh the first time, and the second time it failed to read any data at all: root@BIGBOX:/mnt/cache/sentintel# ./HDSentinel Hard Disk Sentinel for LINUX console 0.08 (c) 2008-2011 [email protected] Start with -r [reportfile] to save data to report, -h for help Examining hard disk configuration ... HDD Device 0: /dev/sda HDD Model ID : SanDisk Cruzer Edge HDD Serial No: 20051740710F5C01ADC9 HDD Revision : 1.26 HDD Size : 7633 MB Interface : SCSI Temperature : Unknown °C Highest Temp.: Unknown °C Health : Unknown % Performance : Unknown % Power on time: Est. lifetime: HDD Device 1: /dev/sdb HDD Model ID : ST3000DM001-9YN166 HDD Serial No: W1F101TJ HDD Revision : CC9F HDD Size : 2861588 MB Interface : S-ATA II Temperature : 26 °C Highest Temp.: 48 °C Health : 100 % Performance : 100 % Power on time: 565 days, 15 hours Est. lifetime: more than 1000 days HDD Device 2: /dev/sdc HDD Model ID : WDC WD20EARX-00MMMB0 HDD Serial No: WD-WCAWZ2783588 HDD Revision : 80.00A80 HDD Size : 1907729 MB Interface : S-ATA II Temperature : 25 °C Highest Temp.: 48 °C Health : 100 % Performance : 100 % Power on time: 637 days, 9 hours Est. lifetime: more than 1000 days HDD Device 3: /dev/sdd HDD Model ID : SAMSUNG HD204UI HDD Serial No: S2H7J1BZB29336 HDD Revision : 1AQ10001 HDD Size : 1907729 MB Interface : S-ATA II Temperature : 24 °C Highest Temp.: 45 °C Health : 100 % Performance : 100 % Power on time: 1154 days, 14 hours Est. lifetime: more than 670 days HDD Device 4: /dev/sde HDD Model ID : ST4000DM000-1F2168 HDD Serial No: S300PVJ0 HDD Revision : CC54 HDD Size : 3815448 MB Interface : S-ATA II Temperature : 27 °C Highest Temp.: 49 °C Health : 100 % Performance : 100 % Power on time: 121 days, 2 hours Est. lifetime: more than 1000 days HDD Device 5: /dev/sdf HDD Model ID : Samsung SSD 840 EVO 250GB HDD Serial No: S1DBNSADA51208J HDD Revision : EXT0BB0Q HDD Size : 238475 MB Interface : S-ATA II Temperature : 24 °C Highest Temp.: 40 °C Health : 100 % Performance : 100 % Power on time: 2 days, 12 hours, 40 minutes Est. lifetime: more than 1000 days HDD Device 6: /dev/sdg HDD Model ID : Hitachi HDS5C3020ALA632 HDD Serial No: ML0220F30R1MXD HDD Revision : ML6OA580 HDD Size : 1907729 MB Interface : S-ATA II Temperature : 24 °C Highest Temp.: 42 °C Health : 100 % Performance : 100 % Power on time: 1108 days, 16 hours Est. lifetime: more than 716 days HDD Device 7: /dev/sdh HDD Model ID : WDC WD20EADS-00R6B0 HDD Serial No: WD-WCAVY1187400 HDD Revision : 01.00A01 HDD Size : 1907729 MB Interface : S-ATA II Temperature : Unknown °C Highest Temp.: Unknown °C Health : Unknown % Performance : Unknown % Power on time: Est. lifetime: HDD Device 8: /dev/sdi HDD Model ID : ST4000DM000-1F2168 HDD Serial No: S300N8RB HDD Revision : CC54 HDD Size : 3815448 MB Interface : S-ATA II Temperature : 22 °C Highest Temp.: 49 °C Health : 100 % Performance : 100 % Power on time: 121 days, 8 hours Est. lifetime: more than 1000 days HDD Device 9: /dev/sdj HDD Model ID : ST4000DM000-1F2168 HDD Serial No: S3008WD3 HDD Revision : CC54 HDD Size : 3815448 MB Interface : S-ATA II Temperature : 23 °C Highest Temp.: 40 °C Health : 100 % Performance : 100 % Power on time: 36 days, 10 hours Est. lifetime: more than 1000 days HDD Device 10: /dev/sdk HDD Model ID : ST2000DL003-9VT166 HDD Serial No: 5YD6G1TX HDD Revision : CC3C HDD Size : 1907729 MB Interface : S-ATA II Temperature : 24 °C Highest Temp.: 43 °C Health : 100 % Performance : 100 % Power on time: 1963 days, 0 hours Est. lifetime: more than 100 days HDD Device 11: /dev/sdl HDD Model ID : WDC WD30EZRX-00D8PB0 HDD Serial No: WD-WCC4N0115460 HDD Revision : 80.00A80 HDD Size : 2861588 MB Interface : S-ATA II Temperature : 24 °C Highest Temp.: 42 °C Health : 100 % Performance : 100 % Power on time: 315 days, 9 hours Est. lifetime: more than 1000 days HDD Device 12: /dev/sdm HDD Model ID : ST3000DM001-9YN166 HDD Serial No: W1F1A2J9 HDD Revision : CC9F HDD Size : 2861588 MB Interface : S-ATA II Temperature : 24 °C Highest Temp.: 48 °C Health : 100 % Performance : 100 % Power on time: 513 days, 17 hours Est. lifetime: more than 1000 days HDD Device 13: /dev/sdn HDD Model ID : TOSHIBA DT01ACA300 HDD Serial No: 531SBGZGS HDD Revision : MX6OABB0 HDD Size : 2861588 MB Interface : S-ATA II Temperature : 27 °C Highest Temp.: 47 °C Health : 100 % Performance : 100 % Power on time: 394 days, 1 hours Est. lifetime: more than 1000 days root@BIGBOX:/mnt/cache/sentintel# ./HDSentinel Hard Disk Sentinel for LINUX console 0.08 (c) 2008-2011 [email protected] Start with -r [reportfile] to save data to report, -h for help Examining hard disk configuration ... HDD Device 0: /dev/sda HDD Model ID : SanDisk Cruzer Edge HDD Serial No: 20051740710F5C01ADC9 HDD Revision : 1.26 HDD Size : 7633 MB Interface : SCSI Temperature : Unknown °C Highest Temp.: Unknown °C Health : Unknown % Performance : Unknown % Power on time: Est. lifetime: HDD Device 1: /dev/sdb HDD Model ID : ST3000DM001-9YN166 HDD Serial No: W1F101TJ HDD Revision : CC9F HDD Size : 2861588 MB Interface : S-ATA II Temperature : 28 °C Highest Temp.: 48 °C Health : 100 % Performance : 100 % Power on time: 565 days, 15 hours Est. lifetime: more than 1000 days HDD Device 2: /dev/sdc HDD Model ID : WDC WD20EARX-00MMMB0 HDD Serial No: WD-WCAWZ2783588 HDD Revision : 80.00A80 HDD Size : 1907729 MB Interface : S-ATA II Temperature : 27 °C Highest Temp.: 48 °C Health : 100 % Performance : 100 % Power on time: 637 days, 9 hours Est. lifetime: more than 1000 days HDD Device 3: /dev/sdd HDD Model ID : SAMSUNG HD204UI HDD Serial No: S2H7J1BZB29336 HDD Revision : 1AQ10001 HDD Size : 1907729 MB Interface : S-ATA II Temperature : 25 °C Highest Temp.: 45 °C Health : 100 % Performance : 100 % Power on time: 1154 days, 14 hours Est. lifetime: more than 670 days HDD Device 4: /dev/sde HDD Model ID : ST4000DM000-1F2168 HDD Serial No: S300PVJ0 HDD Revision : CC54 HDD Size : 3815448 MB Interface : S-ATA II Temperature : 27 °C Highest Temp.: 49 °C Health : 100 % Performance : 100 % Power on time: 121 days, 2 hours Est. lifetime: more than 1000 days HDD Device 5: /dev/sdf HDD Model ID : Samsung SSD 840 EVO 250GB HDD Serial No: S1DBNSADA51208J HDD Revision : EXT0BB0Q HDD Size : 238475 MB Interface : S-ATA II Temperature : 28 °C Highest Temp.: 40 °C Health : 100 % Performance : 100 % Power on time: 2 days, 12 hours, 40 minutes Est. lifetime: more than 1000 days HDD Device 6: /dev/sdg HDD Model ID : Hitachi HDS5C3020ALA632 HDD Serial No: ML0220F30R1MXD HDD Revision : ML6OA580 HDD Size : 1907729 MB Interface : S-ATA II Temperature : 25 °C Highest Temp.: 42 °C Health : 100 % Performance : 100 % Power on time: 1108 days, 16 hours Est. lifetime: more than 716 days HDD Device 7: /dev/sdh HDD Model ID : ? HDD Serial No: ? HDD Revision : ? HDD Size : 0 MB Interface : SCSI Temperature : Unknown °C Highest Temp.: Unknown °C Health : Unknown % Performance : Unknown % Power on time: Est. lifetime: HDD Device 8: /dev/sdi HDD Model ID : ST4000DM000-1F2168 HDD Serial No: S300N8RB HDD Revision : CC54 HDD Size : 3815448 MB Interface : S-ATA II Temperature : 23 °C Highest Temp.: 49 °C Health : 100 % Performance : 100 % Power on time: 121 days, 8 hours Est. lifetime: more than 1000 days HDD Device 9: /dev/sdj HDD Model ID : ST4000DM000-1F2168 HDD Serial No: S3008WD3 HDD Revision : CC54 HDD Size : 3815448 MB Interface : S-ATA II Temperature : 24 °C Highest Temp.: 40 °C Health : 100 % Performance : 100 % Power on time: 36 days, 10 hours Est. lifetime: more than 1000 days HDD Device 10: /dev/sdk HDD Model ID : ST2000DL003-9VT166 HDD Serial No: 5YD6G1TX HDD Revision : CC3C HDD Size : 1907729 MB Interface : S-ATA II Temperature : 25 °C Highest Temp.: 43 °C Health : 100 % Performance : 100 % Power on time: 1963 days, 0 hours Est. lifetime: more than 100 days HDD Device 11: /dev/sdl HDD Model ID : WDC WD30EZRX-00D8PB0 HDD Serial No: WD-WCC4N0115460 HDD Revision : 80.00A80 HDD Size : 2861588 MB Interface : S-ATA II Temperature : 24 °C Highest Temp.: 42 °C Health : 100 % Performance : 100 % Power on time: 315 days, 9 hours Est. lifetime: more than 1000 days HDD Device 12: /dev/sdm HDD Model ID : ST3000DM001-9YN166 HDD Serial No: W1F1A2J9 HDD Revision : CC9F HDD Size : 2861588 MB Interface : S-ATA II Temperature : 25 °C Highest Temp.: 48 °C Health : 100 % Performance : 100 % Power on time: 513 days, 17 hours Est. lifetime: more than 1000 days HDD Device 13: /dev/sdn HDD Model ID : TOSHIBA DT01ACA300 HDD Serial No: 531SBGZGS HDD Revision : MX6OABB0 HDD Size : 2861588 MB Interface : S-ATA II Temperature : 28 °C Highest Temp.: 47 °C Health : 100 % Performance : 100 % Power on time: 394 days, 1 hours Est. lifetime: more than 1000 days root@BIGBOX:/mnt/cache/sentintel# ./HDSentinel -solid /dev/sda ? ? ? SanDisk_Cruzer_Edge 20051740710F5C01ADC9 7633 /dev/sdb 29 100 13575 ST3000DM001-9YN166 W1F101TJ 2861588 /dev/sdc 27 100 15297 WDC_WD20EARX-00MMMB0 WD-WCAWZ2783588 1907729 /dev/sdd 25 100 27710 SAMSUNG_HD204UI S2H7J1BZB29336 1907729 /dev/sde 27 100 2906 ST4000DM000-1F2168 S300PVJ0 3815448 /dev/sdf 29 100 60 Samsung_SSD_840_EVO_250GB S1DBNSADA51208J 238475 /dev/sdg 25 100 26608 Hitachi_HDS5C3020ALA632 ML0220F30R1MXD 1907729 /dev/sdh ? ? ? ? ? 0 /dev/sdi 24 100 2912 ST4000DM000-1F2168 S300N8RB 3815448 /dev/sdj 24 100 874 ST4000DM000-1F2168 S3008WD3 3815448 /dev/sdk 26 100 47112 ST2000DL003-9VT166 5YD6G1TX 1907729 /dev/sdl 25 100 7569 WDC_WD30EZRX-00D8PB0 WD-WCC4N0115460 2861588 /dev/sdm 26 100 12329 ST3000DM001-9YN166 W1F1A2J9 2861588 /dev/sdn 29 100 9457 TOSHIBA_DT01ACA300 531SBGZGS 2861588 root@BIGBOX:/mnt/cache/sentintel# cd .. root@BIGBOX:/mnt/cache# cd .. root@BIGBOX:/mnt# cd .. root@BIGBOX:/# Broadcast message from root (Fri Mar 13 21:46:41 2015): The system is going down for reboot NOW!
  17. I have ordered two of the 3-drive mounting cage/brackets pictured in the original post from http://eshop.macsales.com/item/Newer+Technology/G5MOUNT3HD/ I'm hoping these will let me fit 6 drives in total in the main chamber instead of 4. I'll then need two more free SATA ports and will have to swap the mobo - the current one only has 4. I can then squeeze an extra two drives in using the OWC Multimount, placed in the second chamber secured by Velcro (which came with the case, currently occupied by an SSD but this can be moved into one of two 2.5inch drive bays) - but again I'll need an extra 2 SATA ports. The plan is to get a mobo that also has a mPCIe slot so I can put in a card such as this: http://www.hwtools.net/Adapter/PM362.html If all goes well this will take the Node 804 up to 15 data drives + parity + cache.
  18. The underside of the case has holes for screwing directly into the bottom of the drives
  19. Hi all, I am trying to cram as many drives as possible into a Node 804. It has 8 hard drive bays plus room for two in the main chamber. I have fit 4 in the main chamber using OWC Multimounts, giving 11 data drives plus parity and a SSD for cache connected via the eSATA port on the motherboard. There is room for at least one more drive above each pair in the main chamber (which would take it to 13 data drives) but I don't know how to mount them securely. An adapter such as this would probably do the job but it looks a bit flimsy, and is half way around the world from me.. Any idea on alternatives for this? Case: Fractal Design Node 804 Mobo: ASRock fm2a75m-itx CPU: AMD A6-5600 Controller: Supermicro AOC-SAS2LP-MV8

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.