Posts by jensk

Aparently there were no solution to this problem. I reinstalled OMV6

II have upgraded OMV. I had version 3 and did a clean reinstall of OMV6.

I had everything up and running with no errors a week ago. Suddently yesterday morning the samba shares has stopped working.

I cannot commit changes to OMV - it throws a fault 500 at me.

NFS shares are functioning ok. I can access data from other hosts running Nextcloud and other.

But Samba is dead.

The error from OMV is in the enclosed file

If I run a journalctl -xe I get:
xxxx@yyyyyt:~# journalctl -xe

maj 09 17:35:58 openmediavault wsdd.py[4997]: WARNING: no interface given, using all interfaces

maj 09 17:35:58 openmediavault systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE

░░ Subject: Unit process exited

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ An ExecStart= process belonging to unit smbd.service has exited.

░░

░░ The process' exit code is 'exited' and its exit status is 1.

maj 09 17:35:58 openmediavault systemd[1]: smbd.service: Failed with result 'exit-code'.

░░ Subject: Unit failed

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ The unit smbd.service has entered the 'failed' state with result 'exit-code'.

maj 09 17:35:58 openmediavault systemd[1]: Failed to start Samba SMB Daemon.

░░ Subject: A start job for unit smbd.service has failed

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ A start job for unit smbd.service has finished with a failure.

░░

░░ The job identifier is 1801 and the job result is failed.

maj 09 17:35:58 openmediavault systemd[1]: Stopping Web Services Dynamic Discovery host daemon...

░░ Subject: A stop job for unit wsdd.service has begun execution

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ A stop job for unit wsdd.service has begun execution.

░░

░░ The job identifier is 1810.

maj 09 17:35:59 openmediavault systemd[1]: wsdd.service: Succeeded.

░░ Subject: Unit succeeded

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ The unit wsdd.service has successfully entered the 'dead' state.

maj 09 17:35:59 openmediavault systemd[1]: Stopped Web Services Dynamic Discovery host daemon.

░░ Subject: A stop job for unit wsdd.service has finished

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ A stop job for unit wsdd.service has finished.

░░

░░ The job identifier is 1810 and the job result is done.

Notice I have a data disk that is 85% full but this shouldn't matter.

How do I solve this and regain the possibility to commit changens to OMV?

Well if you have your timezone set correctly it should work including when the time changes for summertime soon. You can make sure that you are using the corect time by setting the -l parameter for local time and the -u parameter for universal time. To use your example:

rtcwake -m no -l -t $(date +%s -d 'Monday 04:00')

I have build a complete backup nas with OMV.

It is an old VIA C7 0.8Ghz with 1G ram and a 100Mb ethernet. It it used to be an old low power dekstop thing. I stripped it open and installed two 1Tb disks. The reason i chosed a rsyncing backup nas was the ease of using rsync from the backup nas to pull files of the productions nas. After the backup just power down and bring off site.

I use rsync for making backups.

I have made a small OMV-backup nas from a VIA C7 mobo and two 1tb disks.
This backup nas is configures to pull files of the production nas via rsync.
I normally take backup nas home the last working day of the month. Turn it on in the evening. It does it's job of rsyncing with production nas. Next morning it is finished and i turn backup nas off again. I take it with me to work to keep it offsite.

On second look it seems like your machine is in the proces of booting in the log entries from 2.03.38 and on. So it might have been shutdown but the -s parameter wasn't passed along correctly so it boots emediately after.

Still try to enter the rtcwake command ind the os crontab to se if rtcwake works there

For those os specific jobs i use cron from the root account login
Login via console/ssh to a root account

crontab -e

Insert your command

00 02 * * * rtcwake -m mem -s xxxxxx

then deactivate the cronjob that you have entered in the OMV gui
Try this and wait until tomorrow to se if it has been sleeping during night time

It seems like in the long run renewables are cheaper than nuclear. The Sweedes are about to decommision their oldest nuclear plants and now the costs for the decommision are beginning to show - and they are huge - very huge exspecially if you count in the storage of nuclear waste for many centuries.
The same is the case with the tender for a new nuclear plant in UK. The subsidy from the government for this nuclear plant is way above government subsidies to other forms of energi not counting burning fossils.

