MyKroFt

RC5 - just got one again and it eventually red balled one of my drives again..... Jun 25 10:10:23 Tower kernel: sas: command 0xf74d4d80, task 0xf75a72c0, timed out: BLK_EH_NOT_HANDLED Jun 25 10:10:23 Tower kernel: sas: Enter sas_scsi_recover_host Jun 25 10:10:23 Tower kernel: sas: trying to find task 0xf75a72c0 Jun 25 10:10:23 Tower kernel: sas: sas_scsi_find_task: aborting task 0xf75a72c0 Jun 25 10:10:23 Tower kernel: sas: sas_scsi_find_task: querying task 0xf75a72c0 Jun 25 10:10:23 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1747:mvs_query_task:rc= 5 Jun 25 10:10:23 Tower kernel: sas: sas_scsi_find_task: task 0xf75a72c0 failed to abort Jun 25 10:10:23 Tower kernel: sas: task 0xf75a72c0 is not at LU: I_T recover Jun 25 10:10:23 Tower kernel: sas: I_T nexus reset for dev 0700000000000000 Jun 25 10:10:25 Tower kernel: mvsas 0000:03:00.0: Phy7 : No sig fis Jun 25 10:10:25 Tower kernel: sas: sas_form_port: phy7 belongs to port7 already(1)! Jun 25 10:10:25 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[7]:rc= 0 Jun 25 10:10:25 Tower kernel: sas: I_T 0700000000000000 recovered Jun 25 10:10:25 Tower kernel: sas: sas_ata_task_done: SAS error 8d Jun 25 10:10:25 Tower kernel: ata7: sas eh calling libata port error handler Jun 25 10:10:25 Tower kernel: ata8: sas eh calling libata port error handler Jun 25 10:10:25 Tower kernel: ata9: sas eh calling libata port error handler Jun 25 10:10:25 Tower kernel: ata10: sas eh calling libata port error handler Jun 25 10:10:25 Tower kernel: ata11: sas eh calling libata port error handler Jun 25 10:10:25 Tower kernel: ata12: sas eh calling libata port error handler Jun 25 10:10:25 Tower kernel: ata13: sas eh calling libata port error handler Jun 25 10:10:25 Tower kernel: ata14: sas eh calling libata port error handler Jun 25 10:10:25 Tower kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 t0 Jun 25 10:10:25 Tower kernel: ata14.00: failed command: CHECK POWER MODE Jun 25 10:10:25 Tower kernel: ata14.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 Jun 25 10:10:25 Tower kernel: res 01/04:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation) Jun 25 10:10:25 Tower kernel: ata14.00: status: { ERR } Jun 25 10:10:25 Tower kernel: ata14.00: error: { ABRT } Jun 25 10:10:25 Tower kernel: ata14: hard resetting link Jun 25 10:10:27 Tower kernel: mvsas 0000:03:00.0: Phy7 : No sig fis Jun 25 10:10:27 Tower kernel: sas: sas_form_port: phy7 belongs to port7 already(1)! Jun 25 10:10:27 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[7]:rc= 0 Jun 25 10:10:27 Tower kernel: sas: sas_ata_hard_reset: Found ATA device. Jun 25 10:10:32 Tower kernel: ata14.00: qc timeout (cmd 0x27) Jun 25 10:10:32 Tower kernel: ata14.00: failed to read native max address (err_mask=0x4) Jun 25 10:10:32 Tower kernel: ata14.00: HPA support seems broken, skipping HPA handling Jun 25 10:10:32 Tower kernel: ata14.00: revalidation failed (errno=-5) Jun 25 10:10:32 Tower kernel: ata14: hard resetting link Jun 25 10:10:34 Tower kernel: mvsas 0000:03:00.0: Phy7 : No sig fis Jun 25 10:10:34 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[7]:rc= 0 Jun 25 10:10:34 Tower kernel: sas: sas_ata_hard_reset: Found ATA device. Jun 25 10:10:34 Tower kernel: sas: sas_ata_task_done: SAS error 2 Jun 25 10:10:36 Tower kernel: sas: sas_ata_task_done: SAS error 2 Jun 25 10:10:36 Tower kernel: sas: sas_form_port: phy7 belongs to port7 already(1)! Jun 25 10:10:36 Tower kernel: ata14.00: both IDENTIFYs aborted, assuming NODEV Jun 25 10:10:36 Tower kernel: ata14.00: revalidation failed (errno=-2) Jun 25 10:10:39 Tower kernel: ata14: hard resetting link Jun 25 10:10:41 Tower kernel: mvsas 0000:03:00.0: Phy7 : No sig fis Jun 25 10:10:41 Tower kernel: sas: sas_form_port: phy7 belongs to port7 already(1)! Jun 25 10:10:42 Tower emhttp: mdcmd: write: Input/output error Jun 25 10:10:42 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[7]:rc= 0 Jun 25 10:10:42 Tower kernel: sas: sas_ata_hard_reset: Found ATA device. Jun 25 10:10:42 Tower kernel: sas: sas_ata_task_done: SAS error 2 Jun 25 10:10:42 Tower kernel: ata14.00: both IDENTIFYs aborted, assuming NODEV Jun 25 10:10:42 Tower kernel: ata14.00: revalidation failed (errno=-2) Jun 25 10:10:42 Tower kernel: ata14.00: disabled Jun 25 10:10:42 Tower kernel: ata14: EH complete Jun 25 10:10:42 Tower kernel: sas: --- Exit sas_scsi_recover_host Jun 25 10:10:42 Tower kernel: mdcmd (154): spindown 4 Jun 25 10:10:42 Tower kernel: md: disk4: ATA_OP e0 ioctl error: -5 Jun 25 10:10:42 Tower emhttp: mdcmd: write: Input/output error Jun 25 10:10:42 Tower kernel: mdcmd (155): spindown 4 Jun 25 10:10:42 Tower kernel: md: disk4: ATA_OP e0 ioctl error: -5 Jun 25 10:10:42 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jun 25 10:10:42 Tower last message repeated 3 times Jun 25 10:10:42 Tower emhttp: mdcmd: write: Input/output error Jun 25 10:10:42 Tower kernel: mdcmd (156): spindown 4 Jun 25 10:10:42 Tower kernel: md: disk4: ATA_OP e0 ioctl error: -5 Jun 25 10:10:42 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jun 25 10:10:42 Tower last message repeated 3 times Jun 25 10:10:42 Tower emhttp: mdcmd: write: Input/output error Jun 25 10:10:42 Tower kernel: mdcmd (157): spindown 4 Jun 25 10:10:42 Tower kernel: md: disk4: ATA_OP e0 ioctl error: -5 Jun 25 10:10:42 Tower emhttp: mdcmd: write: Input/output error Jun 25 10:10:42 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jun 25 10:10:42 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jun 25 10:10:42 Tower kernel: mdcmd (158): spindown 4 Jun 25 10:10:42 Tower kernel: md: disk4: ATA_OP e0 ioctl error: -5 Jun 25 10:10:42 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jun 25 10:10:42 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jun 25 10:10:42 Tower emhttp: mdcmd: write: Input/output error Jun 25 10:10:42 Tower kernel: mdcmd (159): spindown 4 Jun 25 10:10:42 Tower kernel: md: disk4: ATA_OP e0 ioctl error: -5 Jun 25 10:10:43 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jun 25 10:10:43 Tower last message repeated 3 times Jun 25 10:10:43 Tower emhttp: mdcmd: write: Input/output error Jun 25 10:10:43 Tower kernel: mdcmd (160): spindown 4 Jun 25 10:10:43 Tower kernel: md: disk4: ATA_OP e0 ioctl error: -5 Jun 25 10:10:43 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jun 25 10:10:43 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jun 25 10:10:43 Tower emhttp: mdcmd: write: Input/output error Jun 25 10:10:43 Tower kernel: mdcmd (161): spindown 4 Jun 25 10:10:43 Tower kernel: md: disk4: ATA_OP e0 ioctl error: -5 Jun 25 10:10:43 Tower emhttp: mdcmd: write: Input/output error Jun 25 10:10:43 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jun 25 10:10:43 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jun 25 10:10:43 Tower kernel: mdcmd (162): spindown 4 repeats over and over until Jun 25 19:28:23 Tower kernel: end_request: I/O error, dev sdj, sector 1448887568 Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448886480/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887504/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887512/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887520/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887528/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887536/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887544/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887552/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887560/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887568/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887576/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887584/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887592/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887600/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887608/4, count: 1 Jun 25 19:28:23 Tower kernel: md: disk4 read error Jun 25 19:28:23 Tower kernel: handle_stripe read error: 1448887616/4, count: 1 Jun 25 19:28:27 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Jun 25 19:28:27 Tower last message repeated 3 times Jun 25 19:28:34 Tower kernel: sd 0:0:7:0: [sdj] Unhandled error code Jun 25 19:28:34 Tower kernel: sd 0:0:7:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00 Jun 25 19:28:34 Tower kernel: sd 0:0:7:0: [sdj] CDB: cdb[0]=0x2a: 2a 00 56 5c 41 10 00 00 08 00 Jun 25 19:28:34 Tower kernel: end_request: I/O error, dev sdj, sector 1448886544 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448886480/4, count: 1 Jun 25 19:28:34 Tower kernel: md: recovery thread woken up ... Jun 25 19:28:34 Tower kernel: md: recovery thread has nothing to resync Jun 25 19:28:34 Tower kernel: sd 0:0:7:0: [sdj] Unhandled error code Jun 25 19:28:34 Tower kernel: sd 0:0:7:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00 Jun 25 19:28:34 Tower kernel: sd 0:0:7:0: [sdj] CDB: cdb[0]=0x2a: 2a 00 56 5c 45 10 00 00 78 00 Jun 25 19:28:34 Tower kernel: end_request: I/O error, dev sdj, sector 1448887568 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887504/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887512/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887520/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887528/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887536/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887544/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887552/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887560/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887568/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887576/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887584/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887592/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887600/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887608/4, count: 1 Jun 25 19:28:34 Tower kernel: md: disk4 write error Jun 25 19:28:34 Tower kernel: handle_stripe write error: 1448887616/4, count: 1 Jun 25 19:43:42 Tower kernel: mdcmd (8123): spindown 8 Jun 25 19:43:42 Tower kernel: mdcmd (8124): spindown 9 Jun 25 19:43:42 Tower kernel: mdcmd (8125): spindown 10 Jun 25 19:43:51 Tower kernel: mdcmd (8126): spindown 5 Jun 25 19:43:52 Tower kernel: mdcmd (8127): spindown 11 Jun 25 19:43:53 Tower kernel: mdcmd (8128): spindown 12 Jun 25 19:45:36 Tower kernel: mdcmd (8129): spindown 6 Jun 25 19:45:37 Tower kernel: mdcmd (8130): spindown 7 Jun 25 19:50:35 Tower kernel: mdcmd (8131): spindown 3 Jun 25 19:51:18 Tower kernel: mdcmd (8132): spindown 1 Jun 25 19:54:13 Tower kernel: mdcmd (8133): spindown 0 Jun 25 19:54:14 Tower kernel: mdcmd (8134): spindown 2 smart report for drive says its 100% and no reallocated sectors Myk

