I assume you had the flashmemory plugin installed? I have seen SD fail in less than two days without it.
apt failing, normal fixes don't seem to help.
-
-
-
This also makes me FAR less confident that cloning will work. *SIGH*
-
-
dpkg -l | grep openme
-
Code
pi@piomv:~ $ dpkg -l | grep openme ii openmediavault 6.0.28-3 all openmediavault - The open network attached storage solution ii openmediavault-flashmemory 6.1 all folder2ram plugin for openmediavault ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive ii openmediavault-omvextrasorg 6.0.9 all OMV-Extras.org Package Repositories for OpenMediaVault
-
My word. Look at the price comparison. You could buy one 16GB and two 3packs for the price of that one 400GB.
In my signature there is a link to a backup how-to using all three platforms. Using 32GB SD cards, I can back up to desktop, and then dd that to my backup SD card in about 35 minutes. Soma is right. Smaller is better - up to a point. Using 16GB cards would cut that time in half, but I wouldn’t go any smaller.
-
-
Keep in mind, I didn't purchase this sd card this for omv, I bought it to run in a camera I had, and then decided to just use streaming to blue iris instead. It happened to be the only card over 2GB I had
I'll take a look at your backup data, because its apparently of concern for me. -
Off topic: Love that Blue Iris. Too bad there's not a Linux version.
-
Yeah, I wasn't thrilled that its windows only, but it works and it reliable. So I loaded up a VM and tossed it in there.
-
-
So I have rebuilt my openmediavault from scratch and Im trying to mount the USB I had mounted on the previous version, and mount isn't cooperating.
mount: /srv/dev-disk-by-uuid-0a0f0128-3742-4b9d-a834-26a4e672021b: mount(2) system call failed: File too large
Usually this is because e2fs tooling is old...but the system is up to date. Any ideas?
Kernel:
Linux piomv 5.15.32-v7l+ #1538 SMP Thu Mar 31 19:39:41 BST 2022 armv7l GNU/Linux
Tooling:
root@piomv:/srv# dpkg -l | grep e2fs
ii e2fsprogs 1.46.2-2 armhf ext2/ext3/ext4 file system utilities
-
Crap...why do I have a feeling that arm7l is 32 bit. Man, I'm really frosty now. How could the "current" version of raspbian lite be 32 bit
-
So after reinstalling with a new sd, I was troubleshooting the old one...it somehow has been set to read-only. No tooling can change it. Tried changing attributes, different adapters, windows, linux, etc. Its borked.
-
-
So after reinstalling with a new sd, I was troubleshooting the old one...it somehow has been set to read-only. No tooling can change it. Tried changing attributes, different adapters, windows, linux, etc. Its borked.
That's usually a pretty good sign, an SDcard has died or is close to it.
-
Crap...why do I have a feeling that arm7l is 32 bit. Man, I'm really frosty now. How could the "current" version of raspbian lite be 32 bit
Use the raspiOS lite version arm64.
The "standard" version is always 32bit so it's retro-compatible with all Raspberry boards.
-
I was troubleshooting the old one...it somehow has been set to read-only. No tooling can change it
How to Fix Write-Protected MicroSD Card on Windows and Mac (wondershare.com)
-
-
I tried all the detailed steps in that article...although I got the data elsewhere. There must be something in the card itself that flips some bit causing the unit to be read only when a catastrophic event happens.
-
Didn't I mention that back in post #4? Over the years, I have created a large pile of dead SD cards testing OMV and plugins. These weird behaviors have very often been the warning sign.
-
First experience for me. I just expected corruption and disaster, not read-onlyville
-
-
I just expected corruption and disaster, not read-onlyville
I've seen both and more.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!