The only problem with the renewables are that we vill have to develop technolgies that enables us to store the energy between production and consumption. So it is more a matter of investing in getting the storage problem solved than a problem of having enough energi. If we solve the storage problem the earth recieves enough renewable energi from the sun to supply all mankind with energi forever for as long as the sun shines on the globe.

Are you sure the drive died?
Have you tried to change power and data cables as well as cahnge port on the controller to rule out the root cause of the error.

You can identify the faulty disk by looking up the active drive serial numbers under Storage - Phyical Disks. You can compare these serial number with the serial numbers on the labels on each disk.
The disk with a serial number that is not registered under Storage - Physical Disks is the one not connected. I say connected because until you have found the root cause of error it might be cables og controller/port as well as the disk.

I have had my Fit-pc2 turning on and of at specific times using rtcwake under ubuntu 12.04. You have the syntax right with

rtcwake -m mem -s <seconds_to_sleep>

I can't remember precisely how i did this but i know that one thing you have et set is that the bios is NOT set to use ACPI wake. I think the best thing to do is to reset bios to be sure old configuration errors in the bios isn't blocking rtcwake.

Next thing is be sure you do this as root or with "sudo"

You can test wheter the rtcwake command is setting your wakeup time by using the -m no parameter and then examine the rtc - like:

rtcwake -m no -t 600

This will set the wakeup time to 600 seconds from now
Then display the rtc wake paramters with:

cat /proc/driver/rtc

It should show alarmtime/date that is 10 minuters into the future UTC time - like:

....
rtc_time	: 08:09:32
rtc_date	: 2014-02-07
alrm_time	: 08:19:21
alrm_date	: 2014-02-07
alarm_IRQ	: yes
....

Note that you need to have the pc to use UTC time to be able to use rtcwake reliably.

Could you make the above test and se if the alrm_time is set. Also check that the rtc time reflects UTC time

To my knowledge you can't power/spin down USB harrdrives that are mounted in linux. If you wan't to spin down a usb harddrive under linux you will have to unmount it first.
Or
you can use the sg3-utils package for this. It can do to external drives what hdparm cannot.

apt-get install sg3-utils

issue:

sg3_start --pc=3 <disk_device_id>

like

sg3_start --pc=3 /dev/sdg

The --pc=3 parameter sets the disk in standby mode which the system should be able to wake the disk from when accessing it.
To get the system to set the disk ind standby mode on a regular basis you will have to put the command in a cron job with crontab -e

To se the actual mount options of nfs drives you should use the command:

cat /proc/mounts

As far as i know there should be no issue in OMV that should prevent your drives from starting up. Your error could be because the bios/controller on your mobo haven't implementet the power up from sleep commands in the disk protocol.

Another issue could be if you have old hdparm settings stored on the disks - In a console try
hdparm -I <drive> like:

hdparm -I /dev/sda

The last issue should be if your disks doesn't support power management.
Hdparm -I should list all the drive parameters. The command parameters with a star is the ones that are implemented. So if you do not have a start in the row with "Power Management feature set" then you're disks isn't supporting power down

It is faily straight forward mounting OMV NFS shares under Ubuntu.
First you need to have the NFS client parts installed on your Ubuntu desktop:

apt-get install nfs-common

After this you should be able to mount NFS shares from your OMV box by mounting them in fstab.

When sharing NFS from your OMV box use the parameters:

async,no_subtree_check,insecure,all_squash,anonuid=1002,anongid=100

where anonuid and anongid is the id of the user and group that should own the files

On the Ubuntu desktop edit /etc/fstab:

nano /etc/fstab

insert the NFS mount command:

OMV-ip:/nfssharename /localmountpoint_path_and_dir/ nfs4 auto,noatime,nodiratime,_netdev,hard,intr,tcp

The most common NFS problem is getting the rights owner and group rights for files stored on the OMV server. This is especially important if the same files also are accessed by SMB or other protocols. By using the anonuid og anongid parameters you can make sure that the NFS client connection sets the right parameters on the NFS host (OMV).

There are many parameters regarding NFS shares and nfs client connections. With NFS4 the above parameters gives the best performance and lets you bypass the usual owner/group problems. Many will set the wsize and rsize parameters to tune the perfomance of nfs over the network. With NFS 4 packet sizes are automatically set so only use the wsize and rsize parameters it you absolutely have to. you can view your actual parameters by issuing the mount command. My mounts automaticcally sets these paramaters:

