hmatos

Members
  • Posts

    9
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

hmatos's Achievements

Noob

Noob (1/14)

0

Reputation

  1. ckuburlis, Great job, thank you for taking this on. A quick question ... which plug-ins if any did you include (i.e., homebridge-isy-js, homebridge-sonos, homebridge-nest, etc? I'm currently running this in an ubuntu VM and I'm wondering if I can just use this docker version. Thanks, hm
  2. I believe it's .21 -- I can't bring my array down right now, but the moment I do I'll respond with the exact version.
  3. I'm not too confident - I'm pretty sure I already had Beta 12 installed and it did the same thing. I do know that RC2 and RC3 definitely caused the same issue. How confident are you that -beta11 works, and -beta12 and everything after does not recover correctly from these driver reported errors? In other words, are you sure -beta12 introduced a regression (i.e., something changed where this problem appeared when it didn't before)?
  4. It seems to be the known issue where you have to go back to 5.0 Beta 11. Going to this version finally fixed the problem. I guess the new kernel doesn't like the SAS cards? BTW, I can login to the system and execute just about any command. It will NOT let me do anything like umount or reboot or shutdown; it just hangs. The clients also lose die while trying to access any of the shares.
  5. I have been running great under all versions of 5.0 (currently at RC3) until a recent hardware swap. I'm hoping someone can point me to what's causing the issue. I recently moved a functioning array into the configuration below. I've only been able to successfully generate parity once. I've run into a situation where running preclear_disk.sh on two drives which smartctl returned pending errors on would cause the system to lock up (except for the unix prompt). I've since given up on those two drives and removed them from the array (plugged in, but not part of array). The error below has been a constant throughout the build-out process; result is always the same, UnRAID locks up (emhttp) and the only thing I can do is manually power down the server. May 29 22:20:27 Media-Server kernel: sas: command 0xec464e40, task 0xec4a72c0, timed out: BLK_EH_NOT_HANDLED May 29 22:20:27 Media-Server kernel: sas: Enter sas_scsi_recover_host May 29 22:20:27 Media-Server kernel: sas: trying to find task 0xec4a72c0 May 29 22:20:27 Media-Server kernel: sas: sas_scsi_find_task: aborting task 0xec4a72c0 May 29 22:20:27 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 1818:<7>mv_abort_task() mvi=f7680000 task=ec4a72c0 slot=f76916a8 slot_idx=x4 May 29 22:20:27 Media-Server kernel: sas: sas_scsi_find_task: querying task 0xec4a72c0 May 29 22:20:27 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 1747:mvs_query_task:rc= 5 May 29 22:20:27 Media-Server kernel: sas: sas_scsi_find_task: task 0xec4a72c0 failed to abort May 29 22:20:27 Media-Server kernel: sas: task 0xec4a72c0 is not at LU: I_T recover May 29 22:20:27 Media-Server kernel: sas: I_T nexus reset for dev 0000000000000000 May 29 22:20:27 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 0 ctrl sts=0x89800. May 29 22:20:27 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 0 irq sts = 0x1001 May 29 22:20:27 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy0 Unplug Notice May 29 22:20:27 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 0 ctrl sts=0x199800. May 29 22:20:27 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 0 irq sts = 0x1081 May 29 22:20:28 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 0 ctrl sts=0x199800. May 29 22:20:28 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 0 irq sts = 0x10000 May 29 22:20:28 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2253:notify plug in on phy[0] May 29 22:20:28 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 1338:port 0 attach dev info is 0 May 29 22:20:28 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 1340:port 0 attach sas addr is 0 May 29 22:20:28 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 379:phy 0 byte dmaded. May 29 22:20:28 Media-Server kernel: sas: sas_form_port: phy0 belongs to port0 already(1)! May 29 22:20:30 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[0]:rc= 0 May 29 22:20:30 Media-Server kernel: sas: I_T 0000000000000000 recovered May 29 22:20:30 Media-Server kernel: sas: sas_ata_task_done: SAS error 8d May 29 22:20:30 Media-Server kernel: ata15: sas eh calling libata port error handler May 29 22:20:30 Media-Server kernel: ata15.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 t0 May 29 22:20:30 Media-Server kernel: ata15.00: failed command: CHECK POWER MODE May 29 22:20:30 Media-Server kernel: ata15.00: cmd e5/00:00:00:00:00/00:00:00:00:00/40 tag 0 May 29 22:20:30 Media-Server kernel: res 01/04:ff:00:00:00/00:00:00:00:00/40 Emask 0x3 (HSM violation) May 29 22:20:30 Media-Server kernel: ata15.00: status: { ERR } May 29 22:20:30 Media-Server kernel: ata15.00: error: { ABRT } May 29 22:20:30 Media-Server kernel: ata15: hard resetting link May 29 22:20:30 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 0 ctrl sts=0x89800. May 29 22:20:30 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 0 irq sts = 0x1001 May 29 22:20:30 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy0 Unplug Notice May 29 22:20:30 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 0 ctrl sts=0x199800. May 29 22:20:30 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 0 irq sts = 0x1081 May 29 22:20:30 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 0 ctrl sts=0x199800. May 29 22:20:30 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 0 irq sts = 0x10000 May 29 22:20:30 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 2253:notify plug in on phy[0] May 29 22:20:30 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 1338:port 0 attach dev info is 0 May 29 22:20:30 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 1340:port 0 attach sas addr is 0 May 29 22:20:30 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 379:phy 0 byte dmaded. May 29 22:20:30 Media-Server kernel: sas: sas_form_port: phy0 belongs to port0 already(1)! May 29 22:20:32 Media-Server kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[0]:rc= 0 May 29 22:20:32 Media-Server kernel: sas: sas_ata_hard_reset: Found ATA device. May 29 22:20:32 Media-Server kernel: ata15.00: configured for UDMA/133 May 29 22:20:32 Media-Server kernel: ata15: EH complete May 29 22:20:32 Media-Server kernel: ata16: sas eh calling libata port error handler May 29 22:20:32 Media-Server kernel: ata17: sas eh calling libata port error handler May 29 22:20:32 Media-Server kernel: ata18: sas eh calling libata port error handler May 29 22:20:32 Media-Server kernel: ata19: sas eh calling libata port error handler May 29 22:20:32 Media-Server kernel: ata20: sas eh calling libata port error handler May 29 22:20:32 Media-Server kernel: ata21: sas eh calling libata port error handler May 29 22:20:32 Media-Server kernel: ata22: sas eh calling libata port error handler May 29 22:20:32 Media-Server kernel: sas: --- Exit sas_scsi_recover_host May 29 22:20:52 Media-Server kernel: sas: sas_ata_task_done: SAS error 2 Hardware: NORCO RPC-4224 4U Case SUPERMICRO MBD-X8SIA-F-O w/ Pentium G6950 4x Crucial 4GB 240-Pin DDR3 SDRAM ECC Unbuffered DDR3 1333 (16GB) 2x AOC-SASLP-MV8 No Plug-ins 13 Disks (varying size), Parity Drive is 3TB (disabled), all connected to the SASLP cards /dev/md10 932G 496G 437G 54% /mnt/disk10 /dev/md9 932G 886G 46G 96% /mnt/disk9 /dev/md6 1.9T 378G 1.5T 21% /mnt/disk6 /dev/md11 1.4T 1.4T 39G 98% /mnt/disk11 /dev/md7 1.9T 1.8T 73G 97% /mnt/disk7 /dev/md8 1.9T 1.8T 114G 94% /mnt/disk8 /dev/md1 1.9T 1.8T 56G 98% /mnt/disk1 /dev/md5 1.9T 366G 1.5T 20% /mnt/disk5 /dev/md3 1.9T 1.8T 55G 98% /mnt/disk3 /dev/md12 1.4T 1.3T 91G 94% /mnt/disk12 /dev/md4 1.9T 1.8T 67G 97% /mnt/disk4 /dev/md2 1.9T 1.8T 102G 95% /mnt/disk2 /dev/md13 932G 614G 319G 66% /mnt/disk13 Any help would be greatly appreciated. BTW, can I just go back to 4.7 and just use the 3TB as a 2TB drive? - hm unRAID-Logs.zip
  6. I had no problem using 5.0-beta6, but it seems that since installing beta7 I'm not able to build parity without what appears to be a kernel panic. The system freezes, there's output on the monitor and all the keyboard lights are flashing. How do I go about collecting the panic information so I can forward to Lime Tech.? - Thanks
  7. Same here ... I've been waiting ever since I purchased my Pro license. I don't have a test environment, although I might be able to set something up. I do have several Macs and iOS devices that would use the AFP service. - Heroildo Thanks! I will probably be taking you up on that. I have a test server set up and a couple Mac's in the house that I can test with. Let me know if/when you need help and I will help as much as possible. I too have a test box and several Macs that I can test with, including PPC and Intel boxes. I'll do what I can! Doug