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

When using v6 you should not post syslogs. Always go to Tools - Diagnostics and post the complete diagnostics zip. The diagnostics zip includes your syslog, SMART for all disks, and many other useful things. Please save us the trouble of asking for this in the future.

 

Looks like you have a correcting parity check due to unclean shutdown.

 

I think your basic problem is your flash drive. Lots of errors related to it in the syslog. After the parity check put your flash in your PC and let it checkdisk.

 

Not sure what EXT4 has to do with anything. It is not a supported filesystem.

 

You are running an old version of unRAID. Please upgrade to the latest stable version.

 

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

Could also be a problem with the port your flash drive is on so in addition to checking the flash you might try another port.

 

Did you really have an unclean shutdown (powered down without stopping the array)? If not that could also be a symptom of the flash problem since unRAID stores the started/stopped state on the flash.

 

SMART for all disks looks OK.

 

14 hours is definitely excessive for a 2TB parity check. I usually get about that for 6TB. You might go ahead and cancel it, fix your other issues, then do parity check.

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...

You need to fix the problem with your flash before you try to upgrade, since the upgrade must be written to your flash.