Jump to content

Kirkbuilder

Members
  • Posts

    31
  • Joined

  • Last visited

Posts posted by Kirkbuilder

  1. On 8/2/2023 at 1:23 PM, TCMapes said:

    Hardlinks not working.  Am I missing something for my docker setup.  Do I even need the /media path?

     

    image.thumb.png.07b5026023e9dc6357558dbf5c5318bc.png

     

    When I check to see if hardlinks are using for my share /data it is showing it is not used.

     

    image.png.1efca071d519698aa9070fb408aafcc1.png

     

    All my dockers use the data share I setup using the TRaSH guide for hardlinks.

     

    image.png.647a5cebce20ece4ac7e94c7f5c921c6.png

     

     

    Hey!  

     

    Did you ever figure this one out?  After updating to newest Unraid and Radarr 5.0.3.8127 I started having similar issues.  I was able to get Radarr working with nzbget again - sort of, but am still having multiple issues.   Radarr is continuing not see movies in some directories and so continues to download and move files to directories. For example, Radarr does not see that a copy of the movie “The way we were” is in the directory, but will download a new copy (in this example 2 copies a 720p and 1080p) and copy the files to the directory, but not update that those very files it moved to the directory are in the directory. I am seeing lots of database “locked” errors in the log, but have performed .recover operations via sqlite3 commands in the wiki and they persist.

     

    image.thumb.png.4527fc53a1f5761ca388b89dca3a394e.png

    image.png.e676a3f298c1f5016639b6190f59aa5a.png

    image.png.49b30a211c1b0b53c200650da3f90a37.png

     

     

    Logs:  https://privatebin.net/?aa32f003bc3fde6e#8T6LZPWCmaUBRnW7GrNoQVFxsNWJddKYqndCKb7ZHCui

     

    Any assistance would be appreciated.

  2. On 9/8/2023 at 12:48 PM, ChatNoir said:

    Possibly if you already have an extension card using x16 (graphics card maybe), your motherboard wouldn't or couldn't provide you x8 but only x4 ?

    No other cards are installed in the PCI slots.  I have been looking for a way to determine if there is a setting which is keeping the power low on the motherboard or on the expander card.  Any ideas?

  3. 10 hours ago, JorgeB said:

    The HBA is only linking at x4:

     

    Speed 5GT/s, Width x4 (downgraded)

     

    That means around 1600MB/s usable total, with 16 drives it's 100MB/s, so it checks out.

     

    To be able to get around 200MB/s the HBA would need to be on an x8 slot and you'd also need a faster expander, current one will max out at around 120MB/s as mentioned. 

    What would you suggest to replace it?

  4. Love this topic!  I read all the posts here and I am still a bit confused.  Please forgive my ignorance about hardware, but I am trying 🙂  I have been trying to figure out how to increase my disk speeds on my array and was told in a discord channel that I was stuck at my current speeds and there was nothing to be done about it.  BUT, I kept on looking and found this wonderful article which I have learned a great deal from.  My problem, my array of 18 disks is doing read/write at ~100mb and am currently shrinking my array using the second non-volatile procedure of moving the data using unbalance and then 0'ing out the drive to update parity, etc, etc. but am only getting 69.8 MB/s.  As can be seen here: image.png.7d70afb03e56139c0c324b37239f7a4b.png

    Here is my array:image.thumb.png.a83e3125f1773e2675e9e212a641d04b.png

     

    Here is my setup Unraid 6.12.3:

    GA-7PESH2 GIGABYTE Intel Rev1.0 LGA2011 E-ATX Server Motherboard LSI2008 8x SAS/SATA, 2x 10G X540-AT2, Avocent IPMI 2.0 (GA-7PESH2)

    2x Intel Xeon E5-2690 v2 3.0GHz 10 Core 25MB Cache Processors

    128GB DDR3 1600MHz ECC Registered Memory 8x 16GB

    HP 487738-001 468405-001 24-Bay 3Gb SAS Expander Card

    Samsung 860 QVO 1TB 2.5 Inch SATA III Internal SSD (MZ-76Q1T0B/AM) x2 Cache

    24 x 8+ TB Drives

     

    I want to try to maximize bandwidth since it is taking me ~40 hours to "0" out an 8TB drive.  From what I have read, I am now thinking I need to get 2 SAS cards to do this, but was hoping you might confirm that a good option would be 2x LSI 9305-24i's.

     

  5. 18 minutes ago, dlandon said:

    It didn't mount.  This is off the wall, but change the 'USB_DISK' mount point to another name.  Also, try the disk in another computer to see if it mounts.

     

    Why are you mounting a USB stick with ntfs?  Reformat it to vfat.  Windows will able to read it.

    I am mounting NFS with the thumb drive to test mounting external disks which are multi-terabyte drives.  Once i am able to mount this this thumb drive I should be able to mount the external drives which contain data to load onto the array.  The thumb drive mounts with no issue on all other windows computers in my environment.  I tried changing the mount name to USB_THUMB and it still will not mount. 

    image.thumb.png.31bd1e5fad58e3c7b4fe0412248a15d7.png

    image.png.f7befe5c642a32cfce3c4c12d0ce466b.png

    I tried unplugging and replugging in as well, no joy.

     

  6. 4 hours ago, dlandon said:

    There is an issue with one of your disks because it has a duplicate UUID.  You can fix this in UD settings by creating a new UUID.

    
    May 30 22:31:45 Tower unassigned.devices: Adding disk '/dev/sdy1'...
    May 30 22:31:45 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdy1' '/mnt/disks/WDC_WD80EMAZ-00WJTA0_1SJL8HJZ'
    May 30 22:31:55 Tower kernel: XFS (sdy1): Filesystem has duplicate UUID e406c996-a5c7-450c-bde9-bc2f889ce9df - can't mount
    May 30 22:31:55 Tower emhttpd: read SMART /dev/sdy
    May 30 22:31:56 Tower unassigned.devices: Mount of '/dev/sdy1' failed: 'mount: /mnt/disks/WDC_WD80EMAZ-00WJTA0_1SJL8HJZ: wrong fs type, bad option, bad superblock on /dev/sdy1, missing codepage or helper program, or other error. '

    Your thumb drives don't show any indication of errors.  It's almost as if they mounted, but UD doesn't pick that up.  Post the output from the following command:

    
    mount

     

    root@Tower:~# mount
    proc on /proc type proc (rw)
    sysfs on /sys type sysfs (rw)
    tmpfs on /dev/shm type tmpfs (rw)
    tmpfs on /var/log type tmpfs (rw,size=128m,mode=0755,size=384m)
    /dev/sda1 on /boot type vfat (rw,noatime,nodiratime,flush,dmask=77,fmask=177,shortname=mixed)
    /boot/bzmodules on /lib/modules type squashfs (ro)
    /boot/bzfirmware on /lib/firmware type squashfs (ro)
    hugetlbfs on /hugetlbfs type hugetlbfs (rw)
    overlay on /lib/modules type overlay (rw,lowerdir=/lib/modules,upperdir=/var/local/overlay/lib/modules,workdir=/var/local/overlay-work/lib/modules)
    overlay on /lib/firmware type overlay (rw,lowerdir=/lib/firmware,upperdir=/var/local/overlay/lib/firmware,workdir=/var/local/overlay-work/lib/firmware)
    /mnt on /mnt type none (rw,bind)
    tmpfs on /mnt/disks type tmpfs (rw,size=1M)
    tmpfs on /mnt/remotes type tmpfs (rw,size=1M)
    /dev/md1 on /mnt/disk1 type xfs (rw,noatime)
    /dev/md2 on /mnt/disk2 type xfs (rw,noatime)
    /dev/md3 on /mnt/disk3 type xfs (rw,noatime)
    /dev/md4 on /mnt/disk4 type xfs (rw,noatime)
    /dev/md5 on /mnt/disk5 type xfs (rw,noatime)
    /dev/md6 on /mnt/disk6 type xfs (rw,noatime)
    /dev/md7 on /mnt/disk7 type xfs (rw,noatime)
    /dev/md8 on /mnt/disk8 type xfs (rw,noatime)
    /dev/md9 on /mnt/disk9 type xfs (rw,noatime)
    /dev/md10 on /mnt/disk10 type xfs (rw,noatime)
    /dev/md11 on /mnt/disk11 type xfs (rw,noatime)
    /dev/md12 on /mnt/disk12 type xfs (rw,noatime)
    /dev/md13 on /mnt/disk13 type xfs (rw,noatime)
    /dev/md14 on /mnt/disk14 type xfs (rw,noatime)
    /dev/md15 on /mnt/disk15 type xfs (rw,noatime)
    /dev/md16 on /mnt/disk16 type xfs (rw,noatime)
    /dev/sdd1 on /mnt/cache type btrfs (rw,noatime,space_cache=v2,discard=async)
    shfs on /mnt/user0 type fuse.shfs (rw,nosuid,nodev,noatime,allow_other)
    shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,noatime,allow_other)
    /dev/sdj1 on /mnt/disks/CCTV type xfs (rw,noatime,nodiratime)
    /mnt/cache/system/docker/docker.img on /var/lib/docker type btrfs (rw,noatime,space_cache=v2)
    /mnt/cache/system/libvirt/libvirt.img on /etc/libvirt type btrfs (rw,noatime,space_cache=v2)

  7. I am just enough to be dangerous with Linux and looks like the danger is real!

     

    I "vi" edited my GO file attempting to increase my log buffer from 128 to 384 and now I can't connect to my GUI after reboot. 

     

    I removed the inserted line:

    mount -o remount,size=384m /var/log

    I removed it 

     

    Here is the contents of my GO file:

    image.png.937e31b57be00cbbe4ba9ef050a0e0f8.png

    Any help would be appreciated.

×
×
  • Create New...