No idea, sorry.
The drive might be just toast.
Posts by macom
-
-
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
-
You can check the filesystem with fsck
Check and Repair Filesystem Errors With fsck Command in LinuxLinux systems come with a command line utility fsck to check for file system errors. Learn how to use it.linuxhandbook.comSuggest to google first for "group descriptors corrupted"
-
[ERROR ] stderr: mount: /srv/dev-disk-by-uuid-30ab1487-c9f9-4694-91d6-4efbd6f58085: mount(2) system call failed: Structure needs cleaning.
dmesg(1) may have more information after failed mount system call.
back to square one. Check if dmesg has some info about this filesystem
If you don't need the data on that drive, delete it and create a new one.
-
If there is already a filesystem on the drive, use "mount existing filesystem". It is the icon that looks like "play"
-
Soma any idea?
-
If OMV is in an inconsistent state it gives an error. Inconsistent state could be that the database (config.xml) contains the UUID of a filesystem, that does not exist.
You could make a copy of config.xml as backup and check if and where the UUID is mentioned.
-
Das witzige ist dass beim ersten einschalten das alte ("RAID") erkannt wurde und unter Dateisystem eingehängt werden konnte.
Hab dann nochmal was gemacht und dazu ausgehängt und seitdem erkennt er es nicht mehr.
Was hast du beim aushängen und danach genau gemacht? Vielleicht aus versehen die Platten gelöscht?
-
No idea where the backports is coming from.
Can you try again
sudo grep -rlI "backport" /etc/apt/ 2>/dev/null
Copy and paste. If you have to type, the options are lower case R, lower case L and upper case I
-
Did you remove a filesystem with the UUID
56fed896-e2e8-4653-b158-2ee3f1d01848
Is this filesystem marked as missing in the GUI?
-
So part-way through the install, after having created the partitions, the system file install begins, but when the system install gets to 8%, the screen goes red, and an error message comes up saying something like "System install failed", and I'm given the option to select a different part of the install process.
I understand you are now able to release-upgrade. Anyhow, maybe this error is related to the drive you want to install OMV on. Did you try another drive?
You could also try the alternative installation:
-
BTRFS or EXT4 (or other)? This drives ar archive media and files (downloads, etc), so I won't need snapshots. Is the checksum feature good? Or I should just use EXT4? Right now they are with AppleFS, so I assume EXT4 would be a fine replacement.
Go for ext4 if you do not need the advanced features of btrfs.
btrfs needs some learning and maintenance.
Is the OMV LUKS plugin stable enough to not lose data?
The plugin is making use of luks. You can google "luks linux" to see if it is considered stable. I would think so. I use it since several years on a portable drive. But why do you need file encryption on a NAS? Biggest risk is probably that someone is hacking your server while it is running and the filesystem is decrypted.
Luks cannot prevent you from loosing data. For that you need backup.
Other suggestions to be aware (...?)
Think about backup.
Also consider the age of your drives. Check the SMART values of those drives.
I will get a PC motherboard with gigabit connection and enough SATA ports.
Probably will have to buy soemthing like this https://pt.aliexpress.com/item/1005005653706057.html
I assume it will be detected by BIOS (driverless) and OMV without a problem, right?
I guess now one can judge if some hardware purchased from aliexpress will work without problems with Debian (OMV is based on Debian).
-
When I try to update to OMV6 using omv-release-upgrade I get an error that debian buster-backports Release no longer has a release file.
Disable backports (e.g. by removing it from the sources). There are several thread about it.
When I try a fresh install of OMV7, I get as far as installing system to 8% and I get an error.
Which error?
-
Sorry, I thought it was another issue.
So in shared folders the dust bin is grey, not like in the picture below? The selected folder is not marked as referenced and delete is enabled.
-
I assume the apt plugin is installed. Correct?
It is normal that you get a connection reset by peer error.
-
Did I mention that these folders are not empty but rather full?
Does not matter.
both exist
Did you check, if they are visible in the shared folders view?
If they do not show up, try to create the shared folder after clearing your browser cache or using another browser or in a private window.
Maybe it is a cache issue.
-
Did you ran the commands as root or with sudo?
that is why I suggested
Post the command + the output + the prompt at the end in a code box </>
-
This is not a common issues, otherwise the forum would be full of threads related to this.
Most likely the issue happens only under certain circumstances (e.g. a corrupted file system). So a proposal that did not work for others, but still work for you.
If you provide the output of the commands, they might contain also a hint regarding the underlying problem.
-
DNS issue?
Might be better to post the complete error message from the bell icon in the top right corner of the GUI.
-
Strange. According that there is no backport repo in the sources.
Please post the output of
omv-apclean repos
cat /etc/apt/sources.list.d/openmediavault-kernel-backports.list
Post the command + the output + the prompt at the end in a code box </>
