fatalfurry

Members
 View Profile  See their activity

  • Posts

    56

  • Joined

  • Last visited

 Content Type 

Posts posted by fatalfurry

    Unraid OS version 6.8.1 available

    in Announcements

    Posted · Edited by fatalfurry

    2 hours ago, fatalfurry said:

    I'm getting this same error and unable to boot after upgrading. I went from 6.8.0 to 6.8.1. I've tried both the normal boot and safe mode. 

     

     

    error1.jpg

    I was able to boot after going into my bios and disabling C-States. I've been stable for almost a year with C-States set to Auto and I don't  understand how these items could be related. 

    Unraid OS version 6.8.1 available

    in Announcements

    Posted

    On 1/12/2020 at 11:28 AM, Helmonder said:

    Whoops... this is the message I am getting ! No boot...

     

    I rebooted and tried again... Worked without an issue.. So file system corruption does not seem a likely cause ?

    I'm getting this same error and unable to boot after upgrading. I went from 6.8.0 to 6.8.1. I've tried both the normal boot and safe mode. 

     

     

    error1.jpg

    Array missing disk configuration.

    in General Support

    Posted

    Thank you everyone for your input. I've taken jonathanm's advice on assigning all of my disks as they were previously including the correct drives for parity 1 and parity 2. At first glance everything is looking good and I'm running a parity check.

     

    Looking into UPSs I've realized I don't know enough about the nuances. Are there any recommendations on a UPS that can be rack mounted? 

    Disk read errors after server hardware upgrade.

    in General Support

    Posted

    Over the past week I've slowly been upgrading my system from an old i5 to a Threadripper x1950 in a new Norco 4224 case. 

     

    Old server 

    i5 3570

    16 GB ram 

    1x Dell Perc H310 flashed IT mode. 

     

    New Server 

    Threadripper x1950

    Asrock Taichi x399

    16 GB ECC Ram

    2x Dell Perc H310 flashed in IT mode. 

     

    The system was running fine in the new server until today when I started to build a new VM and received disk read errors. One of the disks are disable and it is running a parity check finding 100k in errors so far and it's only 2% complete. 


    Attached is my diagnostic

    I'm hoping someone has insights into what has happened. 

     

     

    tidehunter-diagnostics-20181206-1608.zip

    LSI Controller FW updates IR/IT modes

    in Storage Devices and Controllers

    Posted

    On 4/14/2018 at 11:13 PM, Fulcrum77 said:

    First, a little background.  I have an old Gigabyte motherboard that only supports Sata II and PCIE 2.0.  I just picked up a new Samsung EVO 1TB SSD.  I was trying to buy a SATA III PCIE card to upgrade the machine but most of the ones I found were only PCIE x1 or x2 and didn't seem to support the full bandwidth of 6Gbps SATA III at PCIE 2.0 speeds.  I saw several people making suggestions of picking up a Dell H310 and flashing it to an LSI 9211 IT mode for this purpose.  So, I picked up a used board on eBay and attempted to flash it this evening and I am concerned that I may have bricked the card!  I'm not sure if this was the best course of action but I invested less then $30 in the card with the included cable. 

     

    I am planning on solely using this in Windows 10 as an interface for the Samsung SSD.  I realize that this forum is generally for unRAID stuff but my difficulty seems to be in the flashing part of the adventure and you kind people seem to be the most knowledgeable on this topic!

     

    I originally started following this guide:

     

    https://tylermade.net/2017/06/27/how-to-crossflash-perc-h310-to-it-mode-lsi-9211-8i-firmware-hba-for-freenas-unraid/

     

    I got my SAS address with no problem.

     

    I then executed "megarec.exe -writesbr 0 sbrempty.bin" and it returned a Success!  The way the guide was worded I assumed since the command succeeded I could skip the step of "megarec.exe -cleanflash 0", so I rebooted the system.  No RAID BIOS loaded and I just booted straight to the USB drive.

     

    When I execute the "sas2flsh.exe -o -f 6GBPSAS.fw" I get an error of:

     

    Chip is in RESET state.  Attempting Host Boot...

    ERROR: Firmware Host Boot Failed !

    Due to error remaining commands will not be executed.

    Unable to Process Commands.

    Exiting SAS2Flash.

     

    I went back and executed "megarec.exe -cleanflash 0" but that has not helped the problem.

     

    The little green light on the card is still flashing.

     

    I then did some searching on this error and found these forums and your awesome batch files for accomplishing the flash.  I wish I had found these first!  When I run your batch files I get the error:

     

    Controller is not operational.  A firmware download is required.  Enter firmware file name or quit to exit:

     

    So I enter the path back to the 6GBPSAS.fw that I had previously and it gives the error:

     

    Beginning Firmware Download:

    Firmware Download Failed!

     

    At this point I am not sure which direction I need to go.  Is this correctable?

     

    Also, are my expectations for this project even attainable?  Will this card (assuming I get it to work) give me full 6Gbps SATA III for the Samsung SSD in the Windows environment.  Are there any other possibly better options out there?  Thanks in advance for any input or insights into my situation.

     

     

     

    On 4/15/2018 at 7:35 AM, nthu9280 said:

    The card is not bricked. While the instructions you linked are detailed, it fails to explicitly say to use the older version of SAS2FLSH tool for the first time.

    You will need SAS2FLSH version (phase) 14 or below for flashing 6gbp SAS FW. Then you can flash the IT mode FW.

    Sent from my Nexus 6 using Tapatalk
     

     

    On 4/15/2018 at 11:40 AM, Fulcrum77 said:

     

    I tried the P07 version of SAS2FLSH and while it did recognize the version number of the chip (B2) it still gave me an error.  Here is a screen of the issue with the command that I used at the bottom:

     

    What am I missing?  Thanks.

    0415181131.jpg

     

    On 4/15/2018 at 12:47 PM, nthu9280 said:

    Try the P14 version.
    Also, copy the FW file in the same directory as the sas2flsh. Not sure if that makes a difference. But just to rule out the quirks.

    Sent from my Nexus 6 using Tapatalk
     

     

    On 4/15/2018 at 2:05 PM, Fulcrum77 said:

    OK.  I got the P14 version of SAS2FLSH and it just hangs when attempting host boot.  It has been like this for about 30 minutes.  I'm assuming it will wait forever!  Any other ideas?  Thanks again.  I really appreciate the effort.

     

    0415181355.jpg

     

    On 4/15/2018 at 4:48 PM, nthu9280 said:

    It can be frustrating at time and I've gone thru' this pain. Try the following sequence. Someone had reported success with writing empty sbr after cleanflash. The standard sequence is before. Also check the syntax for my steps. I'm typing this on mobile from my memory.


    Try starting over:
    1. megarec -cleanflash 0
    2. Megarec writesbr sbrempty.bin
    3. Reboot
    4. Sas2flsh-p14 (without -o) -f 6gbpsas.fw
    5. Reboot
    6. Sas2flsh-p20 -f 2118IT.bin
    7. Sas2flsh-p20 (sas-add)


    Sent from my Nexus 6 using Tapatalk
     

     

    On 4/15/2018 at 11:25 PM, Fulcrum77 said:

     

    SUCCESS!!  I'm not sure what exactly did it this time because I had tried the -cleanflash previously several times and it always gave an error.  But, this time I did it first and, it actually completed.  Then -writesbr also completed and it allowed me to continue to flash the firmware!  Go figure.  Maybe it was the several reboots in between this time around?

     

    Thanks nthu9280 for all of the help.  It is greatly appreciated!  It is now working extremely well in Windows 10 with the Samsung 860 Evo 1TB SSD.  I was getting 528 MB/s Write and 571 MB/s Read transfer rates.  I am definitely happy with that.  It was actually faster then my test machine's (Dell Optiplex 7010) internal SATA III ports with a Samsung 850 Evo 250GB SSD.

     

    I did install the BIOS as I need to use it as my boot card on my older machine that I am moving it too.  I originally didn't install the BIOS on the card and it wasn't selectable as a boot device.  It works great now.  Here are some screens.  Thanks again!

     

     

    0415182129a.jpg

    0415181802.jpg

    Doing more research looks like fulcrum77 had the same issue back in April. I follow the same directions finding Sas2flsh P14 and trying to flash any of the three firmware (Dell, P7, P20) and nothing has been working. I still see a light blinking on the HBA so I'm thinking there's still a chance. 

    LSI Controller FW updates IR/IT modes

    in Storage Devices and Controllers

    Posted

    I'm not sure if I've bricked my Dell H310

     

    Going through the process I've gotten to step 3 and received an error code 64.

    ClearFlash.thumb.jpg.0ae831d030840a8520c67a4e2615a0ce.jpg

     

    I continued to the next step and tried to flash the dell firmware but that also threw an error.

     

    image.thumb.png.7d3dd07ce3708786276a9f4a619f955b.png

     

    I've tried going through all of the steps again and nothing seems to be working. I've tried two computers and using BIOS and UEFI scripts. All of which are return the same results above. 

     

    What can i do going forward? Do you think I've bricked my HBA? 

    Mac OS High Siera - 9p Sharing files

    in VM Engine (KVM)

    Posted

    I've used this setup previously between unRaid and a Linux host, but cannot get it working with my Mac VM. 

     

    running the mount command manually 

      

     sudo mount -t 9p -o trans=virtio,version=9p2000.L shares /mnt

    I receive the following error. 

      

    mount: exec /Library/Filesystems/9p.fs/Contents/Resources/mount_9p for /mnt: No such file or directory

     

    The /mnt directory does exist on the Mac and searching for this error hasn't resulted in many things for me to try. 

     

    Has anyone been able to setup 9p sharing with a Mac or have any advice on what to try next? 

     

     

    [Support] binhex - rTorrentVPN

    in Docker Containers

    Posted

    I'm not concerned with my local IP and Routing, but about what could be exposed through the VPN.

     

     

    1 hour ago, c0nfuzed said:

     

    A few things to consider before you start to worry.

    1. This container is not exposed to the internet directly... it uses a VPN.  When connected, it's public IP is not the IP of your machine, but the shared public IP of your VPN server.. often used by hundreds of others. (whole point of VPN for anonymity with torrenting)  So an attacker cannot target your rtorrent server directly.

    2. Because your running rtorrent behind a shared IP address, the ONLY way to allow an incoming connection is with a port forward, and in most cases, the only port you would forward would be the rtorrent "listening port", if any, and only if your VPN provider even allows it.

    3. When you start the container, you specify ports mappings... there is little reason to create a port mapping for the RPC port 5000 unless you are planning on running rutorrent or other XML-RPC management tools outside the container.  Because rutorrent is included inside, this is very unlikely.

     

    That said, even if network.scgi.open_port is set, you are safe using this unless you made some very intentional implementation decisions to expose RPC to the world ( for example added a port mapping for port 5000 in docker and at your VPN provider).

     

    [Support] binhex - rTorrentVPN

    in Docker Containers

    Posted

    I've seen a few headlines concerning rtorrent and it's security around xml-rpc

    https://f5.com/labs/articles/threat-intelligence/malware/rtorrent-client-exploited-in-the-wild-to-deploy-monero-crypto-miner

    https://arstechnica.com/information-technology/2018/03/hackers-exploiting-rtorrent-to-install-unix-coin-miner-have-netted-4k-so-far/

     

    This was discussed on github in the following issue

    https://github.com/rakshasa/rtorrent/issues/696

     

    I don't see network.scgi.open_port or network.scgi.open_local set in the rtorrent.rc but in not 100% familiar with the setup of this docker container. Is there another place to check if this security issues affects us?