This is super weird but I'm seeing this error with a Seagate IronWolf 110 SATA SSD without any USB
Beiträge von magixx
-
-
The mod in the original post has been doing fine for me for the past ~8 months on a Sandisk Cruzer 4GB and 4GB RAM. I did have an issue in the past such that I am missing status logs for a large period of time and web-ui update seemed to not work but I seem to have solved that today by setting my apt source to wheezy and doing a dist-upgrade. I'll probably upgrade to Arch on my fancy SLC usb drive once I get bored enough or this setup dies.
-
Thanks, this seems to have fixed everything. For some reason I did not need to chown as it was already properly set, I only needed to chmod the settings file. Even stranger only some of the torrents were in the same state, I just had to verify them and everything was back to normal.
-
I went to the Reset Permissions tab and hit reset permissions for all my file systems/labels (d1,d2,d3,d4) not clearing ACL. Set transmission umask to 777. This made transmission not able to create files. I tried resetting the permissions again. I then tried setting an inconsequential transmission setting in order to save all setting since reset wasn't working.
Now transmission won't work at all. In trying to reset transmission I'm getting:
"Failed to execute command 'export LANG=C; invoke-rc.d 'transmission-daemon' start 2>&1': Starting bittorrent daemon: transmission-daemon[13:54:46.192] Couldn't read "/var/lib/transmission-daemon/info/settings.json": Permission denied (warning). invoke-rc.d: initscript transmission-daemon, action "start" failed." -
I'm currently using an aufs pool and transmission and cannot seem to be able to get proper rights to any directories/files that transmission creates. Transmission saves on an aufs pool and I'm accessing files from there. Under shares I've checked Privilages for my user/group to read/write.
I've done the same for ACL, and I have done this for all drives/poolshares yet I still cannot delete/copy to transmission created files/folders.
I've added myself to debian-transmission group and I still cannot edit those files.
Whenever I reapply the privilages I will be able to edit the current files, but once again I cannot edit any future created ones.
What am I doing wrong? -
Gave this a try, seems to not have caused problems, although symlinking did give an error about /etc/mtab not existing I believe.
Will see how long this lasts on a very mediocre 4GB usb which was used as a ubuntu disk for a while, in the meantime I placed an order for an 8GB SLC USB from aliexpress ($11). -
So I've set up a new openmediavault box and some plugins, however I am getting consistent crashes around every hour or so when I'm migrating data. My setup is OMV + aufs plugin + transmission and I am sharing the aufs pool and writing both my files and having transmission save on the pool. The odd thing is that everything seems to die (webui, SMB, transmission) however if I go to the PC I can login as root:password and it works (using admin:password just brings up the login again). I tried looking though the logs but can notice anything really repeating.
EDIT: This may even be a networking error where for some reason the connection is dropped, need to look into this further, restarting the networking service did not work though on first trial.Here is an example of a syslog a bit before the crash (happens at around ~10:11), the crash, then me logging as root and doing sudo reboot:
Code
Alles anzeigenNov 30 22:00:01 qube-store /USR/SBIN/CRON[3641]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1) Nov 30 22:00:01 qube-store rrdcached[2307]: Received FLUSHALL Nov 30 22:09:01 qube-store /USR/SBIN/CRON[3866]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)) Nov 30 22:11:41 qube-store kernel: [ 4475.108583] r8169 0000:02:00.0: eth0: link up Nov 30 22:13:11 qube-store kernel: [ 4565.776721] r8169 0000:02:00.0: eth0: link up Nov 30 22:13:13 qube-store shutdown[3929]: shutting down for system reboot Nov 30 22:13:13 qube-store init: Switching to runlevel: 6 Nov 30 22:13:14 qube-store monit[2442]: Shutting down monit HTTP server Nov 30 22:13:14 qube-store watchdog[2477]: stopping daemon (5.12) Nov 30 22:13:14 qube-store monit[2442]: monit HTTP server stopped Nov 30 22:13:14 qube-store monit[2442]: monit daemon with pid [2442] killed Nov 30 22:13:14 qube-store monit[2442]: 'localhost' Monit stopped Nov 30 22:13:19 qube-store wd_keepalive[3965]: starting watchdog keepalive daemon (5.12): Nov 30 22:13:19 qube-store wd_keepalive[3965]: int=10 alive=/dev/watchdog realtime=yes Nov 30 22:13:19 qube-store wd_keepalive[3965]: hardware wartchdog identity: Software Watchdog Nov 30 22:13:19 qube-store wd_keepalive[3965]: unable to disable oom handling! Nov 30 22:13:19 qube-store avahi-daemon[2373]: Got SIGTERM, quitting. Nov 30 22:13:19 qube-store collectd[2326]: Exiting normally. Nov 30 22:13:19 qube-store collectd[2326]: collectd: Stopping 5 read threads. Nov 30 22:13:19 qube-store rrdcached[2307]: caught SIGTERM Nov 30 22:13:19 qube-store rrdcached[2307]: starting shutdown Nov 30 22:13:19 qube-store avahi-daemon[2373]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.3.113. Nov 30 22:13:20 qube-store avahi-daemon[2373]: avahi-daemon 0.6.31 exiting. Nov 30 22:13:20 qube-store rrdcached[2307]: clean shutdown; all RRDs flushed Nov 30 22:13:20 qube-store rrdcached[2307]: removing journals Nov 30 22:13:20 qube-store rrdcached[2307]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1417399044.511545 Nov 30 22:13:20 qube-store rrdcached[2307]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1417402644.512710 Nov 30 22:13:20 qube-store rrdcached[2307]: goodbye Nov 30 22:13:27 qube-store acpid: exiting Nov 30 22:13:27 qube-store wd_keepalive[3965]: stopping watchdog keepalive daemon (5.12) Nov 30 22:14:26 qube-store kernel: imklog 5.8.11, log source = /proc/kmsg started. Nov 30 22:14:26 qube-store rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2168" x-info="http://www.rsyslog.com"] start Nov 30 22:14:26 qube-store kernel: [ 0.000000] Initializing cgroup subsys cpuset Nov 30 22:14:26 qube-store kernel: [ 0.000000] Initializing cgroup subsys cpu Nov 30 22:14:26 qube-store kernel: [ 0.000000] Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.63-2+deb7u1 Nov 30 22:14:26 qube-store kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=af7cd085-289c-4575-80dc-5715c685ada7 ro quiet Nov 30 22:14:26 qube-store kernel: [ 0.000000] BIOS-provided physical RAM map:It then decides to die again at ~10:30 for some reason, at which point I hit restart button.
Code
Alles anzeigenNov 30 22:14:33 qube-store monit[2421]: State file '/var/lib/monit/state': Unable to read magic Nov 30 22:14:38 qube-store watchdog[2456]: starting daemon (5.12): Nov 30 22:14:38 qube-store watchdog[2456]: int=1s realtime=yes sync=no soft=no mla=0 mem=0 Nov 30 22:14:38 qube-store watchdog[2456]: ping: no machine to check Nov 30 22:14:38 qube-store watchdog[2456]: file: no file to check Nov 30 22:14:38 qube-store watchdog[2456]: pidfile: no server process to check Nov 30 22:14:38 qube-store watchdog[2456]: interface: no interface to check Nov 30 22:14:38 qube-store watchdog[2456]: test=none(0) repair=none(0) alive=/dev/watchdog heartbeat=none temp=none to=root no_act=no Nov 30 22:14:38 qube-store watchdog[2456]: hardware wartchdog identity: Software Watchdog Nov 30 22:15:01 qube-store /USR/SBIN/CRON[2557]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1) Nov 30 22:15:01 qube-store rrdcached[2218]: Received FLUSHALL Nov 30 22:15:03 qube-store monit[2421]: Starting monit HTTP server at [localhost:2812] Nov 30 22:15:03 qube-store monit[2421]: monit HTTP server started Nov 30 22:15:03 qube-store monit[2421]: 'localhost' Monit started Nov 30 22:17:01 qube-store /USR/SBIN/CRON[2685]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 30 22:17:01 qube-store postfix/postsuper[2688]: fatal: scan_dir_push: open directory hold: No such file or directory Nov 30 22:29:43 qube-store kernel: [ 934.292408] r8169 0000:02:00.0: eth0: link up Nov 30 22:30:01 qube-store /USR/SBIN/CRON[3381]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1) Nov 30 22:30:01 qube-store rrdcached[2218]: Received FLUSHALL Nov 30 22:33:38 qube-store kernel: imklog 5.8.11, log source = /proc/kmsg started. Nov 30 22:33:38 qube-store rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2454" x-info="http://www.rsyslog.com"] start Nov 30 22:33:38 qube-store kernel: [ 0.000000] Initializing cgroup subsys cpuset Nov 30 22:33:38 qube-store kernel: [ 0.000000] Initializing cgroup subsys cpu Nov 30 22:33:38 qube-store kernel: [ 0.000000] Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.63-2+deb7u1 Nov 30 22:33:38 qube-store kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=af7cd085-289c-4575-80dc-5715c685ada7 ro quiet Nov 30 22:33:38 qube-store kernel: [ 0.000000] BIOS-provided physical RAM map:
Here is a more complete log of the most recent crash:
http://pastebin.com/hYet99FhAnd full log here:
https://drive.google.com/file/…HUGdSU3M/view?usp=sharingEDIT1: Going to attempt disabling transmission and see if that does anything.
EDIT1.5: This did nothing, crashed about 5 minutes later thus interrupting the file transfer once more.
EDIT2: Set static IP outside DHCP, didn't seem to make a difference, upgraded kernel and left it on overnight powered on, it did not disconnect during this time. Back to transferring files from windows machine, will need to see if it continues to disconnect.