Issues with Macrium Reflect Files on NextCloud-Datadir disk

debreziner · Apr 8th 2024

Hello, my NextCloud AIO installation has been running for three weeks. I have no problems, with the following exception: A Macrium Reflect backup cannot be opened.

The NextCloud datadir is on an ext4 drive. The Macrium backup is on the external NVME, but not in the NextCloud datadir. When calling the backup in Macrium, I get a general error. Three other Macrium backups on the same NVME do not cause any problems.

The "problematic" image has about 500GB, the others are much smaller. I have another copy of this image on an NTFS drive. This can be used in Macrium without any problems.

Now I wanted to simply copy the image from the NTFS to the external NVME, but I regularly get errors here.

No matter whether I make the copy via Windows, Cyberduck via WebDAV or with Rsync, it gets stuck at some point and there is no way to write to the NVME anymore.

After the failed copy attempt, the NVME seems to be in read-only mode, no files can be written (neither in NextCloud nor in the SMB-Share).

Rebooting omv settles the issue, the NVME works again (the Macrium image of course not)

While trying to copy the file, I got the following on the open putty session:

Message from syslogd@omv-nas at Apr 3 00:48:25 ...

kernel:[13857.795318] EXT4-fs (sdc1): failed to convert unwritten extents to written extents -- potential data loss! (inode 175243273, error -30)

Might this error <RE: NextCloud AIO - Permission denied?> be somehow related to the behavior described here?

Is there a problem with the NextCloud installation or the associated rights? Or do the signs point more in the direction of a hardware problem?

Thanks for your feedback!

Soma · Apr 8th 2024

Quote from debreziner

The "problematic" image has about 500GB, the others are much smaller.

Instead of making a "single file" backup, try splitting it in 100Gb segments, for eg

debreziner · Apr 9th 2024

Hm, copying 100GB chunks didn't help, it broke down pretty soon.

Trying to open “Storage->Disks”, I got the following error:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; blockdev --getsize64 '/dev/sdb' 2>&1' with exit code '1': blockdev: cannot open /dev/sdb: No such device or address

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; blockdev --getsize64 '/dev/sdb' 2>&1' with exit code '1': blockdev: cannot open /dev/sdb: No such device or address in /usr/share/php/openmediavault/system/process.inc:242
Stack trace:
#0 /usr/share/php/openmediavault/system/blockdevice.inc(261): OMV\System\Process->execute(Array)
#1 /usr/share/openmediavault/engined/rpc/diskmgmt.inc(87): OMV\System\BlockDevice->getSize()
#2 [internal function]: Engined\Rpc\DiskMgmt->enumerateDevices(NULL, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/openmediavault/engined/rpc/diskmgmt.inc(124): OMV\Rpc\ServiceAbstract->callMethod('enumerateDevice...', NULL, Array)
#5 [internal function]: Engined\Rpc\DiskMgmt->getList(Array, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('getList', Array, Array)
#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(620): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusqi...', '/tmp/bgoutputIM...')
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#10 /usr/share/openmediavault/engined/rpc/diskmgmt.inc(151): OMV\Rpc\ServiceAbstract->callMethodBg('getList', Array, Array)
#11 [internal function]: Engined\Rpc\DiskMgmt->getListBg(Array, Array)
#12 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#13 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getListBg', Array, Array)
#14 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('DiskMgmt', 'getListBg', Array, Array, 1)
#15 {main}

Display More

/sdb is the external SSD.

Still, under „File Systems“ it seemed to be online:

Unfortunately, I could not write nor read from the disk...

Soma · Apr 9th 2024

You have drives in NTFS. This is not a FS for Linux.

Since one is showing missing and referenced, you will have problems.

Since it is connected via USB, your system might not cope with the power needed for that.

Quote from debreziner

Now I wanted to simply copy the image from the NTFS to the external NVME, but I regularly get errors here.

Are you running this as ROOT?

NTFS files/folders mounted on Linux will always be owned by ROOT.

There's no way to change the permissions and it looks that's exactly what is going on with the error

Quote from debreziner

