Posts by Teschbert

I'm not an expert for this. But I really appreciate having a "Console/Terminal" integrated in the Homebridge-web-IF.

It just make some things more smooth ...

I would support (whatever this means) having the same in omv

Quote from ryecoaaron

While I don't have any wayland packages installed on my RPi, I would guess one of the RPi utilities has an optional gui componen

Strange.

But I'm not willing to make any "uninstall tests" w/o knowing exactly before what will happen.

Maybe you're able to tell me how to find out what the dependencies are?

Thanx. I did not install anything special - just RPiOS Lite + OMV + some non-graphical-omv-extra-plugins + plexmediaserver.

A reverse dependency search brought up nothing which points to something obvious.

Some further research showing that those libraries are part of and installed by the special Debian-Repo for RPi - for whatever reason.

At the end I gave up research, did the upgrade and everything's working as before.

Edit w more info:

I've got the same packages as list to be upgraded on my other RPI just running RPiOS Lite, homebridge and AdGuardHome.

So definitely a special for RPis

Hi,

I'm a little bit confused this morning because OMV7 is reporting "detected upgrades on Wayland":

apticron has detected that some packages need upgrading on:

    omv
    [ xxxxxxxxxxxxx ]
    [ xxxxxxxxxxxxx ]

The following packages are currently pending an upgrade:

    libwayland-client0 1.23.1-3+rpt1
    libwayland-cursor0 1.23.1-3+rpt1
    libwayland-egl1 1.23.1-3+rpt1
    libwayland-server0 1.23.1-3+rpt1

Is this correct for an headless system?

Just asking before pressing the update button.

OMV ist schon ein sehr gutes Stück SW.

Aber: man muss sich schon ein wenig damit beschäftigen und wie immer: Basiskenntnisse zu Linux und NAS müssen vorhanden sein.

Der Support hier ist recht kompetent. Allerdings muss man auch genau beschreiben, was man im Detail getan hat.

Eine Aussage wie - Zitat - "Ich hatte eine Festplatte kurz Ausgebaut gehabt weil ich dachte die hat nen Fehler, hat sie aber nicht, also wieder rein damit"

Was heisst denn das genau? Hast du sie einfach im Betrieb abgezogen? Warum genau? Wie genau? Hast du sie zuvor ausgehängt? Beim Einbauen einfachen im Betrieb wieder angestöpselt?

Eine Fehlermeldung wie "Struktur muss bereinigt werden" klingt für mich zB nach einem Dateisystem-Defekt, der durchaus auftreten kann, wenn man eine Platte nicht ordnungsgemäß abmeldet.

Ohne diese ganzen Infos kann/wird hier niemand helfen/können.

Certainly, there is one action you can take from the OMV-Project side before releasing omv8, as the samba-related issue has not been resolved:

Issue a high-priority warning to all Mac users that the upgrade will render all Timemachine backups inaccessible.

I believe this is a significant concern, and I am confident that the project team is not interested in receiving an overwhelming number of angry users.

Thats my small HW-Setup (incl. a dedicated ssd for Timemachine backup because I'm Apple user)

I installed Plex directly on system ssd w/o docker (which is not the recommended solution from OMV-Team but working smoothly since 2 years)

Right. Filevault on a Mac has absolutely nothing to do w encryption on an OMV system (or any other NAS or external storage).

If encryption is needed on the NAS you'll have to switch it on there.

Quote from Stasys

People on this forum wrote that they are doing USB backup on ntfs usb hdd. Just that this hdd shall have only one partition - which I have in shown in windows, but not in linux.

Then you should better ask these people directly - or do some search in the internet.

If I'm not wrong, for NTFS support you'll have to install a special driver. This is not included in standard debian.

But I'm not the expert on this and I'm not using Windows-Systems at all. Just Apple and Linux.

From my understanding NTFS is not a supported filesystem (ootb)

If you accept an alternative to rclone:

I'm using duplicacy for this (to another Cloud but GoogleDrive ist supported too) - single binary, powerful, fast, secure, free

Quote from Manicotti Combo

I was thinking that, but I think you are referring to the relative path, I feel like it should work as it is. I tried it anyway and still the same error, however I noticed that the file name of the torrent is actually created, but same error from qbbittorrent that the device doesnt exist.

I was curious did you specify any options here when you created your pool?

Here my Shared Folders:

I was following exactly the guide on omv-extras for mergerfs:

omv6:omv6_plugins:mergerfs [omv-extras.org]

More I cannot say because I'm not an expert on this. I just saw the differences in the setup.

And answering your question: No, I didn't define any special mergerfs options

There's no shared folder created on "TheBigNacho" - maybe that's the problem.

My shared folders are all created on the mergerfs pool and I'm having no issues accessing them from docker.

Just for information and interested people. Found more info/backgroud here in the official Raspberry forum.

Just did the update, got the same warnings, but I did a "dpkg -L rpi-eeprom" before and after which let me diagnose it. The paths in the package have changed from /lib/firmware/raspberrypi to /usr/lib/firmware/raspberrypi. dpkg isn't smart enough to understand that /lib is a symlink to /usr/lib on modern Debian, so it tries to delete the paths which are no longer in the package. Everything that should be there seems to be there after the upgrade, and "dpkg -V rpi-eeprom" doesn't show any problems. Whether that's an intentional change, or more "correct", I can't really say for sure. I can, however, say for certain that it's just harmless noise in practical terms.

An Issue is reported at GitHub: https://github.com/raspberrypi/rpi-eeprom/issues/655

Quote from martinbln

ths Teschbert. Unfortunately my OMV did run mad... that's why i need the restore. i'll get some new sd-cards.

OK. Maybe you should think about switching to a small/cheap SSD in an USB3-case then ...

Its not much more expensive but more reliable

There are two other ways if your system is still living:

1- You have another Windows or Apple System: create a new backup/clone of your SD-Card w a tool which has a shrinking possibility (for a macOS System that could be ApplePiBaker) and restore to the smaller card directly.

2- You're having another second Linux System: create w omv-backup a new backup switching from dd to fsarchiver, and follow the instructions you mentioned in your initial post. Eventually you'll have to adopt the root partition of the new SD card with (g)parted. after creating the partition table with the .grubparts file.

Quote from ryecoaaron

These warnings are completely harmless. There is nothing to solve. It just means another package had a file in the directory. It is very common in many packages especially kernel and firmware packages.

Would mean: "Just do nothing - maybe its somehow fixed or just disappearing in future"?

Those warnings, especially if they occur the first time, are making me a little bit nervous because I cannot overview what are possible future implications

Easy answer:

The the .fsa file belongs to "fsarchiver" . You configured your Backup using dd.

This is why you can't find it.

Quote from Soma

Have you tried the raspberry forum for answers?

What I can think is maybe try to change the version of the eeprom via raspi-config to the STABLE instead of LATEST to see if it can clear the error

No, not yet. If I can't get a definitive answer here, I'll give it a try.

Your hint could help. Or I just do a clone from my system SD of my other RPI, and just try to delete the directories manually and see what happens ...

But my hope was that other more experienced RPi users are observing the same warnings and have a safe solution.

These warnings appeared last week first w the latest Linux updates.

Today I've seen the following warnings when updating the system:

...

Unpacking rpi-eeprom (26.9-1) over (26.8-1) ...

dpkg: warning: unable to delete old directory '/lib/firmware/raspberrypi/bootloader-2712/latest': Directory not empty

dpkg: warning: unable to delete old directory '/lib/firmware/raspberrypi/bootloader-2711/latest': Directory not empty

...

I've seen this on another RPi w/o omv ...

What does this mean?

Anything to fix it?