Yellow Bananas

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by Yellow Bananas

  1. OK lets see if anyone has a simple answer before I figure it out. Im connected on my home wi-fi 192.168.1.4 and im able to open unraid dashboard which unraid is on 192.168.102.9. Different subnets. Then I open openVPN and it says im on 192.168.102.4 and then I lose connection and not able to connect to dashboard till I disconnect openVPN. So why does it do that when the VPN puts me on the same subnet?
  2. thnx for you help yesterday Squid, got my pool up and working. setting up backups and im wondering if I should select DISCS folder for usb and libvirt destination? Never mind I figured it out. oh yeah the help was from Constructor. My bad.
  3. yeah I see a Marvell 9230 sata 3 controller in the manual. A picture in BIOS. After the preclear for my other 4TB drive finishes ill go to BIOS and see about disabling it. Not sure if disabled, if it will revert to SATA 1 or 2. Have to check into it. YB Problem resolved. I moved 2 data disks to other sata ports and restarted, pool up and running.
  4. hmm ill check into it. parity sync failed and the 2 error drives disconnected from the pool. Ill check into it and do a few more things. thank you for your help. YB
  5. all disks are connected to motherboard sata ports. I believe on board controller is set to disable cause freenas required that.
  6. Thanx for the quick response. YB bugsy-diagnostics-20200606-1349.zip
  7. Just started loading unraid on my server box. Put 1 old WD red 3TB (the only one left from Freenas set up that didn't have bad sectors), 1 new WD red 3TB, 4 Seagate Constellation ES 3 TB, 2 HP Constellation ES 4TB, and Samsung 850 EVO SSD 250GB. Loaded these 2 days ago: 4 ea 3TB Seagates for data pool 2 ea WD Reds for data pool 850 EVO for cache Cache SSD healthy. The 6 data drives went through preclear no errors and added to pool and healthy. Jump to 2 days later. In process of added 1 each 4TB as parity drive. Problem: Today I added the other 4TB drive as a parity drive. As I look at the parity-sync process, 2 of the Seagate 3 TB drives have lost their temp reading (just showing *) and are racking up massive read errors. Over 350 million and climbing with 5 1/2 hours still left to finish parity-sync. Is this a known issue? The other 4 data drives are fine. All 6 drives are showing healthy in the Array display. thnx YB