kernel:[13857.795318] EXT4-fs (sdc1): failed to convert unwritten extents to written extents -- potential data loss! (inode 175243273, error -30)

These are just thoughts

Soma · Apr 9th 2024

Quote from debreziner

kernel:[13857.795318] EXT4-fs (sdc1): failed to convert unwritten extents to written extents -- potential data loss! (inode 175243273, error -30)

A search on the web hit this:

EXT4-fs failed to convert unwritten extents to written extents -- potential data loss! : r/debian (reddit.com)

Quote

It happend to me twice today in 2022.
It's caused by USB hub. After removing it, the issue is solved.

Among other things so, check what you have.

debreziner · Apr 9th 2024

Dear Soma, thanks for your thoughts.

As I mentioned, I have multiple Macrium-Images on the SSD, I access them through the same Shared Folder/SMB. So I would exclude there is a permission problem.

Of course, this might be to quick, because I didn't check if the permissions are set exactly the same on the files - Unfortunately, I don't know how to do this.

The missing NTFS-disk shouldn't be that much of a problem too, it is only referenced as a smb-share I'm not using.

On the other NTFS formatted disk I have backed up my "main" Macrium Backups. Backups are planned daily and seem to run well. Opening images from there works. Of course, these are images from a ntfs source to a ntfs smb-share, which might be "easier" than a ntfs source to a ext4-partition?

Anyway, thanks for the reddit discussion, of course it would be great if unplugging and plugging in again would solve the issue

I also would go through the other suggested steps (memtest, changing cable).

Is there a suggested way to run memtest on omv?

Or is it something I should do from the boot menu?

(Most importantly I should get the borg backup running on nextcloud before I do any of the fsck-steps...)

Soma · Apr 10th 2024

Quote from debreziner

Unfortunately, I don't know how to do this.

You need to check them on the CLI with ls -al /srv/dev-disk-by-<UUID>/<folder name>/

It will show the permissions, ownership, etc...

Quote from debreziner

The missing NTFS-disk shouldn't be that much of a problem too, it is only referenced as a smb-share I'm not using

It is in case you make changes on the GUI that require some modules to relaunch.

For example, any editing on the Filesystems Page or Samba (since it's referenced there).

OMV expects drives to be always ON.

Quote from debreziner

On the other NTFS formatted disk I have backed up my "main" Macrium Backups. Backups are planned daily and seem to run well. Opening images from there works. Of course, these are images from a ntfs source to a ntfs smb-share, which might be "easier" than a ntfs source to a ext4-partition?

You aren't making NTFS to NTFS copy.

The way you have it, IIRC, you are using a WindowsPC with a SMB shared folder connected via Explorer.

That SMB folder is on a Linux server but lives on a NTFS drive.

Since NTFS on Linux doesn't have POSIX permissions, it can only be used/owned by root:root

The SMB share has it's own permissions added on top of the HOST permissions which creates conflicts.

Sorry but it's difficult to explain other than, you need to have Linux FS when using drives on it, regardless of sharing it to Windows or Mac.

For info sake, I only use NFS (a Linux native Network Sharing FS) with my WindowsPC since I found to be better controlled than SMB.

I really "hate" SMB.

Quote from debreziner

Is there a suggested way to run memtest on omv?

If you run on x64, use the kernel plugin and use the boot to memtest.

debreziner · Apr 11th 2024

Ok, thanks.

I think my issue with the macrium image is due to the strange clinch of permission smb-share/ext4/ntfs.

Using your command line, I got this:

The last one being the problematic file, while the two just before work fine. Seems to be no difference in owner or permission.

It definitely makes sense that mixing up different philosophy might bring up problems somewhere...

I was barely aware that might be problems using ntfs with linux, and I tended to ignore what I know just because I wanted to be able to get the disk with backups connected with a Windows Pc and running.

This was before I fell in love with omv and felt it like a safe harbor for my data.

So a couple of minutes ago I started the first borg backup of my nextcloud (on a ext4 drive, of course).

Next step will be to find a way how I can give other containers (like jellyfin) access to photos/videos saved in nextcloud, but that's a different topic

Participate now!