dmoney517

Members
  • Content Count

    41
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dmoney517

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Thank you again! I was able to flash and get back online with out any issues!
  2. Thanks! Also - Could be a dumb question - but how do I know which version of sas2flash to use (Im thinking x86-64, but want to be sure. I'm not sure what 'ppc64' is referring to, and do not want to do the wrong package.). Edit - Looks like the ppc64 is for PowerPc. So It looks like I need x86-64 as I was thinking. Would still appreciate confirmation this all looks correct. Thanks! I am using 9211-8i P20 to for LSI SAS2008 B2 Appreciate the guidance and experience!
  3. Parden my ignorance - Does this just mean to stop the array? I dont have any disks mounted that are not part of the array. I have 3 disks in Unassigned Devices that are NOT mounted.
  4. I am searching for firmware on the site in your pther post, but all I am seeing is drivers. Sorry, I don't know a ton about SAS controllers. I am searching for this model = LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) Is this correct? When I search this on the support page, it only returns drivers.
  5. Thanks. I will get the drive back to a normal state then update the firmware. Strange that this is popping up now after running without any issues for 3 years.
  6. Of course, as I say this, I just got an email saying one of my parity drives went to disable state. I just put new SAS breakouts in after I had the issue with the last disk. is it the controller? Im now having constant dsbl disks with 2 different sets of cables.
  7. Thanks! Rebuild finished succesfully, and I ran an extended smart on the drive and it is coming back clean. Appreciate your input. I will look into updating the firmware as well.
  8. Thanks. I rebooted again, and have now restarted the re-build again. This time the rebuild is running well at the expected 130MB/s. And the disk is not in DSBL. Diagnostics attached. maybe the 2nd DSBL on the disk came because the parity rebuild got aborted? I don't know - but hopefully this re-build runs successfully and the disk stays up. I have another new drive coming in the mail tomorrow as well (received a new warning late last night about a different disk failing ((Subject: Warning [NAS] - seek error rate (failing now) is 6619148)), which is what got me moving on fixing this one
  9. Oh wow. I did not realize it was a check. Why would this keep going to dsbl? It is a new disk, on cables that are good. Is there some data on that disk that could be causing this?
  10. About a week ago, I had a disk go into DSBL state. My array continued to function. The disk was locked to only hold my security camera footage, and my windows nightly backups. I was not overly worried about either things (really important windows stuff also backs up to OneDrive). So I drug my feet on doing anything about it. I had a backup ready and pre-cleared in unassigned devices, so when i stopped my array this morning, I swapped the disks, and started parity rebuild. 15 minutes in I saw that the parity rebuild was super slow (4TB disk rebuild time was like 30 d
  11. I'm having an issue with my motherboard temps being very high. I originally posted this in the General tab, and it was recommended to post here... My typical idle temps, are 45c CPU, and 57-60c mobo. This by itself feels high. If I have 1 or 2 plex streams running, temps may raise a degree or 2, but nothing that worries me. The issue comes whenever I start a Win10 VM. It is a basic web browsing VM that my wife RDPs to from a chromebook so she can work in a windows ecosystem. It has 4 cores, and 6 GB RAM. Whenever it is running, my temps go up to 60c
  12. Thanks for the reply. Atttached below is a screenshot of the options I have when I choose a sensor - I am using the sensor for MB Temp. The labelling from the driver is incorrect if that is not the correct sensor for MB temps.
  13. Hello All - I am experience high Motherboard temps whenever I start a Win10 VM, and sometimes when idle. My typical idle temps, are 45c CPU, and 57-60c mobo. This by itself feels high. If I have 1 or 2 plex streams running, temps may raise a degree or 2, but nothing that worries me. The issue comes whenever I start a Win10 VM. It is a basic web browsing VM that my wife RDPs to from a chromebook so she can work in a windows ecosystem. It has 4 cores, and 6 GB RAM. Whenever it is running, my temps go up to 60c CPU and 80c mobo, and hold there until I s
  14. Solved my own issue. needed to update my port fowarding (changed port by mistake when installing new version) and update config.php to accept the DNS address as trusted domain.
  15. I had the same versioning issue as most here - Once I was upgraded to 16, everything seemed to work, until i tried to access in my android app. It seems now that my DNS is no longer being recognized. I can connect on my local network with the IP:port, but when i try to connect (local or not) with my DynDNS:port i am getting a "The Server took too long to respond" error. I never made any changes in nextcloud previously to use the DNS. It is configured on my unraid server to use for any traffic (I know it is worked, as my OpenVPN is using it as well and I can connect wi