Jump to content

foerl

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by foerl

  1. first of all, thanks for all your great guides! they're well explained and easy to follow. :)

     

    i was following your guide until the point where i set up port forwarding - i went to my subdomain (using my own website) and it shows my unraid dashboard instead of nextcloud! i used my mobile network to verify - i now disabled port forwarding because that's something i don#t want lol... 

     

    what did i miss, what went wrong? any help would be greatly appreciated! 

  2. When i try to spin down the drives to shut down the server i get this:

     

    Stopping Docker...Stopping libvirt...Stop AVAHI...Stop AFP...Stop SMB...Spinning up all drives...Sync filesystems...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...Retry unmounting user share(s)...

     

    + it says EXT4-fs error (device loop1): ext4_put_super:781: Couldn't clean up journal

     

    chkdsk was ok on the usb stick, but i get the same error on both usb ports i use for this... :(

  3. sorry, i must've misread that part about uploading the diag file! i've included the right one now. :)

     

    parity check takes 14 hours now... last time it took 4...

     

    i tried to update to 6.1.9 from 6.1.6 but got this error:

     

    plugin: updating: unRAIDServer.plg

    plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.1.9-x86_64.zip ... done

    plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.1.9-x86_64.md5 ... done

    Archive: /tmp/unRAIDServer.zip

    inflating: /tmp/unRAIDServer/bzimage

    inflating: /tmp/unRAIDServer/bzroot

    inflating: /tmp/unRAIDServer/changes.txt

    creating: /tmp/unRAIDServer/config/

    extracting: /tmp/unRAIDServer/config/go

    inflating: /tmp/unRAIDServer/config/network.cfg

    inflating: /tmp/unRAIDServer/config/ident.cfg

    creating: /tmp/unRAIDServer/config/plugins/

    creating: /tmp/unRAIDServer/config/plugins/dockerMan/

    extracting: /tmp/unRAIDServer/config/plugins/dockerMan/template-repos

    inflating: /tmp/unRAIDServer/install.txt

    inflating: /tmp/unRAIDServer/license.txt

    inflating: /tmp/unRAIDServer/make_bootable.bat

    inflating: /tmp/unRAIDServer/make_bootable_mac

    inflating: /tmp/unRAIDServer/memtest

    creating: /tmp/unRAIDServer/syslinux/

    inflating: /tmp/unRAIDServer/syslinux/menu.c32

    inflating: /tmp/unRAIDServer/syslinux/ldlinux.c32

    inflating: /tmp/unRAIDServer/syslinux/syslinux.cfg-

    inflating: /tmp/unRAIDServer/syslinux/mbr.bin

    inflating: /tmp/unRAIDServer/syslinux/mboot.c32

    inflating: /tmp/unRAIDServer/syslinux/syslinux.cfg

    inflating: /tmp/unRAIDServer/syslinux/syslinux.exe

    inflating: /tmp/unRAIDServer/syslinux/syslinux

    inflating: /tmp/unRAIDServer/syslinux/libutil.c32

    inflating: /tmp/unRAIDServer/syslinux/libcom32.c32

    inflating: /tmp/unRAIDServer/syslinux/make_bootable_mac.sh

    flash write error 0, maybe corrupted?

    plugin: run failed: /bin/bash retval: 1

    tower-diagnostics-20160912-2124.zip

  4. i recently changed from a cheap pentium processor to a xeon 1231v3 to get some vms going but when i try to install a vm i get the read-only filesystem error.

     

    Tower login: EXT4-fs error (device loop1): ext4_journal_check_start :56: >Detected aborted journal

    EXT4-fs (loop1): Remounting filesystem read-only

    sed: couldn't open temporary file /boot/config/sedLqpGbz: Read-only file system

    and so on...

     

    Please help!

    tower-syslog-20160912-1901.zip

×
×
  • Create New...