sota

Members
 View Profile  See their activity

  • Posts

    691

  • Joined

 Content Type 

Posts posted by sota

    SYSLOG stopped populating

    in General Support

    Posted

    (was going to post this as a question, but since it's now resolved, i'm posting as a documentation of my journey.)

     

    This has been an on going problem for a long time for me, but i'm just now able to deal with it.

     

    /var/log/syslog no longer populates.

    as such http://server/logging.htm never populates.

     

    if I delete the /var/log/syslog file, I get...

    /usr/bin/tail: cannot open '/var/log/syslog' for reading: No such file or directory
    /usr/bin/tail: no files remaining

    and it never recreates the files.

     

    tmpfs           128M   18M  111M  14% /var/log

    so I have plenty of space.

     

    /etc/rc.d/rc.rsyslogd restart does no good.

    restarting the machine does no good.

     

    finally tried this... 

     

     

    deleting the file AND rebooting appears to have solved it for me.

    deleting the file AND ONLY restarting the service does not work.

    not sure what background process(es) are also affected, but I figured I'd post this as how it worked for me.

    recreating partial old array and recovering dead drive from parity...

    in General Support

    Posted · Edited by sota

    UNRAID 6.9.2

     

    long story short, had 2 drives in a 6+1 array die (one of which was parity).

    Since I needed to get the box working RIGHT NOW, I yanked all 7 disks, build a new system, copied everything I could from the working drives, and set these disks to the side.

    Now, I'm trying to see if I can't recover something extra.

     

    Parity "failed", but with some effort on my part (HDD REGEN tool) I got it back and working, for now.

    that leaves 6 data disks. 5 of them work.

    I want to try and recreate the array, and somehow get it to rebuild the data from the 6th drive.

    What steps do i need to take to convince a trial version of UNRAID that this array is a valid, but 1 disk is listed as "missing", so I can force the rebuild to a replacement when I add it in?

    I know which drives are which (thank god for good note taking!)

    I stupidly did NOT save a copy of the CONFIG before blowing the original box up, so that's on me.

     

    I'm sure there's details i'm missing that needed providing, so just let me know and I'll do my best to gather that info.

    thanks!

    Cache drive's and trim support

    in General Support

    Posted

    fstrim -v /mnt/cache
    /mnt/cache: 444 GiB (476746616832 bytes) trimmed

     

    that's on a 500GB SSD with 6.9.2 running.  we've had performance issues on the system recently, and when I copied the VMs off the drive, it was barely moving data.  then I ran the command above.

    something tells me it's not TRIMming the drive like its supposed to.

    e1000e Detected Hardware Unit Hang

    in General Support

    Posted 

    Apr 21 23:14:44 Tigger kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
