Ok. Try:
mkdir -p /media/test
mount /dev/md127 /media/test
Ok. Try:
mkdir -p /media/test
mount /dev/md127 /media/test
tried it and got this now
mount: you must specify the filesystem type
not sure how to add ext4 as I'm pretty sure that it is that
That isn't a good sign... mount -t ext4 /dev/md127 /media/test
you are right
i'm not having any luck with OMV
mount: wrong fs type, bad option, bad superblock on /dev/md127,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
If that doesn't work, then
mdadm --stop /dev/md127
mdadm --assemble --run --force --update=resync /dev/md127 /dev/sd[ab]
i'm not having any luck with OMV
This isn't an OMV problem... You might have better luck using a scheduled rsync job than using raid 1.
I can see that the RAID array is re-syncing.
but still unable to mount
yeah this new issue got unravelled because i tried using rsync from old to new.
then for some reason the job got stuck, waited for a while but nothing was happening.
I rebooted the old OMV server, it came back up, but unable to login
so whenever I tried logging in, it accepted my password, but it just kept looping at login page.
my plex server was running, but SMB/CIF wasn't. I could still SSH in.
do you think i will have better luck fixing that issue? As I will need some help on that one too
then when that's back in business, I'll just to rsync.
Always let an array finish syncing before doing anything to it.
One problem at a time...
LOL. yes sir!!
by the way, the status of the synching of RAID is in pending.
mdadm --readwrite /dev/md127
nice, thanks.
If this raid can be mounted on this new omv then won't need to sort out the old omv
That sounds good. Did it finish syncing?
nah, it's still going. only 2% at the moment. it will defo take sometime.
Hi Rye,still a no go unfortunatelyback to square one.should I just bung them back to the old OMV and fix the login issue?or since I can access the old omv thru ssh, maybe run rsync via cli? whaddya think?
from bad to worse ( I think)
put HDDs back to old OMV and now it's not mounted too ( I think)
here's the proc/mdstat
cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : active (auto-read-only) raid1 sdb[0] sda[1]
1953513424 blocks super 1.2 [2/2] [UU]
blkid
/dev/sda: UUID="4bd6103f-6c37-782a-f3d2-03511a8e5df7" LABEL="openmediavault:DATA" TYPE="linux_raid_member"
/dev/sdb: UUID="4bd6103f-6c37-782a-f3d2-03511a8e5df7" LABEL="openmediavault:DATA" TYPE="linux_raid_member"
/dev/sdc1: UUID="425d4f1d-1fd2-4642-aebc-c5332ccc464e" TYPE="ext4"
/dev/sdc5: UUID="50ceae47-10e2-436c-9ec1-7453e5eafdb7" TYPE="swap"
Really hope i haven't lost any of the data...
Hi Rye,
Am I really in a bad position right now?
Is there any hope of recovering the DATA in that RAID array?
The fact that the filesystem doesn't show up in blkid when the array is active is not good. I would try booting systemrescuecd and then post the output of fdisk -l, blkid and cat /proc/mdstat
okay, thanks buddy. I'll try that.
Cheers
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!