Jump to content

raidserver

Members
 View Profile  See their activity

  • Posts

    76

  • Joined

  • Last visited

 Content Type 

Posts posted by raidserver

    [SOLVED] My Array Won't Work!! HELP

    in General Support

    Posted · Edited by raidserver
    for clarity

    My original issue with the PCIE x4 port which i use for the HBA card/HDD`s never gave me any issues other than spamming the log with errors.

     

    Its a power management issue with the HBA trying to save power. Turning the pcie aspm off for the x4 socket solved the log errors.

     

    Hope new motherboard swap fixes your issue @Muath

     

    Edit Switched off aspm via BIOS

    • Like 1

    Why are VM's so much hard work?

    in VM Engine (KVM)

    Posted

    Not sure about nVidia 670, can you test a newer card? 980 + 1060 successful with Supermicro motherboard. Nothing needed other than choosing it within the template. Enter server BIOS and select iGPU onboard graphics to boot first which hands off the GPU for passthrough. No video output if you havent done this, windows starts loading then black screen.

     

    I couldnt be happier with Win10 VM`s. Easily passthrough SSD`s & USB devices ie: XBOX wireless for gaming 15metres away from the server :)

     

     

    (SOLVED) Set write cache permanently?

    in General Support

    Posted

    On 5/23/2019 at 1:58 AM, ideaman924 said:

    For anyone who needs the script here it is:

      

    
#!/bin/bash

# Drives
declare -a StringArray=("ata-WDC_WD2003FYYS-70W080_WJUN0123456" "DRIVE2" "DRIVE3" "DRIVE4")

# Show status
echo "Current drive status: "
for drive in ${StringArray[@]}; do
    hdparm -W /dev/disk/by-id/$drive
done

# Enable write caching
for drive in ${StringArray[@]}; do
    hdparm -W 1 /dev/disk/by-id/$drive
done

# Show status again
echo "Finished running, check if the write cache was enabled!"
for drive in ${StringArray[@]}; do
    hdparm -W /dev/disk/by-id/$drive
done

    Replace the serial codes in the StringArray and you should be good to go! Pop it in User Scripts.

    Thanks

    Enabling write cache manually worked but the changes were not persistent through reboots on AMD server.

     

    Working perfectly now.

     

    NVME M.2 Passthrough

    in VM Engine (KVM)

    Posted

    With a good dose of patience windows has made it to desktop via VNC i see the NVME drive.

     

    Performance is terrible though it takes forever to boot & shutdown.

     

    the VM log is showing

    2019-05-09T16:48:18.233068Z qemu-system-x86_64: warning: guest updated active QH

     

    spamming the log tail

    NVME M.2 Passthrough

    in VM Engine (KVM)

    Posted · Edited by raidserver

    thanks cybernook, after a bit of fumbling around with the xml iam now at the stage of booting windows which is hanging on boot loading window.

     

    I no longer receive the error stated. heres my xml, maybe i have overlooked something.

     

    Reinstalled 6.7 rc8

     

    EDIT: added vm log which shows an error near end.

     

    win8.1 xml.txt

    vm log.txt

    NVME M.2 Passthrough

    in VM Engine (KVM)

    Posted · Edited by raidserver

    Struggling to passthrough nvme drive too.

     

    Crucial CT1000P1SSD8 P1 1 TB

    [c0a9:2263] 07:00.0 Non-Volatile memory controller: Micron/Crucial Technology Device 2263 (rev 03)

     

    internal error: qemu unexpectedly closed the monitor: 2019-05-08T16:39:22.718254Z qemu-system-x86_64: -device vfio-pci,host=07:00.0,id=hostdev3,bus=pci.0,addr=0x9: vfio 0000:07:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align

     

    Unraid 6.7.0-rc8

     

    I have tried adding the alias line to my xml but that doesnt change anything, as the qemu code is also need. Is there anything i must do or should i be patient?

     

    EDIT: While i wait patiently :) i have rolled back to rc7 and all is well.

    (Solved) PCIe Bus Error

    in General Support

    Posted

    I have updated the newer 2.2b BIOS.

     

    The same errors started to spam the log file continuously again. It is occupied by my RocketRAID 640L. Before i decided to occupy the only other PCIE slot (x16) i read THIS bug report thread which has a few fixes to try.

     

    I have turned off/disabled pcie aspm on the x4 currently used slot.

     

    This power management option has fixed this issue. No more error logs.

    (Solved) PCIe Bus Error

    in General Support

    Posted

    On 01/02/2018 at 4:09 PM, johnnie.black said:

    Those can sometimes be fixed by using the offending controller on a different PCIe slot (ideally changing from a CPU slot to a PCH slot or vice versa) or with a bios update.

    Quick follow up about this because its been bugging me since i flashed the BIOS. When i revisited supermicro i found only an older BIOS which once flashed has been fine and i have no syslog errors now.

    I reached out to supermicro for an answer, they said.

     

    "The BIOS 2.2 we had on our website had fixes for the Spectre vulnerabilities.
    However, the fixes had issues and Intel has asked all Vendors to revoke the updates until new Micro codes can be released.

    So it's possible the new BIOS had the issues you saw, and our current advise would be to use the 2.0c BIOS version from our website."

     

     

    (Solved) PCIe Bus Error

    in General Support

    Posted · Edited by raidserver

    Ever since i have updated my supermicro motherboard BIOS i have been receiving these errors in the system log.

     

    Feb  1 15:47:48 Tower kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
    Feb  1 15:47:48 Tower kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e0(Transmitter ID)
    Feb  1 15:47:48 Tower kernel: pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00003000/00002000
    Feb  1 15:47:48 Tower kernel: pcieport 0000:00:1c.0:    [12] Replay Timer Timeout  

     

    After BIOS flash i have cleared CMOS and set up the server as "i think" i had it prior to the update.

     

    8086:a110 is 

    8086:a110] 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)

     

    Would appreciate any input many thanks

     

    tower-syslog-20180201-1550.zip

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted · Edited by raidserver

    since i have upgraded my very poor ISP bundled router/firewall/wifi box to a pfsense minipc(somewhat overkill) i have seen very stable VPN torrents. Before i found that it would peak then drop for awhile.

    Iam almost certain it was the poor devices lack of power to route the encrypted traffic consistently. AES-256-CBC with multiple connections @ 20mbit/s troughput.

     

     

    [Support] binhex - MiniDLNA

    in Docker Containers

    Posted · Edited by raidserver

    5 hours ago, kolla said:

     

     /nmt/

    /nmt/user/Music" so I have "/nmt/user/Music"

     

    Are these typo`s kolla? check your directory inputs its mnt(mount)

     

    once miniDLNA starts scanning you will see the files.db grow (located in the appdata binhex-miniDLNA folder) & the artwork folder starts to populate.

     

    Perhaps you could start again, uninstall minidlna then run the plugin CA cleanup appdata to wipe whats remaining of the docker.

    Pull the docker down again and set the correct directory where your files are located.

     

    • Like 1

    [Support] binhex - MiniDLNA

    in Docker Containers

    Posted

    18 hours ago, kolla said:

    Thanks I did that and re-started the server but for some reason it's not seeing anything inside "Music" share.

    Maybe something else I missed?

     

    I have not used miniDLNA for awhile so i pulled down the latest docker image.

    I left everything default other than changing where the docker should look for my music directory. which is /mnt/user/Tunes/Album

    It is now scanning all my files including artwork. So it would seem editing the .conf file is no longer needed

     

    Untitled.thumb.png.b86e989b398b1ca88cc12acdd14b6acc.png

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted · Edited by raidserver

    On 12/6/2017 at 7:36 PM, raidserver said:

    I have noticed i get maxed line for awhile then that drops off, then resumes as it was. TBH i think its my ISP`s bundled router struggling with heavy encrypted traffic. Then again it could be the tracker being brought to its knees with traffic.

     

     

    This has been happening very often recently. Looking at the logs when the speed drops off then resumes it seems its because the link goes down and then reconnects.

    This is reoccurring over and over. DNS issue?

     

    Log for binhex-delugevpn.txt

    [Support] binhex - DelugeVPN

    in Docker Containers

    Posted

    That looks fine, you have left some room for other traffic.

     

    I have noticed i get maxed line for awhile then that drops off, then resumes as it was. TBH i think its my ISP`s bundled router struggling with heavy encrypted traffic. Then again it could be the tracker being brought to its knees with traffic.

    pfsense firewall/router upgrade soon. Long overdue. :) Overkill for my setup but...technology hey lol.

     

×
×
  • Create New...