Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About stor44

  • Rank
    Advanced Member


  • Gender
  • Location

Recent Profile Visitors

738 profile views
  1. Ah I see, thanks for that info Eric! That makes sense. I’ll leave it as is then. I also have unRAID email me if there is a problem, so I’m covered either way. Cheers!
  2. Hi there. I'm seeing inconsistent behaviour with Pushover notification sounds on my unRAID server. I have Pushover configured in my Sonarr and Radarr dockers which are working normally. They send the alerts to my iPhone and Apple Watch - these display as alert notifications, while also playing an alert sound on those devices. So that's good. And I also have Pushover set up on the unRAID Notifications settings page. In this case, unRAID sends the notifications fine, but they don't trigger an alert sound. I've reinstalled the iOS Pushover app, and disabled/re-enabled unRAID notifications, and also rebooted unRAID, no change. It's not a huge problem, in fact I didn't even notice for the past month or so. Perhaps Pushover changed something in their API that breaks unRAID triggering the sounds? Anyone else use Pushover seeing this behaviour? Let me know if you need more information. Thanks for any ideas.
  3. Thanks, I was able to get this running with this. My blu-ray drive is an internal SATA drive, but it wouldn't show up until doing these commands. But as mentioned by others, it doesn't survive restarting the Docker container.
  4. Parity-sync finished, no errors. I was able to use the NVME-PCIe card in another PC here, will be more careful with future upgrades. All good now, thanks for the help.
  5. Ok I've now started a parity-sync, by following the steps in the first post (stop array, unassign parity drives, start array, stop again, re-assign, start array): Will find out in 20 hours!
  6. Thanks. I've shut down, checked connections, removed the NVME-to-PCIe card (don't need it anyway), and also re-plugged a USB drive that was having issues. The two parity drives are now showing no errors. Stupid question, but how do I now write new parity to the parity drives? I've started an array read-check, but it doesn't seem to be writing new parity information.
  7. Hi there. I've been notified today that both of my parity drives have errors. Diagnostics attached. However, I was poking around in my case earlier today dusting and installing a card, so it's possible I've bumped some cables. I had just installed an NVME-to-PCIe adapter card with an old 250GB Samsung M2 SSD on it, so I'm also wondering maybe if that is conflicting. Also, I ran a parity check on Tuesday Apr 28th with zero errors. My 10TB Seagates are new as of Black Friday (shucked), and I even pre-cleared them with binhex's docker. Am I ok to stop the array, disable auto-start, and then shut down and check connections? Thanks for any help! tower-diagnostics-20200502-1051.zip
  8. I would like to know this too, thanks to anybody who knows.
  9. Hi @klogg. So far so good with these 10TB drives once I switched motherboards. In fact I’ve since added a 4th one, but it’s only been in there a couple weeks. My monthly parity check will run next week. But I haven’t had any connection issues or missing drives anymore. Best of luck!
  10. Hi, I'm seeing the same hypervisor error as shown in the first post. I think it started with 6.8.0, but can't confirm that. My VMs are working.
  11. Yes sorry I probably confused you with my posts. When I moved unRAID and the HBA to my ASUS motherboard, at first I did have the 10TB Seagates running off the motherboard SATA ports. After a few days I decided to try the 10TB’s on the HBA, and it has been fine for several days now. Strange, but I’ll take it. Will watch for any further issues.
  12. I’ll keep my eyes open for drive firmware updates. It’s weird that they are working now, connected to the HBA. I think my old motherboard was playing a role. Anyway, I’ll mark this as solved and move on. Thanks.
  13. Update: Ok I think things are finally stable. Since moving unRAID and the HBA to my ASUS motherboard, no issues. I'm now running all three 10TB Seagates off the HBA. So yeah, just some random incompatibility with the HBA, old motherboard, and these 10TB drives? I just have my 2 cache drives and optical drive on the motherboard SATA ports. I've also repurposed my old unRAID PC by installing Windows 10. Still using a Dell H310 in there, and DrivePool to pool the drives to backup unRAID. No issues there yet, but it's a mix of old 3TB & 4TB WD Red drives. I'll stay away from adding 10TB drives to that setup. Thanks for all the help, this is an outstanding community. tower-diagnostics-20200113-0517.zip
  14. Update: Still had HBA card failing in different slots. So I've given up on my Gigabyte X58A-UD3R, and moved my unRAID setup to my other PC consisting of: Case: Fractal Design R2 XL EATX // MB: ASUS Maximus VI Formula, 1603 BIOS // Intel Core i7-4790 3.6 GHz RAM: 24GB HyperX (3x8GB) // Dell Perc H310 // Array: 1 x 10TB Seagate Barracuda Pro // 5 x WD 4TB RED // Parity: 2 x 10TB Seagate Barracuda Pro // Cache: WD Blue 500GB SSD x 2 Docker: ChannelsDVR // Plex // Sonarr unRAID Pro 6.8.0 Only problem I'm seeing now is a "softreset" on Sata8 during bootup. Is that a concern other than making it take longer to boot unRAID? Thanks. tower-diagnostics-20200102-0645.zip
  15. I love how I can run a VM on my storage server, two birds with one stone. I also love the price...considering the money I dumped into Drobo when I was younger...dude! I would like to see simpler health reporting for hard drives. Like DriveDx on Mac OS? Congrats and here's to the next 100k! Those case badges look rad.