Jump to content

BRiT

Members
  • Content Count

    5447
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by BRiT

  1. BRiT

    Ver: 4.5.6 upgrade to 6.6 help

    Is your hardware even 64bit capable?
  2. BRiT

    Unraid OS version 6.7.0-rc3 available

    And that is why some folks no longer bother to reply to threads with varioous items to try.
  3. BRiT

    [Plugin] CA User Scripts

    Fully specify the config location.
  4. Not sure if anyone has tried the 9305-16i or 9400-16i, if they need or want Pcie 3.0 or nvme.
  5. BRiT

    New Emby Docker

    Post in the emby forums. They likely have better support for that specific situation.
  6. This certainly would be nice.
  7. BRiT

    New Emby Docker

    Of course not. I'm a Lazy Dev. I forget that not many folks around this forum is aware of that knee-jerk reaction joke. It shows up all the time on the graphical/game related forums. Frankly, developers' time is better spent developing than it is documenting, unless it's a fundamental breaking change that requires manual steps to adjust.
  8. BRiT

    New Emby Docker

    Lazy Devs.
  9. BRiT

    HGST Drives, what happened to them

    They were still out there a year ago when I was shopping around, but they seem to be harder to find at more typical retail and even some online shops.
  10. BRiT

    Unraid OS version 6.7.0-rc2 available

    No. I did not forget that RC does not mean Release Candidate here. Other's have. That's why I asked why they don't ask for features.
  11. BRiT

    Unraid OS version 6.7.0-rc2 available

    Why? It's not like RC(s) here mean feature freeze that goes along with Release Candidate.
  12. BRiT

    Memory keeps getting MAXED

    https://www.linuxatemyram.com/
  13. And bad news for all existing mb owners ... I'm fine (accepting there's nothing I can do now) just ignoring the temps for monitoring and just spot checking since I know its setup fine.
  14. I don't see anything that's not expected from the process/syslogs. At the time of the diagnostics capture it shows you have 2 "rsync" processing running that's causing the load from the "unbalance" plugin. nobody 15606 0.4 0.1 110180 14136 ? Sl 11:04 0:18 /usr/local/emhttp/plugins/unbalance/unbalance -port 6237 nobody 27569 21.4 0.0 20164 3308 ? D 12:03 0:39 \_ /usr/bin/rsync -avPR -X Video/Action Cam /mnt/disk2/ nobody 27570 0.0 0.0 19556 2556 ? S 12:03 0:00 \_ /usr/bin/rsync -avPR -X Video/Action Cam /mnt/disk2/ nobody 27571 15.3 0.0 19996 2384 ? S 12:03 0:28 \_ /usr/bin/rsync -avPR -X Video/Action Cam /mnt/disk2/ From your SMARTS on your cache drive(s), I'm not sure if the RAW value has any meaning for SSDs, but for most spinners, it does for field 187. Do you have a lot of power outages? If not, perhaps your power plane for the cache drives needs to be corrected. The larger ones report a number of "unexpected power loss" as well. Model Family: SandForce Driven SSDs Device Model: SanDisk SDSSDA240G Serial Number: 154836404031 LU WWN Device Id: 5 001b44 f188d033f Firmware Version: Z22000RL User Capacity: 240,057,409,536 bytes [240 GB] 174 Unexpect_Power_Loss_Ct -O--CK 100 100 000 - 24 187 Reported_Uncorrect -O--CK 100 100 000 - 5872 0x04 0x008 4 5872 --- Number of Reported Uncorrectable Errors --- Model Family: SandForce Driven SSDs Device Model: SanDisk SDSSDA240G Serial Number: 161337404732 LU WWN Device Id: 5 001b44 4a4758b33 Firmware Version: Z22000RL User Capacity: 240,057,409,536 bytes [240 GB] 174 Unexpect_Power_Loss_Ct -O--CK 100 100 000 - 16 187 Reported_Uncorrect -O--CK 100 100 000 - 2 0x000a 2 4 Device-to-host register FISes sent due to a COMRESET SMART Extended Comprehensive Error Log Version: 1 (1 sectors) Device Error Count: 1 CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 [0] log entry is empty SMART Extended Self-test Log Version: 1 (1 sectors) No self-tests have been logged. [To run self-tests, use: smartctl -t] --- Model Family: SandForce Driven SSDs Device Model: TS64GSSD320 Serial Number: A2910611949538650037 LU WWN Device Id: 0 0232d0 000000000 Firmware Version: 5.0.2 User Capacity: 64,023,257,088 bytes [64.0 GB] 174 Unexpect_Power_Loss_Ct ----CK 000 000 000 - 122 0x0009 2 1 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 1 Device-to-host register FISes sent due to a COMRESET
  15. Try using a usb2 port instead.
  16. BRiT

    ZFS filesystem support

    The pressure needs to be on Oracle (current owners of Sun Microsystems IP) to get them to change the license terms on ZFS. Not until the terms are adjusted will you see the attitude towards it from Linux Kernal developers change.
  17. BRiT

    Device Missing following power failure

    That missing drive doesnt seem to show up in your syslog at all nor in the device list. Have you tried shutting down and doing a power cycle? Also recheck the power cables on the drives. [0:0:0:0] disk Kingston DataTraveler 3.0 /dev/sda /dev/sg0 state=running queue_depth=1 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/0:0:0:0 [/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/host0/target0:0:0/0:0:0:0] [3:0:0:0] disk ATA Samsung SSD 850 3B6Q /dev/sdb /dev/sg1 state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/3:0:0:0 [/sys/devices/pci0000:00/0000:00:1f.2/ata3/host3/target3:0:0/3:0:0:0] [8:0:0:0] disk ATA ST4000DM004-2CV1 0001 /dev/sdc /dev/sg2 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/8:0:0:0 [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:0/end_device-8:0/target8:0:0/8:0:0:0] [8:0:1:0] disk ATA WDC WD20EARS-22M AB51 /dev/sdd /dev/sg3 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/8:0:1:0 [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:1/end_device-8:1/target8:0:1/8:0:1:0] [8:0:2:0] disk ATA ST4000DM004-2CV1 0001 /dev/sde /dev/sg4 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/8:0:2:0 [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:2/end_device-8:2/target8:0:2/8:0:2:0] [8:0:3:0] disk ATA ST4000DM004-2CV1 0001 /dev/sdf /dev/sg5 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/8:0:3:0 [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:3/end_device-8:3/target8:0:3/8:0:3:0] [8:0:4:0] disk ATA ST4000DM000-1F21 CC54 /dev/sdg /dev/sg6 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/8:0:4:0 [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:4/end_device-8:4/target8:0:4/8:0:4:0] [8:0:5:0] disk ATA ST4000DM005-2DP1 0001 /dev/sdh /dev/sg7 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/8:0:5:0 [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:5/end_device-8:5/target8:0:5/8:0:5:0] [8:0:6:0] disk ATA ST4000DM005-2DP1 0001 /dev/sdj /dev/sg9 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/8:0:6:0 [/sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host8/port-8:6/end_device-8:6/target8:0:6/8:0:6:0] [9:0:0:0] disk ATA ST8000DM004-2CX1 0001 /dev/sdi /dev/sg8 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/9:0:0:0 [/sys/devices/pci0000:00/0000:00:03.0/0000:06:00.0/host9/port-9:0/end_device-9:0/target9:0:0/9:0:0:0] [9:0:2:0] disk ATA ST4000DM004-2CV1 0001 /dev/sdk /dev/sg10 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/9:0:2:0 [/sys/devices/pci0000:00/0000:00:03.0/0000:06:00.0/host9/port-9:2/end_device-9:2/target9:0:2/9:0:2:0] [9:0:3:0] disk ATA ST4000DM004-2CV1 0001 /dev/sdl /dev/sg11 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/9:0:3:0 [/sys/devices/pci0000:00/0000:00:03.0/0000:06:00.0/host9/port-9:3/end_device-9:3/target9:0:3/9:0:3:0] [9:0:4:0] disk ATA ST4000DM004-2CV1 0001 /dev/sdm /dev/sg12 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/9:0:4:0 [/sys/devices/pci0000:00/0000:00:03.0/0000:06:00.0/host9/port-9:4/end_device-9:4/target9:0:4/9:0:4:0] [9:0:5:0] disk ATA ST4000DM004-2CV1 0001 /dev/sdn /dev/sg13 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/9:0:5:0 [/sys/devices/pci0000:00/0000:00:03.0/0000:06:00.0/host9/port-9:5/end_device-9:5/target9:0:5/9:0:5:0]
  18. BRiT

    How to unzip and zip bzroot

    The lines dealing with extraction, since bzroot has 2 sections you need to deal with first part and then skip that section to get to the last part: echo -e " ----- Extract BZROOT microcode" dd if=/boot/bzroot bs=512 count=$(cpio -ivt -H newc < /boot/bzroot 2>&1 > /dev/null | awk '{print $1}') of=bzrootmicrocode echo -e "----- Unpack BZROOT" dd if=/boot/bzroot bs=512 skip=$(cpio -ivt -H newc < /boot/bzroot 2>&1 > /dev/null | awk '{print $1}') | xzcat | cpio -i -d -H newc --no-absolute-filenames
  19. BRiT

    Dynamix - V6 Plugins

    Maybe 6.7.0 addresses the issue of impossible updates.
  20. BRiT

    Ryzan and current OS

    Did you update your motherboard BIOS. Most hangs on Ryzen are caused by out of date BIOS or incorrect ram timings.
  21. BRiT

    ZFS filesystem support

    I suggest others re-read the above concern before handwaveing it away as a non-issue. (Copied it because it was well expressed)
  22. BRiT

    6.7RC coming? [PIC]

    No.
  23. BRiT

    CPU pinned at 100%