have you looked at "subsonic" as there is a plugin for it already and works wonders..... Myk

my SF says 2 cores, 2 enables, but top is showing Cpu0, 1 and 2 - does that mean it actually has 3 cores? Myk

I have 3.1.0.21 as well on 3 cards, really dont want to spend the $$ to go so something else - still waiting on RC with update mvsas drivers to test.... Myk

On my setup I still export them, but as hidden - then if need be - I can access them direct by adding /diskX at then end of the share address.... Myk

need to have the 1st folder using a period ex: /mnt/cache/.sabnzbd Myk

or subsonic addon

might try calling support then Myk

anymore on this test release. I am starting to get these at least once a day now after going to RC4 just happened again 5 min ago, have to force reset the array again to get the GUI - which causes a dirty shutdown, the shutdown or powerdown hangs..... otherwise I can leave it, shares are still working, and I can still telnet in.... Jun 11 05:39:08 Tower kernel: sas: command 0xf4b3a6c0, task 0xf7635b80, timed out: BLK_EH_NOT_HANDLED (Drive related) Jun 11 05:39:08 Tower kernel: sas: Enter sas_scsi_recover_host (Drive related) Jun 11 05:39:08 Tower kernel: sas: trying to find task 0xf7635b80 (Drive related) Jun 11 05:39:08 Tower kernel: sas: sas_scsi_find_task: aborting task 0xf7635b80 (Drive related) Jun 11 05:39:08 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1818:<7>mv_abort_task() mvi=f70c0000 task=f7635b80 slot=f70d1640 slot_idx=x2 (System) Jun 11 05:39:08 Tower kernel: sas: sas_scsi_find_task: querying task 0xf7635b80 (Drive related) Jun 11 05:39:08 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1747:mvs_query_task:rc= 5 (System) Jun 11 05:39:08 Tower kernel: sas: sas_scsi_find_task: task 0xf7635b80 failed to abort (Minor Issues) Jun 11 05:39:08 Tower kernel: sas: task 0xf7635b80 is not at LU: I_T recover (Drive related) Jun 11 05:39:08 Tower kernel: sas: I_T nexus reset for dev 0300000000000000 (Drive related) Jun 11 05:39:08 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 3 ctrl sts=0x89800. (System) Jun 11 05:39:08 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 3 irq sts = 0x1001001 (System) Jun 11 05:39:08 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy3 Unplug Notice (System) Jun 11 05:39:08 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 3 ctrl sts=0x199800. (System) Jun 11 05:39:08 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 3 irq sts = 0x1001081 (System) Jun 11 05:39:09 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 3 ctrl sts=0x199800. (System) Jun 11 05:39:09 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 3 irq sts = 0x10000 (System) Jun 11 05:39:09 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2253:notify plug in on phy[3] (System) Jun 11 05:39:09 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1338:port 3 attach dev info is 0 (System) Jun 11 05:39:09 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1340:port 3 attach sas addr is 3 (System) Jun 11 05:39:09 Tower kernel: drivers/scsi/mvsas/mv_sas.c 379:phy 3 byte dmaded. (System) Jun 11 05:39:09 Tower kernel: sas: sas_form_port: phy3 belongs to port2 already(1)! (Drive related) Jun 11 05:39:11 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[2]:rc= 0 (System) Jun 11 05:39:11 Tower kernel: sas: I_T 0300000000000000 recovered (Drive related) Jun 11 05:39:11 Tower kernel: sas: sas_ata_task_done: SAS error 8d (Errors) Jun 11 05:39:11 Tower kernel: ata15: sas eh calling libata port error handler (Routine) Jun 11 05:39:11 Tower kernel: ata16: sas eh calling libata port error handler (Routine) Jun 11 05:39:11 Tower kernel: ata17: sas eh calling libata port error handler (Routine) Jun 11 05:39:11 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 t0 (Errors) Jun 11 05:39:11 Tower kernel: ata17.00: failed command: CHECK POWER MODE (Minor Issues) Jun 11 05:39:11 Tower kernel: ata17.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 (Drive related) Jun 11 05:39:11 Tower kernel: res 01/04:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation) (Errors) Jun 11 05:39:11 Tower kernel: ata17.00: status: { ERR } (Drive related) Jun 11 05:39:11 Tower kernel: ata17.00: error: { ABRT } (Errors) Jun 11 05:39:11 Tower kernel: ata17: hard resetting link (Minor Issues) Jun 11 05:39:11 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 3 ctrl sts=0x89800. (System) Jun 11 05:39:11 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 3 irq sts = 0x1001001 (System) Jun 11 05:39:11 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy3 Unplug Notice (System) Jun 11 05:39:11 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 3 ctrl sts=0x199800. (System) Jun 11 05:39:11 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 3 irq sts = 0x1001081 (System) Jun 11 05:39:11 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 3 ctrl sts=0x199800. (System) Jun 11 05:39:11 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 3 irq sts = 0x10000 (System) Jun 11 05:39:11 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2253:notify plug in on phy[3] (System) Jun 11 05:39:11 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1338:port 3 attach dev info is 0 (System) Jun 11 05:39:11 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1340:port 3 attach sas addr is 3 (System) Jun 11 05:39:11 Tower kernel: drivers/scsi/mvsas/mv_sas.c 379:phy 3 byte dmaded. (System) Jun 11 05:39:11 Tower kernel: sas: sas_form_port: phy3 belongs to port2 already(1)! (Drive related) Jun 11 05:39:13 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[2]:rc= 0 (System) Jun 11 05:39:13 Tower kernel: sas: sas_ata_hard_reset: Found ATA device. (Drive related) Jun 11 05:39:13 Tower kernel: ata17.00: configured for UDMA/133 (Drive related) Jun 11 05:39:13 Tower kernel: ata17: EH complete (Drive related) Jun 11 05:39:13 Tower kernel: sas: --- Exit sas_scsi_recover_host (Drive related) Jun 11 05:39:13 Tower kernel: mdcmd (113): spindown 5 (Routine) Jun 11 05:39:23 Tower kernel: mdcmd (114): spindown 9 (Routine) Jun 11 06:07:28 Tower kernel: sas: command 0xf4be7c00, task 0xf7645e00, timed out: BLK_EH_NOT_HANDLED (Drive related) Jun 11 06:11:31 Tower in.telnetd[4775]: connect from 192.168.0.99 (192.168.0.99) (Routine) Jun 11 06:11:32 Tower login[4776]: ROOT LOGIN on '/dev/pts/0' from '192.168.0.99' (Logins) Myk