<OMV_IP>:/<sharename> on /<localmountpoint> type nfs4 rw,noatime,nodiratime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=<client_ip>,minorversion=0,local_lock=none,addr=<OMV_IP>,_netdev)

I have been using ubuntu for years with nautilus to access smb shares. It works out-of-the-box if you are clicking network in the left menu. If you want permanent connection to shares I suggest setting up nfs shares and connecting to them in fstab. By using nfs you can maximize the throughput and minimize protocol overhead compared to smb.

The two drives are set up differently
/dev/sde has MultSect=off and *udma6
/dev/sdb has MultSect=16 and *udma5

You can use hdparm to set these parameters alike for the two drives.
In the console can type

hdparm /deb/sdb -X udma6

and

hdparm /dev/sde -m 16

This will set the same parameters for the /dev/sdb and the /dev/sde drives
If you want to make these settings persistent across boot you can put the commands into the end of the /etc/rc.local file right before the "exit 0" command

hdparm parameters: http://linux.die.net/man/8/hdparm

I would recommend kernel 3.2 or newer before using the system under KVM - both for the guest and for the host. I use kernel 3.2.4 for my host which is very stable.

Have you upgraded to a newer kernel on your host - like the raring og saucy kernel. This might help you getting the newest drivers for your network/mobo https://wiki.ubuntu.com/Kernel/LTSEnablementStack

There is a collections of howto and guides regarding many issues in Squeeze/OMV here http://forums.openmediavault.org/viewtopic.php?f=3&t=1289
The guide for using kernel 3.2.4 on Squeeze/OMV is here http://forums.openmediavault.o…ic.php?f=10&t=2258#p13821
There are newer kernels for OMV like 3.10.x but i haven't tried them as they are unsupported

Like you I would start using standard precise 12.04.3 kernel for the host and squeeze/OMV with backports kernel 3.2 on the guest. If you have driver or performance issues i would upograde the host to raring og saucy kernel - but only if there are performance or driver issues.

Regarding your network speed my best guess is that its the e1000 driver that slow everything down. If you change to virtio you will experience a substantial performance lift. To start you can test by just assigning one host interface (br0) through virtio.

For your networking in general i would recomment trunking all four interfaces on the hostlevel. Then I would assign the trunked network interface to the OMV guest through virtio. This way you would get the combined network throughput - like 4Gb/s - delivered on one interface to your guest.

Hi Torsten
Even though your stability prblems seem to be gone I think that you should tune your VM instalation to get the most stable installation. I have had my KVM based VMs Debian Wheezy and Ubuntu 12.04.2 running without a hickup for more than 6 months on my small AMD eE350 MB that is also running OMV.

Primarily I suggest that you use the device model: virtio for networking in stead of e1000

If you haven't then tune your elevator model for virtualisation in the guest VM by editing /etc/default/grub. In the line GRUB_COMMAND_LINE_DEFAULT insert

transparent_hugepage=always elevator=noop

The do a grub update

update-grub

You can do the same elevator tuning on the KVM host by editing /etc/default/grub. In the line GRUB_COMMAND_LINE_DEFAULT insert

transparent_hugepage=always elevator=deadline

The do a grub update

update-grub

There are more KVM tuning parameters. i have described some of the in my Howto KVM/qemu on OMV http://forums.openmediavault.org/viewtopic.php?f=13&t=2417. Even though you run OMV as a guest vm the same tuning parameters and stability meassures apply.

If you wan't to install OMV and have data on just one disk you need to follow this guide:
http://forums.openmediavault.o…opic.php?f=10&t=727#p4162

To secure my OwnCloud &OMV while giving external users access to OC i have installed OC on a virtual machine runnning on my OMV box. The OC virtual machine has it's own IP through a bridget interface on the OMV host. The OC servers Ip address is portforward in my router. No portforwarding of the OMV ip address

I have used my KVM howto to install OC as a VM:
http://forums.openmediavault.org/viewtopic.php?f=13&t=2417
The VM is an ordinary Wheeezy headless server with OC and iRedMail

To further enhance i have installed OC data dir outside the www-data path.
The OC VM accesses the personal OMV shares through NFS protocol. I can post the complete setup if you are interested.

I know that i through this setup looses some speed in OC but i have complete security separation between my public (OC & iRedMail) and my non-public (OMV) install.