Jump to content

BLuFeNiX

Members
  • Posts

    10
  • Joined

  • Last visited

Posts posted by BLuFeNiX

  1. 6 hours ago, Frank1940 said:

    This version seems to work fine for many people:   FWVersion(20.00.07.00)  The better vendors will spell out exactly what you are getting.  If you are comfortable with flashing the firmware, it does not matter much what software/firmware is installed.  However, you must be aware enough to check and take any appropriate action required. 

    Gotcha, thanks. I'm fine with flashing firmware. If the server is stable with virtualization turned off I'll probably leave it be though :)

  2. 1 minute ago, jonathanm said:

    Since it's new, can you return the marvell based controller? Switching to an LSI chipset controller would likely solve most of your issues.

    I'm considering it. Gonna see how the stability is for a week or so, and if it doesn't freeze up I might return the card and try turning virtualization back on with a different card.

    Is LSI the gold standard for Unraid?
     

    1 minute ago, johnnie.black said:

    x4 it's fine for an LSI, less bandwidth but enough for most HDDs.


    Is there a particular card you'd all recommend?

  3. 31 minutes ago, Frank1940 said:

    The Marvell chip sets have been an issue for quite some time.  (For more information, Google  Unraid.net Marvell 88SE9230 Chipset )  You can try turning off any virtualization options in the BIOS.

    ...

    You should also check the spec's on that power supply.

    ...

    Thanks! Unraid's information panel told me IOMMU was disabled, but I've just turned off SVM in the BIOS to be safe. I'll see if I can get it to run like this, and if it happens again I'll try swapping the PSU. I will update here in several weeks, in case it's able to help anyone else down the road.

  4. 38 minutes ago, Frank1940 said:

    Yous should provide the Diagnostics file.      Tools   >>>   Diagnostics     

     

    You might also give us a rundown on the actual hardware since it is brand new build. 

     

    Is the PS new or recycled?  

    Sure thing, it's attached. The build was partially cannibalized from another server I built in 2016.

    Old parts from 2016:
    * ASRock AM1H-ITX mobo
    * 2x 2TB Seagate ST2000DM001 HDDs
    * 2x Crucial 8GB DDR3 1600 MT/s PC3-12800 CL11 Unbuffered UDIMM 240-Pin Desktop Memory CT102464BA160B
    * AMD Athlon 5350 AD5350JAHMBOX 2.05 GHz Quad-core

    New parts:
    * 2x 2TB WD AV-GP SATA III Intellipower 64 MB Cache Bulk/OEM AV Hard Drive WD20EURX
    * Syba 4 Port SATA III 6.0Gb/s PCIe Controller Card (identifies as Marvell 88SE9230 Chipset via lspci)
    * Chenbro SR30169 Tower Case SR30169T2-250 (came with new 250 watt PSU preinstalled)
    * 1x Crucial BX500 240GB 3D NAND SATA 2.5-Inch Internal SSD - CT240BX500SSD1Z
    * 1x PNY CS900 240GB 2.5” SATA III Internal Solid State Drive (SSD) - (ssd7cs900-240-rb)

    Misc details:
    * The HDDs are connected to the PCIe expansion SATA card
    * The SSDs are plugged directly into the Mobo. One of them is in a "normal" SATA port, and the other is in an ASmedia SATA port (but in regular SATA mode). This is because of the UDMA error I got, so I moved it from the normal SATA port to the ASmedia one.
    * The flash drive is from a few years ago. Not certain of age, but basically never used. I have a new one that I will be swapping in.

     

    Thanks for the help. Let me know if any more information would be useful.
     

    watt-diagnostics-20190917-0305.zip

  5. Would anyone care to take a look at my syslog? It contains multiple boots worth of logs, with the last section being the boot after the hard reset. Best I can figure, it started to hang immediately following an SSD trim. I have left several newlines separating the hang-time logs and the following reboot (around line 26800).

     

    This server build is only a few days old. I have done 5 passes with memtest86 (0 errors) prior to this happening, and the SSDs are brand new. I did have a UDMA error previously on one of the SSDs, but I swapped the cable and SATA port, and it's been fine since then.

     

    Any advice is appreciated.

    syslog.watt.txt

  6. On 9/13/2019 at 10:17 AM, trurl said:

    Disable docker service and wait for it to complete shutdown of dockers, then it will let you edit settings for docker, including authoring mode.

     

    On 9/13/2019 at 11:23 AM, Squid said:

    Just as an FYI, the only xml schema that is supported (and has been this way since the introduction of docker on unRaid) is that which is produced by the GUI.  Since there's nothing that you can do in the schema that you cannot do in the GUI, documentation on the schema itself does fall by the way side since for all intents and purposes it is an internal data structure that no one ever has any need to even look at.

     

    That being said, there are a few CA specific entries which can be added, which are fully documented and kept up to date via a link in the post which @trurl previously linked.

     

    Thanks guys. This makes sense, but I wish it were better reflected in the documentation. It seems that much of the unraid knowledge base is fragmented across old forum posts. What's the general consensus of when to trust the wiki versus when to search the forums for a more correct answer?

  7. I just built my first Unraid server a few days ago, and now I'm trying to create a docker container for it. I actually have one up and running, which I pieced together by looking at the template specification and a couple of existing template repos (limetech's and binhex's).

     

    The problem is that the template specification between the above wiki and some of the repos XMLs does not match. It seems that there was a schema change that's not reflected in the wiki.

     

    Is there an up-to-date schema document?

×
×
  • Create New...