am in the US, but I use the segate.com website via the support > warranty tab... Myk

o dang! i dont like finding bugs - as now it dont work ok, thanks for the confirmation... Myk

scheduled my party check to 1st tues of the month and now get this in my syslog Jun 9 23:48:01 Tower crond[1369]: failed parsing crontab for user root: [ $(date +%d) -le 7 ] && /root/mdcmd check 1>/dev/null 2>& following is in my crontab file # Scheduled Parity Check 0 0 * 2 [ $(date +%d) -le 7 ] && /root/mdcmd check 1>/dev/null 2>&1 any ideas? Myk

plus if they are out of stock for the replacement drive - you get to wait, going the preship route - for example for me had a 1.5Tb, was out of stock/discontinued - they sent me a 2TB replacement instead. Otherwise I would have had to wait for a 1.5TB somewhere to be repaired and then shipped to me.... The reconditioned drives from seagate come back with a green border on the labels - I am in the process of sending back a once repaired drive back a 2nd time. It all of a sudden starting making head clicking noises and brought down the array.... Myk

you can have seagate preship you a replacement drive for $10.95. It will include the return box, packing material and a prepaid shipping label. This is what I do, so I dont have to wait for it to go back, them to process it and ship out the replacement..... Myk PS - 10.95 is close to what it costs me to ship it back on my own, plus finding a suitable box to ship it in etc.....

