fnwc

Members
  • Posts

    57
  • Joined

  • Last visited

Posts posted by fnwc

  1. On 5/6/2020 at 7:15 AM, Aceriz said:

    I have tried a reinstall with no luck to fix.. Have you had any luck getting it working again 

    Not sure if this is the issue you're having but it has to do with existing session data at least in the x64 version of Duplicati.

     

    When in the web UI, for Chrome, right click "inspect" go to the "Application" and click the "Clear Site Data" button then reload.

    • Like 1
    • Thanks 2
  2. Does anyone have any idea if there is some kind of HDD mount for 3.5" drives that doesn't mount in a drive bay?

     

    I'm using an Antec Twelve Hundred with an mATX motherboard (E3C246D4U), so there is some space where a full ATX motherboard would fit. I need to mount an internal 3.5" but all of my drive slots for the front drive bays are taken by three 5-in-1 drive cages, so there is no more space there.

     

    I'm going to put a 3.5" drive for access outside of the array for torrents using a docker, I think using an external USB is probably asking for trouble, so I want to have a direct SATA connection.

     

    I need to mount the 3.5" drive somewhere, I don't think it's a good idea to just let it float in the case. Does anyone know if there are drive cages you could mount say, on the server chassis where the full ATX case would extend?

  3. I'm having some issues with my unRAID samba and web UI becoming unresponsive after about 12 hours of uptime. However, I can still login to the machine locally, and I was able to recover the syslog (attached).

     

    There seems to be some kind of memory issue, but I can't seem to figure out what's the offending process.

     

    Can anyone take a look?

    syslog

  4. Hi, 

     

    My unraid (v6.7.2) server, which has been running well until the other day, it completely stopped responding. I attempted to reboot it and it would sometimes get stuck on the "loading bzroot" stage. Other times it would seeming throw an exception. I have no idea what the green blocks on the monitor are:

     

    IMG-4811.thumb.jpg.d38873792d3140cc72c4261c1e3aacd1.jpgIMG-4818.thumb.jpg.d65dbc3d148fbf3e5ddcfc71460868cb.jpg

     

    I've tried a couple of things:

     

    • Ran memtest, passed
    • Copied a known backup flash copy from a month ago that I know works (v6.7.2)
    • I'm using an old MobileLite G2, I replaced the card with a new Sandisk Extreme PLUS 32GB SDHC
    • Replaced the MobileLite with a Sandisk Cruzer Glide 32GB
    • Tried downloading and 6.8.2 clean format, copying my config from my known "good" copy
    • Tried downloading and 6.8.2 clean format, copying my config from my known "good" copy, only selective files/folders:
    • 298805887_2-21-20208-53-03PM.thumb.png.b84072ea5a0b196f1412ade8da430efa.png

     

     

    Sometimes it will actually boot to the login screen, but it soon throws some kind of exception.

     

    Since the entire OS becomes unresponsive, how would I track down the log of this? I need to get a diagnostic, but IIRC unraid stores logs in memory, which doesn't help me here.

     

    Next I might just try a completely fresh 6.8.2 install, but I don't want to have to recreate all of my settings from scratch... (Edit: just did this and it still faulted out -- seemingly there is a hardware error somewhere, but how can I figure out what's wrong)?

     

    Any thoughts?

     

     

  5. I'm trying to set up the CA Backup for my Docker and my various containers.

     

    • Docker vDisk location: /mnt/cache/docker.img
    • Default appdata storage location: /mnt/user/appdata/

     

    Can someone explain how to set up the CA Backup settings? Current settings:

     

    • Appdata Share (Source): /mnt/cache
    • Destination Share: /mnt/user/CA Backup

     

    I assume I need to backup both directories in order to save all my docker data. I think I've set it up correctly for the vDisk location, how can I setup a separate backup for the appdata storage location? 

     

    I'm basically trying to ensure my Plex DB and configuration on my docker are backed up in case of data loss.

  6. No VM's and Dockers. 

     

    Running an ECS A88GM-A2 motherboard, AMD Sempron 145 @ 2.8 GHz

     

    8 GB Memory (4 x 2GB)

     

    Plugins are:

     

    CA Auto Update Applications

    CA Backup / Restore Appdata

    Community Applications

    Dynamix Active Streams

    Dynamix Cache Directories

    Dynamix S3 Sleep

    Dynamix System Information

    Dynamix System Statistics

    Fix Common Problems

    Nerd Tools

    Network Statistics

    Preclear Disks

    User Scripts

     

  7. Question: I had a disk fail due to uncorrectable writes. The disk was then taken out of the array and the contents emulated.

     

    I put in a new disk and started rebuilding the array, but I'm wondering if the file copy that caused the write error would be ok or not. In other words, can I trust the parity to be correct in being able to reconstruct the missing data correctly, or should I assume whatever file(s) failed to copy are corrupt?

  8. My parity drive is 4TB.

     

    I'm trying to figure out how I can force unraid to accept a drive and start without having it try to rebuild that drive from parity (since I'm pretty sure parity is invalid right now).

     

    Once I have the drive accepted (since the data is still "good" on it), I can rebuild parity correctly with the accepted drive.

     

    I'm wondering if the "trust my array" procedure is the correct way to accomplish this.

  9. Hi,

     

    I recently tried to upgrade a 1.5 TB drive to 4.0 TB drive, but something bad happened when trying to rebuild the replaced disk with existing parity (no drives past the replaced drive showed up on simple features and the unraid main page wouldn't load).

     

    I had to reset the server, which then on reboot, caused a parity check with correct to begin.

     

    I still have the old disk, however, so I'm pretty sure that my parity is bad, but all of the data disks are 'good'.

     

    Right now, I've put the old "good" 1.5 TB drive back in, but it isn't assigned and the slot is red balled because it's expecting the 4 TB drive.

     

    I "think" that I need re-assign the old 1.5 TB drive and run the trust my array procedure to get the array to accept the old drive back and rebuild parity based on the existing data. I want to make sure that I don't overwrite my existing data before I've had a chance to correct the parity drive.

     

    It also looks like there are changes to the "trust my array" procedure for 5.0. Is there anything specific that I should be careful about?

     

    Thanks in advance!

  10. for i in /etc/rc.d/rc.avahi* ;do :>$i ;done

    I don't have any Macs on my network, so I guess I don't need avahi.

    However, this didn't seem to do anything (avahi still spammed the syslog).

    Did you put the above line in your "go" script, and then reboot?

    If so, then the avahi daemon will not be started at boot, so how can it still spam your syslog?

     

    I don't know what to tell you, but it didn't work. I edited "/boot/config/go" and added the line above and rebooted. After reboot, I'm still seeing the messages.

     

    The other fix worked, though. Thanks for that.

  11. That can't happen.  syslogd is NOT writing to the flash drive. (unless you've modified its config to do so on purpose).  In v.5, the syslog is in a size-limited tmpfs in RAM.  So nothing bad will happen as a result of its growing.  It will just stop growing once it reaches a certain size (128MB?  grep /var/log /proc/mounts).  That may take a very long time though.

    I'm a little confused. I see a file "/var/log/syslog" that grows... am I not looking in the right place?

    You are looking in the right place.  What are you confused about?

     

    Well, since "/var/log/syslog" resides on the flash drive, I was confused that you were saying that syslogd doesn't write to the flash drive. Maybe I'm mistaken about where "/var/log/syslog" actually sits -- I don't really know much about linux.

     

    The syslog priority levels, in ascending order are: debug, info, notice, warning, error, emerg.

    Stock unRAID uses the highest log level -- debug -- logs everything.

     

    So you could lower the log level with something like this:

    mv /etc/syslog.conf /etc/syslog.conf.bak
    echo '*.info	-/var/log/syslog' >/etc/syslog.conf
    /etc/rc.d/rc.syslog restart
    

    Is the syslog still getting spammed? If yes, try lowering some more:

    echo '*.notice	-/var/log/syslog' >/etc/syslog.conf
    /etc/rc.d/rc.syslog restart
    

    ...etc.

     

    While the above may help you, it is still better to deal with the offending program's settings (avahi-daemon?), rather than messing with the syslogd conf settings.

     

    Ok thanks, I'll look into that. I'm basically using stock unRaid with the latest unmenu (which doesn't have anything to do with this avahi spam, AFAIK), so the avahi-daemon message is coming from the unraid package, which is what I'm trying to solve.

     

    Thanks for your help. I'll see if I can reduce the logging.