Beiträge von Deckma

Hello,

I'm encountering a non-fatal error message when quick wiping a hard drive in OMV via the WebUI. The error message I receive is below:

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; blockdev --rereadpt '/dev/sde' 2>&1' with exit code '1': blockdev: ioctl error on BLKRRPART
: Device or resource busy

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; blockdev --rereadpt '/dev/sde' 2>&1' with exit code '1': blockdev: ioctl error on BLKRRPART
: Device or resource busy in /usr/share/openmediavault/engined/rpc/diskmgmt.inc:312
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(628): Engined\Rpc\DiskMgmt->Engined\Rpc\{closure}()
#1 /usr/share/openmediavault/engined/rpc/diskmgmt.inc(244): OMV\Rpc\ServiceAbstract->execBgProc()
#2 [internal function]: Engined\Rpc\DiskMgmt->wipe()
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array()
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()
#5 /usr/sbin/omv-engined(544): OMV\Rpc\Rpc::call()
#6 {main}

What I am doing is slowly growing my existing 8 drive RAID6 array using the multiple device plugin via replacing each drive with a bigger one.

1. Remove a drive from the the array via the MD plugin of OMV
2. Turn off my PC
3. Replace the old drive with a bigger drive
4. Turn back on my system
5. Log back into OMV 7 WebUI
6. Go to Storage > Disks, select the newly installed bigger disk and select wipe and select quick wipe. This is when I get the error message. I have reproduced this error message every time I have replaced one of my drives.

One thing I also noticed is that I am unable to select my newly wiped drive and use it to recover the array until I reboot OMV. MD will say the newly wiped drive is "busy". I have to reboot OMV to clear the issue, then I am able to go into Multiple Devices, select the new drive and start the recovery of the array. The recovery works fine.

I have repeated the above process 3 times now, each time I get the same error message. Thankfully I am still able to recover my array and everything works fine. I don't understand why I am getting this error message and how to prevent it.

I am running:

• OMV 7.7.9-1
• Plugins: openmediavualt-backup 7.1.4, openmediavault-md 7.0.5-1, openmediavault-omvextrasorg 7.0.2, openmediavault-resetperms 7.1

Zitat von macom

My backup function doesn't look like that in 4.x. I still only see shared folder, root device, extra options. I don't have the option to change the Method. Am I using the wrong plugin?

Problem solved. I accidentally scheduled two cron jobs for SnapRAID that runs at same time.

I upgraded from 3.x to 4.x recently and just received a warning email from OMV about the status of SnapRAID. It says the following:

Cron <root@nas2> /var/lib/openmediavault/cron.d/userdefined-5f6fd87f-bd21-48a6-bde1-4a14016699e0 | mail -E -s "Cron - SnapRAID - Scheduled diff." -a "From: Cron Daemon <root>" root >/dev/null 2>&1


mkdir: cannot create directory ‘/tmp/snapraid’: File exists

Do I need to do anything to fix this? I thought /tmp folder is cleared on each reboot. Do I need to remove existing /tmp/snapraid?

If I get this error message, does that mean SnapRAID fails to run?

Upgrade went well, on 4.x now. Thanks for the help.

Understood, thank you.

I read some posts that said I need to remove plugins before upgrading. How do I handle that? Do I need to remove openmediavault-omvextrasorg 3.4.30 plugin and its related sub-plugins? I am using omv-backup, snapraid, union file system.

So first remove the children plugins (omv-backup, snapraid, union file system) and then remove the openmediavault-omvextrasorg 3.4.30 plugin, is this correct?

I checked and it looks like these plugins are also supported in 4.x. To reinstall the plugins I need to install openmediavault-omvextrasorg_latest_all4.deb via the web interface and then reinstall the related children plugins (omv-backup, snapraid, union file system)?

Ok, I will backup with clonezilla. Thanks for the advice.

I'm preparing to upgrade to OMV 4 so I made a backup of OMV via the openmediavault-backup 3.11 plugin. If I need to do a restore, what is the process? I see the backup folder that was created but I'm not sure what I'm supposed to do with it if I need to use it.

The plugins I'm currently using are omvextrasorgs, omv-backup, snapraid, and union file system. Not sure if that has an impact or not.

Does the box work again when you put back your old CPU? Normally I would not expect a CPU change to cause this kind of issue unless the instruction set support was different between the CPUs.

Are the CPU virtualization enhancements still turned on in the BIOS? Sometimes called AMD-Vi/VT-d or SVM (secure virtual machine) Mode?

Zitat von subzero79

Because your using fstab the mount is mapped to root. If you are using a desktop the the file browser should be fine. Otherwise use uid in the fstab line.
That is described in the ubuntu wiki for mounting cifs.

Thanks! That fixed the problem. I don't know how I missed the uid option when I was reading the wiki... I guess I shouldn't setup NAS while low on sleep.

Sorry for the triple post. Please delete the extra posts. When I tried to post I kept getting the following error so I thought it failed and kept retrying:

Fatal error: An error occured. Sorry.
Information:

ID: 1aba215ed6d70ce9ba4926bd2b2816da94f2a4f3
Please send the ID above to the site administrator.
The error message can be looked up at “ACP » Logs » Errors”.

I can't seem to figure out why I am unable to write to mounted CIFS/SMB shares using my Ubuntu box. The same share folders are mounted to my Windows 10 PCs using the same account and it has have full read/write access. When I mount the same folders in Ubuntu with the same user I can only read.

Every time I try to create a file or folder in the mounted CIFS/SMB folder I get permission denied. I can only create files or folders if I use sudo. I assume it must be a permission issue, but I am unsure what permissions I need to add in OMV. The user "media" has R/W permission to the folder. I have used the OMV extra tool to make sure to reset the permissions and remove ACL.

Settings in OMV:

line in /etc/fstab from Ubuntu box:

# mount media download folder
//nas2.lesl.pw/media /mnt cifs credentials=/home/mediauser/.smbcredentials,iocharset=utf8,rw 0 0

output of df from Ubuntu box:

Filesystem            1K-blocks      Used  Available Use% Mounted on
udev                    1006344         0    1006344   0% /dev
tmpfs                    204820      3252     201568   2% /run
/dev/sda1              15349744   1652000   12894980  12% /
tmpfs                   1024092         0    1024092   0% /dev/shm
tmpfs                      5120         0       5120   0% /run/lock
tmpfs                   1024092         0    1024092   0% /sys/fs/cgroup
//nas2.lesl.pw/media 6228303224 189799024 6038438664   4% /mnt