exist2resist

Members
  • Posts

    329
  • Joined

  • Last visited

Everything posted by exist2resist

  1. Instead of running chmod 777 ./* I ran chmod 777 /* I know I'm lucky I wasn't performing a rm function. If I re run the permissions will that apply to the file system as well or just the disks and their shares?
  2. I understand that they don't spin down, but my understanding is instead SSDs are able to go into low power mode.
  3. My unRAID server is set to spin disks down, but I have a couple SSD drives looking to put in a third that are also spinning down. I want these SSDs to be always on. Is there a way to add these to a spin up group?
  4. I didn't even have to refresh the GUI. It auto refresh and populates the drop down lists. I just had to put in the new drive. If I removed the drive the GUI would auto refresh the drop down for me.
  5. Sweet, my array is being rebuilt without having to reboot. I can confirm that when you stop the array, plug a new drive in, unraid will detect it. I was also pulling and checking several other drives to find the correct serial # of the faulty drive. Unraid reports the drive missing in the web interface but once you plug it back in it repopulates it.
  6. Cool thanks for all the replies. I have external 24 hot swap bays so no going inside the case. I usually shut er down, but wanted to see if it is possible to do online. I will try online. Thanks again
  7. Normally I shut down my entire server when I swap out a bad drive. What is the procedure to do it live? Stop array, remove drive from array, spin down drive, remove drive, insert new drive, put in old drive slot, spin up array, and let OS rebuild array. Does the above work?
  8. What about 21? ftp://ftp.supermicro.com/driver/SAS/Marvell/MV8/SAS1/Firmware/3.1.0.21/ Then just do this....
  9. . Thanks I will search. Still can't believe how crazy all this is, all of a sudden it would just come up like that. Now I will have to go into those drives and test the files on there make sure it's not corrupted, ugh. I think this is something that would need to be documented as there could be a lot of people having their data corrupted
  10. Dude you warned me, yesterday I has a dual drive failure, I've been seeing more and more parity errors over the month. Fortunately I had dual parity, and my H310s came in from Ebay a day prior. I am rebuilding my array as we speak, flashed all 3x 310s to IT mode, hopefully it rebuilds fine and without errors. But wow, 6.3.3 what a cluster fuck, how did that slip through the cracks. Do you have a link to the thread where people complain about those SASLP-MV8 cards?
  11. I figured it out, but I had to do 1 and 3 in dos, and 5 and 6 in UEFI shell. So weird.
  12. Can you update the "See here how to use UEFI shell" link, it's not working. I have 3 h310 cards I need to flash to IT mode however I am not able to do this in DOS. Thanks
  13. I downgraded my OS from 6.3.3 to 6.2.4 Shares are there but my docker won't start right.
  14. You could pick up a 5450 for $30 on Amazon. Sent from my LG-H915 using Tapatalk
  15. I only ever ran a KODI HTPC with AMD GPUs. LibreELEC and OpenELEC support them so it should work. Are you sure your board is capable of IOMMU?
  16. You don't need this template if you have a physical GPU. You can create a VM as you normally would. This template is for those of us that want to run a headless KODI instance for the sole purpose of updating our database.
  17. I haven't changed anything in the last 2.5 years, and all of a sudden after upgrading to new version I start getting parity errors. I think it is unlikely that the hardware decided to shit the bed. However I'm going to update all firmware and bios, this weekend.
  18. I've had these controllers for 2.5 years, this is the first time that I've gotten parity errors on my server ever, and twice about a month apart. Coincidentally this started after upgrading to 6.3, I don't know if that is significant or not but that is what I have observed. What are the alternatives to this controller? Is there a firmware that I should be considering?
  19. Alright I will do that. This is weird though, I started getting random parity errors since I upgraded to 6.3 This is the second time something like this happened. Last time it was about a month or so ago when I had only a single parity drive. This is why I put in a second parity. Would parity errors occur if the mover was invoked at the time that a parity check ran?
  20. I ran the parity check again. Could you tell me if it's the drive again? I'm not sure what I'm looking for. How do I match up the recovery thread: Q incorrect message to the drive? I'd like to know for future reference, thanks. tower-diagnostics-20170504-1638.zip
  21. I have 3 controllers I will swap the cables and run the parity test again. Thanks
  22. Have a look, I will as well. ooops, uploaded the wrong file. tower-diagnostics-20170502-0959.zip