seagate

Glad I could be of assistance..... Myk

/mnt/disk/cache would be incorrect, you are somehow creating that directory, it should be /mnt/cache. the contents of /mnt/cache are also seen in /mnt/user but not in /mnt/user0 Myk

ok here is what I got On Main tab, click on cache down at the bottom and make sure its set at Export > yes, Security > public then in windows if you open \\tower it will list everything share that is public, cache should be one of them, if you click and open cache - you will see its contents now in your sabnzbd plugin settings, the install/data dir in my example is /mnt/cache/.sabnzbd, this will create the .sabnzbd when the plugin is enabled and sab is started, that folder will then show up under the cache folder, in your case you can use the _sabnzbd so the mover script will leave it alone. so under windows if I want to access my cache dir I open \\tower\cache and will see all its contents. If you dont have the install/data dir setup correct, it will not make the files/folders in the cache dir - I suspect this is what is happening I also have all of my indv diskX shared being exported as hidden, I can manually access them by \\tower\disk1, but they will not show up so they will not be messed with, only thing I have showing up under \\tower is my user shares and cache, even the flash share is hidden so its not messed with. Let me know if this helps Myk

I cant get to mine remote atm to show you exactly how i have mine setup, but as soon as I get home I will post settings Myk

is there a start/end event that unraid initiates when doing parity - a external script could be called to retrieve the same info unmenu is doing, append it to syslog, sleep 5 min and then do it again until it received a end event....? Myk

