Jump to content

kyis

Members
  • Posts

    44
  • Joined

  • Last visited

Posts posted by kyis

  1. Everything is working as intended on my end, but my setup probably wasn't accounted for:

     

    I have two WAN links/ public IPs, a fast link with a dynamic IP I'm unable to forward ports through (say 1.1.1.1), another slightly slower with a static IP I'm using as failover for the first link and to forward ports through (say 2.2.2.2), the plugin probably tested the default link to get my external IP and associate it (1.1.1.1) to my www.hash.unraid.com subdomain, except that's not the one I'm forwarding from.

    Is there any way I can manually override the external IP to set my inbound link (2.2.2.2 in my example) or more complex but probably more flexible, a list of IPs assigned in order to www./www1./www2. etc?

  2. Hi,

    My problem The top right log button loads an "about:blank" popup.

     

    Tested on Chrome, Edge, IE

    Output of cat /var/log/syslog is as expected.

    Nothing changes by disabling antivirus and adblocker.

    Running the following line outputs properly html formatted tail of syslog:

    /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

    Edit: When clicking the button I get this in syslog:

    Aug 10 19:09:31 Tower emhttpd: req (11): csrf_token=***************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog
    Aug 10 19:09:31 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog
    

    Opening other popups such as docker logs doesn't log anything, it seemed odd and worth mentioning. The "(11)" increments at each request.

     

    Edit2: The issue occurs with VM logs as well.

     

    Any help would be greatly appreciated.

  3. Same issue as xoddoza on a C2750D4I, I cleared my settings and reinstalled the plugin.

    Previously working board.json (its presence/absence in the ipmi folder doesn't seem to change anything):

    {
        "ASRockRack": {
            "raw": "00 3a 01",
            "auto": "00 00 00 00 00 00 00 00",
            "full": "64 64 64 64 64 64 64 64",
            "fans": {
                "CPU_FAN1": "00",
                "FAN_POS2": "00",
                "REAR_FAN1": "00",
                "FAN_POS4": "00",
                "FRNT_FAN1": "00",
                "FRNT_FAN2": "00",
                "FAN_POS7": "00",
                "FAN_POS8": "00"
            }
        }
    }

    Edit: I found that the fan.cfg file doesn't have anything for the board key,  from the code it looks like that would make the configuration fail but I've run out of time to look into where that file is generated and why everything is grayed in the ui. I'll keep looking later.

    FANCONTROL="disable"
    FANPOLL="3"
    FANIP=""
    IPMIBOARD=""

     

  4. @johnnie.black thanks, I know what I'm doing after work tomorrow. xD

    It'll be hell to reroute all the cables cleanly but I'll give the skirt a try, my idea was a bit more destructive, cutting 120mm holes in the side panel and putting 2 fans to pull air out so airflow would be forced through the HDD cage.

     

    Edit:

    Adding the skirt didn't change much, I assume the fans didn't have enough static pressure to begin with. Installing the PPC fans made a huge difference, they keep everything at 11°C above ambient when running at 30% with a huge margin if things start to heat up.

  5. @johnnie.black Yup that's why I'm fretting, I don't want to wait for winter to do parity checks. ^^

    I've got a DS380 case with 8 drives, that's a lot of drives in a tiny space and not a lot of cooling solutions. The new fans I ordered should ideally triple the airflow but even then I'm not sure it'll be enough. I have no way to control ambient temp, goes from 16°C in winter to 26°C in summer. If the new fans don't cut it, I'll be looking if I can contribute some code to do what I need and if it's beyond me I'll be cutting into the case to pull air through the HDD cage. B|

  6. @graywolf yup, 6TB drives take 14-16 hours to scan on my system, starting at 36°C,  6 hours in the scan I'm nearing 60°C on all 8 drives and if the mover is active all bets are off in terms of duration...

     

    In the meantime I ordered 3 industrial PPC fans, they do magic in my other rigs, I hope they'll improve cooling overall but I don't think they'll change anything for parity scans, it's too much heat too fast. :/

  7. +1 for this feature, I would love if scan throttling also responded to disks temp as well, my drives are running way too hot for comfort during scans on warmish days and I don't have room in the case for more fans (currently 3x120mm running 100% all the time), I'm at a point where I'm considering cutting into the side and front panels to add fans...

    My thinking is that the scan would pause when a disk goes above warning temp and resume when it's below minus a few degrees or a set value maybe.

    If the scan could pause for the mover it would avoid endless thrashing also.

    • Like 1
    • Upvote 1
  8. @wgstarks ok here is my version (under unRAID 6.3.2) and truncated columns list which includes SERIAL, I think this column is a requirement you may be stuck until you can update unRAID if it isn't supported by your version. If it has just been renamed maybe...

    root@BlackHole:~# lsblk -V
    lsblk from util-linux 2.28.2
    root@BlackHole:~# lsblk -h
    ...
    Available columns (for --output):
            NAME  device name
           KNAME  internal kernel device name
         MAJ:MIN  major:minor device number
          FSTYPE  filesystem type
      MOUNTPOINT  where the device is mounted
           LABEL  filesystem LABEL
            UUID  filesystem UUID
        PARTTYPE  partition type UUID
       PARTLABEL  partition LABEL
        PARTUUID  partition UUID
       PARTFLAGS  partition flags
              RA  read-ahead of the device
              RO  read-only device
              RM  removable device
         HOTPLUG  removable or hotplug device (usb, pcmcia, ...)
           MODEL  device identifier
          SERIAL  disk serial number
            SIZE  size of the device
           STATE  state of the device
           OWNER  user name
           GROUP  group name
            MODE  device node permissions
       ALIGNMENT  alignment offset
          MIN-IO  minimum I/O size
          OPT-IO  optimal I/O size
         PHY-SEC  physical sector size
         LOG-SEC  logical sector size
            ROTA  rotational device
           SCHED  I/O scheduler name
         RQ-SIZE  request queue size
            TYPE  device type
        DISC-ALN  discard alignment offset
       DISC-GRAN  discard granularity
        DISC-MAX  discard max bytes
       DISC-ZERO  discard zeroes data
           WSAME  write same max bytes
             WWN  unique storage identifier
            RAND  adds randomness
          PKNAME  internal parent kernel device name
            HCTL  Host:Channel:Target:Lun for SCSI
            TRAN  device transport type
      SUBSYSTEMS  de-duplicated chain of subsystems
             REV  device revision
          VENDOR  device vendor
    ...
    

     

  9. @wgstarks ok, typical output should be :

    NAME="sdf" TYPE="disk" LABEL="" SIZE="4000787030016" MOUNTPOINT="" FSTYPE="" SERIAL="WD-WCC4E1YTHK4R"
    NAME="sdf1" TYPE="part" LABEL="" SIZE="4000786980352" MOUNTPOINT="" FSTYPE="xfs" SERIAL=""
    NAME="sdd" TYPE="disk" LABEL="" SIZE="250059350016" MOUNTPOINT="" FSTYPE="" SERIAL="S2R6NX0HB36987T"
    NAME="sdd1" TYPE="part" LABEL="" SIZE="250059317248" MOUNTPOINT="" FSTYPE="btrfs" SERIAL=""
    NAME="md6" TYPE="md" LABEL="" SIZE="6001175072768" MOUNTPOINT="/mnt/disk6" FSTYPE="" SERIAL=""
    NAME="sdb" TYPE="disk" LABEL="" SIZE="6001175126016" MOUNTPOINT="" FSTYPE="" SERIAL="WD-WX11D76D3L8C"
    NAME="sdb1" TYPE="part" LABEL="" SIZE="6001175076352" MOUNTPOINT="" FSTYPE="xfs" SERIAL=""
    NAME="md4" TYPE="md" LABEL="" SIZE="4000786976768" MOUNTPOINT="/mnt/disk4" FSTYPE="" SERIAL=""
    NAME="sdk" TYPE="disk" LABEL="" SIZE="6001175126016" MOUNTPOINT="" FSTYPE="" SERIAL="WD-WX21DC5J246D"
    ...

    And lines where type is "disk" are used by php to populate the array your error says is null.

    Try running the command again but remove the "2>/dev/null" maybe it'll give you some useful error.

  10. 8 hours ago, trurl said:

    Have you done a memtest?

    That was the next step, I'm rerunning a clear before that to see if it was a fluck or if it consistently fails on just one write.

     

    Edit: Exact same result, 2MB not written or failed, can't tell. I won't upload the log, it's identical to the previous one.

    I wonder if it might be an "off by 1" kind of error somewhere in the math, 2MB is the value of the sb parameter of dd, it might be used somewhere else.

     

    Edit: Memtest done no errors... I'm stumped

     

    Edit: Finally caught what I was looking for, I edited the script so the -t option would run over 1TB and I monitored dd_output, I got this amongst the normal output:

    dd: warning: partial read (1126400 bytes); suggest iflag=fullblock

    Added the flag inside the function write_disk(), clearing and praying (already past the point where the message was showing up).

  11. Hi, can you please check this out : 

    It should have been posted here to begin with I guess. ^^

     

    Edit: Is there any way to increase verbosity on dd ? Looking at the script real quick it looks like all errors should be logged already but it's quite a large script/voodoo magic spell, I wouldn't want to edit anything half-assedly and screw with my data.

  12. You're fast ^^

     

    Fixed by opening flash/bzroot using 7zip

    Extracted /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php

    Connected via sftp to my machine (as root)

    Copied php file to /usr/local/emhttp/plugins/dynamix/include/

    Checked that permissions were 644

    Refreshed WebUI

    Works

     

    Since I know I can fix it, I tried reinstalling Local Master in hopes of it breaking again but I failed, it installed fine ^^.

  13. Could this be used to generate duplicates reports like same files in any folder, same folders (identical hash set), etc ?

     

    I figure since we're spending time computing hashes, might as well make use of them.  :P

×
×
  • Create New...