That’s no good. You can try and recover the partition table first
https://lihashgnis.blogspot.co…ted-gpt-partition_30.html
Once there check if the Fs signature appears again.
I assume the disk should be gpt because is 5TB. Check with gdisk if it says gpt is present.
I’ve never done gpt partition rescue before but as I understand the benefits is the partition table is Backed several times across the disk.
Alles anzeigen
Looks like the partition rescue mentioned in that article isn't around anymore but I was able to use "testdisk" and got it kinda working... Now it hangs on boot with errors and if I "ctrl D" then it boots. In the web interface it shows as online now but I can't access the folder from another computer says no such directory.
Now I'm trying to figure out how to fix it so it boots without errors and then how to access it again.
When I try and mount it I get this error
or how to fix the errors on boot?
running :~# journalctl -xb shows these errors
Jul 04 14:24:21 OMV5.local blkmapd[310]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
Jul 04 14:24:21 OMV5.local systemd-fsck[389]: StorageOne: One or more block group descriptor checksums are invalid. FIXED.
Jul 04 14:24:21 OMV5.local systemd-fsck[389]: StorageOne: Group descriptor 448 checksum is 0x0000, should be 0x06a7.
Jul 04 14:24:21 OMV5.local systemd-fsck[389]: StorageOne: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Jul 04 14:24:21 OMV5.local systemd-fsck[389]: (i.e., without -a or -p options)
Jul 04 14:24:21 OMV5.local systemd-fsck[389]: fsck failed with exit status 4.
-- The unit systemd-fsck@dev-disk-by\x2dlabel-StorageOne.service has entered the 'failed' state with result 'exit-code'.
Jul 04 14:24:21 OMV5.local systemd[1]: Failed to start File System Check on /dev/disk/by-label/StorageOne.
-- Subject: A start job for unit systemd-fsck@dev-disk-by\x2dlabel-StorageOne.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- A start job for unit systemd-fsck@dev-disk-by\x2dlabel-StorageOne.service has finished with a failure.
-- The job identifier is 350.
Jul 04 14:26:30 OMV5.local cron[881]: (CRON) INFO (pidfile fd = 3)
Jul 04 14:26:30 OMV5.local chronyd[890]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +AS
Jul 04 14:26:30 OMV5.local systemd-fsck[837]: StorageOne: One or more block group descriptor checksums are invalid. FIXED.
Jul 04 14:26:30 OMV5.local systemd-fsck[837]: StorageOne: Group descriptor 448 checksum is 0x0000, should be 0x06a7.
Jul 04 14:26:30 OMV5.local systemd-fsck[837]: StorageOne: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Jul 04 14:26:30 OMV5.local systemd-fsck[837]: (i.e., without -a or -p options)
Jul 04 14:26:30 OMV5.local systemd-fsck[837]: fsck failed with exit status 4.
Jul 04 14:26:30 OMV5.local systemd-fsck[837]: Running request emergency.target/start/replace
Jul 04 14:26:30 OMV5.local chronyd[890]: Frequency 6.187 +/- 0.090 ppm read from /var/lib/chrony/chrony.drift
Jul 04 14:26:30 OMV5.local chronyd[890]: Loaded seccomp filter