real world example that happened to me last night..... had a seagate fail again for the 2nd time, and pulled the drive (clicking) out and unRaid saw disk missing, started up the array and because i dont have a spare at the moment and dunno how long seagate will take to preship one to me, I did a move from /mnt/disk11 to /mnt/disk4 to save my data (coming from parity). After the move I did a new config to remove the missing drive so I was protected again, and its now rebuilding the parity - but samba and the GUI did not fully come up when it started auto rebuilding the parity, however unmenu is giving me a status of how the rebuild is going, and I can telnet in and watch the syslog, but the drives and gui are not avail at the moment. Like in the past, as soon as the rebuild is finished they will come back up - but if I didnt have unmenu, I would not know the status of the parity rebuild. Hence a output of progress every % would be nice to the syslog... unmenu is telling me at the moment STARTED; 12 disks in array. Rebuilding Parity Total Size 1,953,514,552 KB Current 1,350,428,140 (69.1%) Speed 76,144 KB/sec Finish 131 minutes Sync Errors 0 (corrected) so it will be done soon.... Myk

ya snap would be the tool to use to do the mounting, but then you have to make sure its mounted 1st before starting sabnzbd etc - and am not sure how you would do that as I have not used snap yet Myk

not to beat a dead horse - but on 4.7 i would STRONGLY go with just 1 partition on the cache drive.... just my 2 cents Myk

on the unraid machine it needs to be referenced as /mnt/cache/_sabnzbd, but on your mac and pc you would access as \\tower\cache\_sabnzbd if you shared your cache drive as "cache" for the share name Myk

it would be /mnt/cache/_sabnzdb make sure the cache drive is shared and exported myk