Fireball3

Members
  • Posts

    1355
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Fireball3



  1. Just though I should mention that using the Parity Problems Assistant that is installed as part of the Parity Check Tuning plugin (under the Tools tab) it is possible to do this.    Not had any feedback as to whether users have successfully used it in practice and whether there are any suggestions for improving it.


    Thanks for the heads up!
    Obviously I missed some improvements since I didn't have to jump on every new release as my servers are doing well as they are now.
    In the meantime I'm increasingly following the principle: "never change a running system"
    Although, pausing the parity check, is a much anticipated feature that would fit my needs.



  2. If the hardware is performing optimally then it is irrelevant as you will not get a sync error.

    Of course you will and that's why the check is done. But it is expected to be only read errors on the drives. That was the reason why I joined unraid in the first place, after I found out that my drives we throwing read errors when lying on the shelf.


    We frequently see cases in the forum where a drive has started misbehaving for some reason and the user did not notice. By that time they may have corrupted parity badly enough to prejudice data recovery actions.

    I remember having had this discussion some years ago in this forum already. If this is a frequent and serious issue, shouldn't there be a better solution how to deal with sync errors?
    1. There should be no automatic correction
    2. There should be an easy way to inspect the potentially affected data
    3. The resync should be limited to the affected area without the need to run another 24h parity check

    Parity checks put the most stress on the system - at least on mine.


  3. It could be something obvious like an unclean shutdown but there are all sort of hardware errors (RAM. Power supply, drives) that could be occurring that triggered the errors.  You therefore want to be sure you are not currently having any hardware related issues that you know about before letting the system try to correct parity.

    Assuming the system has been properly commissioned and tested before taken into service, it's not reasonable to tear it apart everytime a sync error pops up.
    At some point one should be able to rely on what it shows - a sync error.
    That's why the correcting check is on by default and from my understanding there is still no commonly agreed recommendation that this should be done in another way.





  4. It is normally recommended that you set this to be non-correcting so you do not inadvertently corrupt parity if you have a drive acting up.   Then only run correcting checks manually as needed.


    Hi, sorry to hijack this topic but is this the commonly agreed procedure?
    If so, what is the recommended workflow to get everything straightened if there is a sync. error detected (and not corrected)?

  5. OK, weekend is approaching and I have to get the media server up and running again... 😓

    My plan is to setup a clean unRAID on the USB and copy the settings without the docker from the old install.

    Maybe I should skip the plugins also since they are giving errors in the syslog?

     

    So, what are the essential parts that I need to copy to the fresh install?

    super.dat

    license file

    ...

    ?

  6. Hi folks,

    I ran into this issue after installing the MiniDLNA docker.

    Probably didn't pay attention (took the presettings) with the settings of the docker.

    Now the server is running out of space on the rootfs when booting.

    The GUI is not available, SMB not running, array is not mounted.

    Luckily I can ssh in and see what's going on.

    When trying to grab a diagnostics I get this:

     

    root@Tower:~# diagnostics
    Starting diagnostics collection...
    Warning: file_put_contents(): Only 0 of 5 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 80
    Warning: file_put_contents(): Only 0 of 975 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85
    Warning: file_put_contents(): Only 0 of 78 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 101
    Warning: file_put_contents(): Only 0 of 2 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 120
    Warning: file_put_contents(): Only 0 of 34 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 122
    Warning: file_put_contents(): Only 0 of 2 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 120
    Warning: file_put_contents(): Only 0 of 34 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 122
    echo: write error: No space left on device
    echo: write error: No space left on device
    echo: write error: No space left on device
    echo: write error: No space left on device
    echo: write error: No space left on device
    echo: write error: No space left on device
    echo: write error: No space left on device
    echo: write error: No space left on device
    echo: write error: No space left on device
    
    Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
    Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
    Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
    Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
    Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
    Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
    Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
    Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
    Warning: file_put_contents(): Only 0 of 65 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 166
    Warning: file_put_contents(): Only 0 of 535 bytes written, possibly out of free disk space in 
    /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 210
    done.
    ZIP file '/boot/logs/tower-diagnostics-20210117-0922.zip' created.

    The diagnostic file contains only empty files.

     

    Checking for space:

    root@Tower:~# df -h
    Filesystem      Size  Used Avail Use% Mounted on
    rootfs          684M  684M     0 100% /
    tmpfs            32M  368K   32M   2% /run
    devtmpfs        684M     0  684M   0% /dev
    tmpfs           747M     0  747M   0% /dev/shm
    cgroup_root     8.0M     0  8.0M   0% /sys/fs/cgroup
    tmpfs           128M  140K  128M   1% /var/log
    /dev/sda       1003M  246M  758M  25% /boot
    /dev/loop0      9.2M  9.2M     0 100% /lib/modules
    /dev/loop1      7.3M  7.3M     0 100% /lib/firmware

     

    Is my assumption correct about the docker filling up the rootfs?

    That was the last thing I set up before this problem arose.

    How can I free up the space used by the docker?

     

    I checked the stick on a Windows machine for filesystem issues, but all is fine.

    I have teamviewer access only to the server. Safe boot and such things are not an option.

    I can ask the remote user to plug the stick into a Windows machine and change/modify content on the stick or

    do it via console.

    I would prefer not to set up a new config but remove the docker to free up space.

     

  7. that's the result of trim, when data is deleted from a modern SSD trim is used to tell the controller that those blocks are free and can be erased, the controller does that and marks those blocks / pages as zeroes. when you try to read from these blocks the ssd controller does not actually read the flash it just sends you zeroes as fast as it can. this is the reason ssd's used in the unraid parity array can not be used with trim since that will invalidate the parity.
     
    Just to make sure I understand it right. The flat line that basically indicates the max. interface throughput is trimmed (empty) space on the SSD?
  8. On 3/2/2019 at 2:46 PM, itimpi said:
    • Auto detect idle periods:  The idea is that instead of the user having to specify specific start/stop times for running parity check increments the plugin should automatically detect periods when the system is idle to resume a parity check.   This would need the complementary option of automatically detecting the system is no longer idle so that the check can be paused.
    • Partial parity Checks: This is just a different facet of the ability to Resume parity checks on array start where you deliberately set the system up to perform part of a parity check with reboots in between the parts.

    Those are the features I personally need most. 🤤

    Thanks for finally bringing this to life.

  9. On 6/23/2020 at 1:08 PM, GFRoSTY said:

    I

     

    I can second this find.

    I'm playing with a HP NL54 microserver.

    After installing the plugin it detects the correct sensors.

    Aufnahme2.png.66dffb3b54ba3c06c87285bbc62f54ab.png

     

    Assignment of sensors

    Aufnahme3.png.c928d8fde46e324edab382a9573bb01c.png

     

    Pressing "APPLY"

    Aufnahme5.png.f43bfb06c19f7aabec4db849be4aea80.png

    Of course, no sensor data is displayed.

     

    After deleting /etc/sensors.d/sensors.conf I can repeat the procedure. If the file is not deleted or modified like below, no chance to

    get the selection back.

     

    Initial sensors.conf

    root@Tower:~# cat /etc/sensors.d/sensors.conf
    # sensors
    chip "k10temp-pci-00c3"
    label "temp1" "CPU Temp"
    chip "w83795adg-i2c-1-2f"
    label "temp2" "MB Temp"
    chip "w83795adg-i2c-1-2f"
    label "fan1" "Array Fan"
    root@Tower:/etc/sensors.d# sensors
    Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced
    Error: File /etc/sensors.d/sensors.conf, line 6: Undeclared bus id referenced
    sensors_init: Can't parse bus name

     

    Deleted the sensors.conf and rescan. Sensors were back for selection in the GUI.

    Note, the K10 sensor disappeared...

    Pressed APPLY again and they were gone.

    I change the sensors.conf like this

    root@Tower:/etc/sensors.d# cat /etc/sensors.d/sensors.conf
    # sensors
    chip "w83795adg-i2c-12f"
    label "temp1" "CPU Temp"
    chip "w83795adg-i2c-12f"
    label "temp2" "MB Temp"
    chip "w83795adg-i2c-12f"
    label "fan1" "Array Fan"

     

    root@Tower:/etc/sensors.d# sensors
    Error: File /etc/sensors.d/sensors.conf, line 2: Parse error in chip name
    Error: File /etc/sensors.d/sensors.conf, line 4: Parse error in chip name
    Error: File /etc/sensors.d/sensors.conf, line 6: Parse error in chip name

    But the sensors reapear in the GUI.

    Of course there is no further benefit in having them back for selection, as long as they can't be saved and the temps are not displayed

    as intended.

     

    @bonienl Please let me know how I can contribute further to help debugging this issue.

     

    I also noticed this little spelling error in the mouseover.

    Aufnahme7.png.be27734ff37636b0a875089d733bc784.png



  10. Hello,
     

    I had some doubts on the chipset so I removed the heatsink, and noticed the thermal compound was completely dry and inefficient so I cleaned it and put a decent one. Here is the chip of the card : https://photos.app.goo.gl/NXBhBz2EtjHhnJie6
     
    Any idea on what I'm doing wrong ? Next step would be to return the card to the vendor (I asked him if he had any drivers or anything, but no)
     
    Thanks


    Is the PCB itself genuine LSI or a rebrand?
    For LSI you shouldn't need the workaround as for the rebranded cards.
    Have you tried the toolset I used for the Dell adapters?
    Should be linked in my signature. Ima posting this from my mobile so can't provide a link right now.
  11. The router will sent the magic packet and wake up the machine if it sees traffic dedicated for the server, but the NIC will have to do its job and listen for it.

    The router setting just takes over the wake-up task that you would need to perform by hand with a wake up command sent from PC or smartphone.

     

    Maybe on those server boards the WOL is done via the management interface? The support should be able to help.

     

     

     

    • Like 1
  12. The wake-up can not be performed by the plugin. The feature is called wake-on-lan aka. WOL and it must be configured in the BIOS if you use the on-board NIC. Check the manual of your board.

    If you use an add-on NIC the issue gets more sophisticated.

     

     

    • Like 1
  13. Your attempt to ping johnnie.black failed.   You have to begin typing, and then you have to actually make a selection from the matching choices. Just typing it won't work.

     

    @Fireball3

     

    VS

     

    @Fireball3

     

     

    @trurl I'm using Tapatalk here and I selected the name off the list that popped up but for reasons the link failed!?But I see there is a difference once the post is online.

     

    Edit:

    Once edited, the link gets fixed...

    Just edit and save without any modification.

     

     

     

     

     

     

     

  14. I suppose one of your 4TB drives is parity at the moment.
    The new drive is bigger than your current drives, so it will have to be the new parity drive. The parity needs to be at least as big as your biggest data drive.
    I'm not sure how the preclear is handled in recent versions. Maybe @johnnie.black can help here?

    For the Plex thing you should read up on how to use docker containers and see if that works for you.
    IIRC there is also a install package on the Plex site if you want to go that way.

    Sorry for the global answers, but I'm travelling at the moment and can't provide links as I'm writing this on my mobile.

    Gesendet von meinem Mi 9 SE mit Tapatalk

  15. Hi,

    welcome to the unRAID forums.

    If you didn't know by now, writing everything in CAPITAL letters is considered as SHOUTING to others.

     

    Now we have 3 possibilities on the receiver side:

    1. You are not sure about your orthography skills and go all capital. ^_^ 

    2. Your caps-lock has been unintentionally stuck.

    3. You are intentionally shouting at us. :/

     

    Please elaborate.

     

  16. Yes, it is allowed as long as it's not excessive and the first disaster happened some years ago.

    By that time webmail access was still allowed and somebody launched one of those encrypting malwares that he received on his private mail.  It started encrypting shares on the server :S...

    Webmail is blocked since.

  17. As I mentioned, this is the company machine.

    I don't know what the IT guys configured in detail. I see the whole "security" tab is missing in my options and a notice

    says that some settings are controlled by the sysadmin.

     

    They prevent the use of other browsers than IE and Edge. >:(

     

  18. Yes, I have set the same settings.

     

    Edit:

    Checked it to be 100% sure...

    The setting to "Delete browser history" does NOT remove temporary files.

    Check yourself, go to

    "C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\" and you will find lots of files in \Content.IE5\ and \Ie\.

    I don't trust that setting and run a batch to delete the files.

     

    Still, logs me in, even if all is deleted.