Apr 21 23:14:44 Tigger kernel:  TDH                  <2d>
Apr 21 23:14:44 Tigger kernel:  TDT                  <44>
Apr 21 23:14:44 Tigger kernel:  next_to_use          <44>
Apr 21 23:14:44 Tigger kernel:  next_to_clean        <2c>
Apr 21 23:14:44 Tigger kernel: buffer_info[next_to_clean]:
Apr 21 23:14:44 Tigger kernel:  time_stamp           <13a8c3651>
Apr 21 23:14:44 Tigger kernel:  next_to_watch        <2d>
Apr 21 23:14:44 Tigger kernel:  jiffies              <13a8c3f00>
Apr 21 23:14:44 Tigger kernel:  next_to_watch.status <0>
Apr 21 23:14:44 Tigger kernel: MAC Status             <80083>
Apr 21 23:14:44 Tigger kernel: PHY Status             <796d>
Apr 21 23:14:44 Tigger kernel: PHY 1000BASE-T Status  <3800>
Apr 21 23:14:44 Tigger kernel: PHY Extended Status    <3000>
Apr 21 23:14:44 Tigger kernel: PCI Status             <10>
Apr 21 23:14:46 Tigger kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
Apr 21 23:14:46 Tigger kernel:  TDH                  <2d>
Apr 21 23:14:46 Tigger kernel:  TDT                  <44>
Apr 21 23:14:46 Tigger kernel:  next_to_use          <44>
Apr 21 23:14:46 Tigger kernel:  next_to_clean        <2c>
Apr 21 23:14:46 Tigger kernel: buffer_info[next_to_clean]:
Apr 21 23:14:46 Tigger kernel:  time_stamp           <13a8c3651>
Apr 21 23:14:46 Tigger kernel:  next_to_watch        <2d>
Apr 21 23:14:46 Tigger kernel:  jiffies              <13a8c46c0>
Apr 21 23:14:46 Tigger kernel:  next_to_watch.status <0>
Apr 21 23:14:46 Tigger kernel: MAC Status             <80083>
Apr 21 23:14:46 Tigger kernel: PHY Status             <796d>
Apr 21 23:14:46 Tigger kernel: PHY 1000BASE-T Status  <3800>
Apr 21 23:14:46 Tigger kernel: PHY Extended Status    <3000>
Apr 21 23:14:46 Tigger kernel: PCI Status             <10>
Apr 21 23:14:48 Tigger kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
Apr 21 23:14:48 Tigger kernel:  TDH                  <2d>
Apr 21 23:14:48 Tigger kernel:  TDT                  <44>
Apr 21 23:14:48 Tigger kernel:  next_to_use          <44>
Apr 21 23:14:48 Tigger kernel:  next_to_clean        <2c>
Apr 21 23:14:48 Tigger kernel: buffer_info[next_to_clean]:
Apr 21 23:14:48 Tigger kernel:  time_stamp           <13a8c3651>
Apr 21 23:14:48 Tigger kernel:  next_to_watch        <2d>
Apr 21 23:14:48 Tigger kernel:  jiffies              <13a8c4ec0>
Apr 21 23:14:48 Tigger kernel:  next_to_watch.status <0>
Apr 21 23:14:48 Tigger kernel: MAC Status             <80083>
Apr 21 23:14:48 Tigger kernel: PHY Status             <796d>
Apr 21 23:14:48 Tigger kernel: PHY 1000BASE-T Status  <3800>
Apr 21 23:14:48 Tigger kernel: PHY Extended Status    <3000>
Apr 21 23:14:48 Tigger kernel: PCI Status             <10>
Apr 21 23:14:49 Tigger kernel: e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly
Apr 21 23:14:50 Tigger kernel: bond0: (slave eth0): link status definitely down, disabling slave
Apr 21 23:14:50 Tigger kernel: device eth0 left promiscuous mode
Apr 21 23:14:50 Tigger kernel: bond0: now running without any active interface!
Apr 21 23:14:50 Tigger kernel: br0: port 1(bond0) entered disabled state
Apr 21 23:14:53 Tigger kernel: e1000e 0000:00:19.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Apr 21 23:14:53 Tigger kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex
Apr 21 23:14:53 Tigger kernel: bond0: (slave eth0): making interface the new active one
Apr 21 23:14:53 Tigger kernel: device eth0 entered promiscuous mode
Apr 21 23:14:53 Tigger kernel: bond0: active interface up!
Apr 21 23:14:53 Tigger kernel: br0: port 1(bond0) entered blocking state
Apr 21 23:14:53 Tigger kernel: br0: port 1(bond0) entered forwarding state

     

    Started having this problem recently.  Not physically at the machine right now, but does this look like a faulty card, bad port on the switch, or a bad cable?  Or, something else software related.

     

    Machine is basically a glorified file cabinet, running a single Windows 7 x64 VM for SageTV (haven't gotten the docker to work to my liking, and i'm under a time crunch with a failing physical SageTV server and a 4/25 "hard" cut over date for Cablevision switching to encrypted.)

    Everything seemed to be working fine until a couple days ago, when while I was remoted into the VM (anydesk) I kept and keep getting disconnected.  Finally tried to watch the log, only to discover /var/log was full.  I caught the above after the most recent disconnect.

     

    diagnostics and syslog.1 are attached.

    syslog.zip tigger-diagnostics-20220421-2322.zip

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted · Edited by sota

    5 hours ago, dlandon said:

    The php warning doesn't make any sense because that is not the file UD is referencing in the settings page.  The warning doesn't prevent UD from working and can be ignored for now.  I'll do some more research and see if I can make sense of it.

    I'd appreciate it, as the warning does prevent UD from working.

    image.thumb.png.44ca91f06d4f5ceab1afd12cca38635d.png

     

    image.thumb.png.136429e9be8864aae525aa08aafa9e14.png

     

    note: i just got a notification of a new version. applying it now.

    eta: applied 2022.04.20 update. now it appears to be working again.

    unable to create VMs. v6.9.2 Emulator does not support virt type 'kvm'

    in VM Engine (KVM)

    Posted · Edited by sota

    unsupported configuration: Emulator '/usr/local/sbin/qemu' does not support virt type 'kvm'

     

    HP Z420 workstation

    Hewlett-Packard 1589, Version 0.00
    Hewlett-Packard, Version J61 v03.96
    BIOS dated: Tue 29 Oct 2019 12:00:00 AM EDT

    Intel® Xeon® CPU E5-1660 @ 3.30GHz

     

    build is pretty virgin/plain, so no idea what's wrong.

    BIOS settings are set to allow virtualization.

     

    thanks!

     

    ETA: nevermind, i'm an idiot.  they moved the VT-X function to the Security -> System Security tab, instead of bundling it with the rest of the CPU settings.

    [SOLVED] EXECUTION ERROR: SERVER ERROR on all my docker containers

    in Docker Engine

    Posted

    Would like to note:

    Same issue for me after a restart after 131 days (trying to sort out another problem.)

    Immediately had a problem starting any containers.

    Found this thread, #commented out the noted line (for now), restarted.  Containers are starting again.

     

    While i'm glad this fixed it, can I get some info as to what/why this happened?  AKA, did I miss an announcement someplace?

    Thanks!

    [Support] spaceinvaderone - Shinobi Pro

    in Docker Containers

    Posted

    Anyone have any suggestions for something "dumber" than shinobi?

    I've decided it's too tempermental for my needs.

    I just need to dump the live stream from multiple cameras, to separate folders, broken up in 5 minute increments.

    I can live without the 'timelapse' image option, as it's problematic at best, and I can create post processed.

     

    I don't need any of the fancy that shinobi provides, as I use the native app to my cameras to view them in real-time, or I go look at the MP4 files directly.