Posts by fumantsu
-
-
Today, I had different error message:
/etc/cron.weekly/openmediavault-update-smart-drivedb:Updating smartmontools drive database .../tmp/tmp.mCC69edTik: download from trunk failed (HTTP error)
Internet was working for sure (email...)
-
From time to time I'm getting this errors on the smartmontools email (not always)
/etc/cron.weekly/openmediavault-update-smart-drivedb:Updating smartmontools drive database ...grep: /usr/share/smartmontools/drivedb.h.new: No such file or directorycmp: EOF on /usr/share/smartmontools/drivedb.h.new/usr/share/smartmontools/drivedb.h updated from branches/RELEASE_5_41_DRIVEDB
I wonder if there is something to do to fix it.
-
The cron file is installed by default by the mdadm Debian package. Delete the cron job file if you do not want it.
I check that there are two crons for mdadm. One is "mdadm" and one is "openmediavault-mdadm"
-
What is the output of:
cat /etc/mdadm/mdadm.conf
fdisk -lCode
Display More# mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is # used if no RAID devices are configured. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> # definitions of existing MD arrays Disk /dev/sdc: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/sdc doesn't contain a valid partition table Disk /dev/sde: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0xad28ad28 Device Boot Start End Blocks Id System Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/sdb doesn't contain a valid partition table Disk /dev/sdd: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0xad91ad91 Device Boot Start End Blocks Id System Disk /dev/sda: 32.0 GB, 32017047552 bytes 255 heads, 63 sectors/track, 3892 cylinders, total 62533296 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000589d9 Device Boot Start End Blocks Id System /dev/sda1 1 23439359 11719679+ 83 Linux /dev/sda2 23439360 31250431 3905536 82 Linux swap / Solaris WARNING: GPT (GUID Partition Table) detected on '/dev/zd0'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/zd0: 343.6 GB, 343597383680 bytes 256 heads, 63 sectors/track, 41610 cylinders, total 671088640 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 8192 bytes I/O size (minimum/optimal): 8192 bytes / 8192 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/zd0p1 1 671088639 335544319+ ee GPT Partition 1 does not start on physical sector boundary. Disk /dev/zd0p1: 343.6 GB, 343596318208 bytes 16 heads, 63 sectors/track, 665760 cylinders, total 671086559 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 8192 bytes I/O size (minimum/optimal): 8192 bytes / 8192 bytes Disk identifier: 0x00000000 Disk /dev/zd0p1 doesn't contain a valid partition table # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is # used if no RAID devices are configured. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> # definitions of existing MD arrays# mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is # used if no RAID devices are configured. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> # definitions of existing MD arrays# mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is # used if no RAID devices are configured. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> # definitions of existing MD arrays
-
Why should not be compatible? If you want to have it as boot disk more possible is to have compatibility issues with your MB than with the OS.
-
Good day,
I notice that from the moment that upgrade to 2.0 I have started to receive cron emails about mdadm.
/etc/cron.daily/mdadm:mdadm: No mail address or alert command - not monitoring.run-parts: /etc/cron.daily/mdadm exited with return code 1
The funny is that I don't have mdadm working (I use ZFS) and I don't have enable the software RAID in the notifications. I tried to enable/disable again but no luck.
-
-
Good day,
Any guide how to correctly setup this plugin? I'm not so familiar with syslinux and basically I need to test pxe boot for Windows 7 and 8 (I'm aware from other guides that I need to setup some PE iso images)
-
Really I don't know. I know about the grive how it works because I installed as normal program. It only needs once to authenticate with the google by a generated hash.
-
I vote for dropbox but I would like to see a Google drive plugin based on grive or something else. The only issue of grive is that it not push client and needs to run to sychronize the file/directories but at least it does the job.
-
Also... wrong topic?
-
I like very much the approach. Very fresh, very different. I believe that can be more mobile friendly also. When you are ready for beta, count me.
-
Good day,
I'm try to create some users and to have them their own home directory. According the wiki on settings:
Enable: select to specify a that a specific location of user home directories should be used. If not set users home directories are created in the data root.From this I understand that if I not set a location it will be created on / (which is normal). The problem is that the field is mandatory. I can't just leave it like this and I need to specify some shared folder. It is some kind of bug or I don't understand it well?
EDIT: I notice that when I create a new user the home directory is not created even if is mention on the /etc/passwd.
-
You had right. It was sensors module (I haven't follow the thread for a while to catch a newer version). I just uninstall it and the tab is working again. Normal situations with testing/alpha plugins. Thanks a lot for all the help.
-
Question: this tab what is reading? startup services or GUI services?
root@NASBox:/home/fumantsu# grep "OMVIModuleServiceStatus" /usr/share/openmediavault/engined/module/*
/usr/share/openmediavault/engined/module/nfs.inc: implements OMVINotifyListener, OMVIModuleServiceStatus, OMVIModuleZeroconf {
/usr/share/openmediavault/engined/module/plexmediaserver.inc: implements OMVINotifyListener, OMVIModuleServiceStatus {
/usr/share/openmediavault/engined/module/proftpd.inc: implements OMVINotifyListener, OMVIModuleServiceStatus, OMVIModuleZeroconf {
/usr/share/openmediavault/engined/module/pyload.inc: OMVIModuleServiceStatus
/usr/share/openmediavault/engined/module/rsyncd.inc: implements OMVINotifyListener, OMVIModuleServiceStatus, OMVIModuleZeroconf {
/usr/share/openmediavault/engined/module/samba.inc: implements OMVINotifyListener, OMVIModuleServiceStatus, OMVIModuleZeroconf {
/usr/share/openmediavault/engined/module/sensors.inc: OMVIModuleServiceStatus
/usr/share/openmediavault/engined/module/snmp.inc: implements OMVINotifyListener, OMVIModuleServiceStatus {
/usr/share/openmediavault/engined/module/ssh.inc: implements OMVINotifyListener, OMVIModuleServiceStatus, OMVIModuleZeroconf {
/usr/share/openmediavault/engined/module/tftp.inc: implements OMVINotifyListener, OMVIModuleServiceStatus, OMVIModuleZeroconf {
/usr/share/openmediavault/engined/module/virtualbox.inc: OMVIModuleServiceStatus -
root@NASBox:/home/fumantsu# ls -al /usr/share/openmediavault/engined/module/
total 232
drwxr-xr-x 2 root root 4096 Jan 8 18:36 .
drwxr-xr-x 5 root root 4096 Nov 29 15:04 ..
-rw-r--r-- 1 root root 2458 Jan 4 16:51 acpid.inc
-rw-r--r-- 1 root root 1745 Jan 4 16:51 apt.inc
-rw-r--r-- 1 root root 1836 Jan 4 16:51 certificatemgmt.inc
-rw-r--r-- 1 root root 2624 Jan 4 16:51 collectd.inc
-rw-r--r-- 1 root root 2773 Jan 4 16:51 cpufrequtils.inc
-rw-r--r-- 1 root root 2379 Jan 4 16:51 cron-apt.inc
-rw-r--r-- 1 root root 2633 Jan 4 16:51 cron.inc
-rw-r--r-- 1 root root 1600 Dec 9 17:55 downloader.inc
-rw-r--r-- 1 root root 5057 Jan 4 16:51 fstab.inc
-rw-r--r-- 1 root root 1993 Jan 4 16:51 halt.inc
-rw-r--r-- 1 root root 1961 Jan 4 16:51 hdparm.inc
-rw-r--r-- 1 root root 2081 Jan 4 16:51 hostname.inc
-rw-r--r-- 1 root root 1768 Jan 4 16:51 hosts.inc
-rw-r--r-- 1 root root 2927 Jan 4 16:51 interfaces.inc
-rw-r--r-- 1 root root 2147 Jan 4 16:51 iptables.inc
-rw-r--r-- 1 root root 2538 Jan 4 16:51 mdadm.inc
-rwxr-xr-x 1 root root 3199 Jan 4 16:51 monit.inc
-rw-r--r-- 1 root root 1749 Jan 4 16:51 networking.inc
-rwxr-xr-x 1 root root 3593 Nov 26 15:06 networkroute.inc
-rwxr-xr-x 1 root root 4652 Jan 4 16:51 nfs.inc
-rw-r--r-- 1 root root 2094 Dec 12 13:12 nginx-server.inc
-rw-r--r-- 1 root root 2420 Jan 4 16:51 ntp.inc
-rw-r--r-- 1 root root 2500 Dec 13 20:20 omvextrasorg.inc
-rw-r--r-- 1 root root 1500 Jan 4 16:51 pam.inc
-rw-r--r-- 1 root root 1935 Jan 4 16:51 php5fpm.inc
-rw-r--r-- 1 root root 2534 Dec 12 13:12 phpfpm-server.inc
-rw-r--r-- 1 root root 3560 Dec 13 23:51 plexmediaserver.inc
-rw-r--r-- 1 root root 2786 Jan 4 16:51 postfix.inc
-rwxr-xr-x 1 root root 7139 Jan 4 16:51 proftpd.inc
-rw-r--r-- 1 root root 3047 Dec 12 14:03 pyload.inc
-rw-r--r-- 1 root root 2659 Jan 4 16:51 quota.inc
-rwxr-xr-x 1 root root 5059 Jan 4 16:51 rsyncd.inc
-rwxr-xr-x 1 root root 3397 Jan 4 16:51 rsync.inc
-rwxr-xr-x 1 root root 10875 Jan 4 16:51 samba.inc
-rw-r--r-- 1 root root 2405 Sep 22 20:57 sensors.inc
-rwxr-xr-x 1 root root 4150 Jan 4 16:51 smartmontools.inc
-rwxr-xr-x 1 root root 3169 Jan 4 16:51 snmp.inc
-rwxr-xr-x 1 root root 4260 Jan 4 16:51 ssh.inc
-rw-r--r-- 1 root root 1808 Jan 4 16:51 sysctl.inc
-rwxr-xr-x 1 root root 1956 Jan 4 16:51 syslog.inc
-rwxr-xr-x 1 root root 4086 Jan 4 16:51 tftp.inc
-rw-r--r-- 1 root root 1769 Jan 4 16:51 timezone.inc
-rwxr-xr-x 1 root root 2710 Jan 1 2014 usbbackup.inc
-rw-r--r-- 1 root root 4733 Dec 12 13:29 virtualbox.inc
-rw-r--r-- 1 root root 1796 Jan 4 16:51 webadmin.inc
-rw-r--r-- 1 root root 3070 Jan 4 16:51 webserver.inc
-rwxr-xr-x 1 root root 2113 Jan 4 16:51 zeroconf.inc
root@NASBox:/home/fumantsu# apt-get --purge remove openmediavault-processlist
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'openmediavault-processlist' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@NASBox:/home/fumantsu# apt-get --purge remove openmediavault-supportinfo
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'openmediavault-supportinfo' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.For the purge I was pretty sure that nothing will happen as apt-get can't clean something that is not installed. From the other hand supportinfo can't be reinstalled (to make the purge trick)
-
I don't remember....
-
I went but probably it didn't like. I tried again and here is the new output:
omv-engined[22022]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22022) terminated with exit code 0
omv-engined[22021]: RPC response (service=Services, method=getStatus): {"response":{"total":11,"data":[{"name":"ftp","title":"FTP","enabled":false,"running":false},{"name":"nfs","title":"NFS","enabled":false,"running":false},{"name":"PlexMediaServer","title":"PlexMediaServer","enabled":true,"running":true},{"name":"pyload","title":"PyLoad","enabled":true,"running":false},{"name":"rsyncd","title":"RSync server","enabled":false,"running":false},{"name":"samba","title":"SMB\/CIFS","enabled":true,"running":true},null,{"name":"snmp","title":"SNMP","enabled":false,"running":false},{"name":"ssh","title":"SSH","enabled":true,"running":true},{"name":"tftp","title":"TFTP","enabled":false,"running":false},{"name":"virtualbox","title":"VirtualBox WebService","enabled":true,"running":false}]},"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22021) terminated with exit code 0
omv-engined[22223]: Child process forked (pid=22223)
omv-engined[22223]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22223]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22223) terminated with exit code 0
omv-engined[22228]: Child process forked (pid=22228)
omv-engined[22228]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22228]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22228) terminated with exit code 0
omv-engined[22229]: Child process forked (pid=22229)
omv-engined[22229]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22229]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22229) terminated with exit code 0
omv-engined[22230]: Child process forked (pid=22230)
omv-engined[22230]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22230]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22230) terminated with exit code 0
omv-engined[22233]: Child process forked (pid=22233)
omv-engined[22233]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22233]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22233) terminated with exit code 0
omv-engined[22234]: Child process forked (pid=22234)
omv-engined[22234]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22234]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22234) terminated with exit code 0
omv-engined[22235]: Child process forked (pid=22235)
omv-engined[22235]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22235]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22235) terminated with exit code 0
omv-engined[22238]: Child process forked (pid=22238)
omv-engined[22238]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22238]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22238) terminated with exit code 0
omv-engined[22241]: Child process forked (pid=22241)
omv-engined[22241]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22241]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22241) terminated with exit code 0
omv-engined[22242]: Child process forked (pid=22242)
omv-engined[22242]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22242]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22242) terminated with exit code 0
omv-engined[22245]: Child process forked (pid=22245)
omv-engined[22245]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22245]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22245) terminated with exit code 0
omv-engined[22250]: Child process forked (pid=22250)
omv-engined[22250]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22250]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22250) terminated with exit code 0
omv-engined[22253]: Child process forked (pid=22253)
omv-engined[22253]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22253]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22253) terminated with exit code 0
omv-engined[22254]: Child process forked (pid=22254)
omv-engined[22254]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22254]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
omv-engined[10757]: SIGCHLD received ...
omv-engined[10757]: Child (pid=22254) terminated with exit code 0
omv-engined[22255]: Child process forked (pid=22255)
omv-engined[22255]: Executing RPC (service=Config, method=isDirty, params=null, context={"username":"admin","role":1}) ...
omv-engined[22255]: RPC response (service=Config, method=isDirty): {"response":false,"error":null}
.... -
for a small quick test Mobile Chrome proved adequate. For the sake of discussion I tested in one other PC (chrome again).
The output:
omv-engined[7891]: SIGCHLD received ...
omv-engined[7891]: Child (pid=9658) terminated with exit code 0
omv-engined[9857]: Child process forked (pid=9857)
omv-engined[9858]: Child process forked (pid=9858)
omv-engined[9857]: Executing RPC (service=Config, method=isDirty, params=null, c ontext={"username":"admin","role":1}) ...
omv-engined[9857]: RPC response (service=Config, method=isDirty): {"response":fa lse,"error":null}
omv-engined[9858]: Executing RPC (service=System, method=getInformation, params= [], context={"username":"admin","role":1}) ...
omv-engined[7891]: SIGCHLD received ...
omv-engined[7891]: Child (pid=9857) terminated with exit code 0
omv-engined[9858]: RPC response (service=System, method=getInformation): {"respo nse":[{"name":"Hostname","value":"NASBox.mylan.local","type":"string","index":0} ,{"name":"Version","value":"1.9 (Kralizec)","type":"string","index":1},{"name":" Processor","value":"Intel(R) Atom(TM) CPU C2550 @ 2.41GHz","type":"string","in dex":2},{"name":"Kernel","value":"Linux 3.16.0-0.bpo.4-amd64","type":"string","i ndex":3},{"name":"System time","value":"Thu 08 Jan 2015 08:28:41 PM CET","type": "string","index":4},{"name":"Uptime","value":"7 days 2 hours 43 minutes 13 secon ds","type":"string","index":5},{"name":"Load average","value":"0.79, 0.43, 0.28" ,"type":"string","index":6},{"name":"CPU usage","value":{"text":"27%","value":27 },"type":"progress","index":7},{"name":"Memory usage","value":{"text":"51% of 7. 78 GiB","value":51},"type":"progress","index":8}],"error":null}
omv-engined[7891]: SIGCHLD received ...
omv-engined[7891]: Child (pid=9858) terminated with exit code 0
omv-engined[9869]: Child process forked (pid=9869)
omv-engined[9870]: Child process forked (pid=9870)
omv-engined[9869]: Executing RPC (service=Config, method=isDirty, params=null, c ontext={"username":"admin","role":1}) ...
omv-engined[9869]: RPC response (service=Config, method=isDirty): {"response":fa lse,"error":null}
omv-engined[9870]: Executing RPC (service=System, method=getInformation, params= [], context={"username":"admin","role":1}) ...
omv-engined[7891]: SIGCHLD received ...It is the same again and again...