Trying to fix little accident on Synology Raid 1 System Volume
by devedse from LinuxQuestions.org on (#5MEEY)
Hi all,
As of this morning I accidently screwed up my Synology device. I tried to manually install iperf3 on it for which I assumed you had to overwrite some files in the /lib folder on the synology device.
The second I did this operation my SSH connection disconnected and the device was unreachable.
Shit. Where's the CTRL+Z...
(you probably know this feeling)
Anyway, my train of thought on how to fix this is as follows:
1. The Synology device has 4 disks
2. There's 2 raid partitions on there. 1: The system partition (should be raid 1) and 2: The Synology Hybrid Raid partition
3. I'm not interested in the SHR partition I just want to fix those files on the system partition.
4. I thought let's put only drive 1 in an Ubuntu computer. Mount the drive, replace the /lib folder with the original en I'd be done. (I hope if I put this drive in my Synology first that it would sync up the other 3 drives system partitions. Hopefully I'd be right on this. (But please let me know if I'm not)
I haven't been able to get the drive to mount though, what I've tried:
Install mdadm + lvm2
I then followed lots of these commands: https://ubuntuforums.org/archive/ind...t-2331271.html
But I haven't been able to get it to mount.
The last thing that I tried was:
Code:mdadm --create /dev/md0 --assume-clean --verbose --level=raid1 --raid-devices=4 /dev/sda1 missing missing missingThis showed me the following text:
Code:mdadm: /dev/sda1 appears to contain an ext2fs file system
size=2490176K mtime=Wed Jul 21 09:49:03 2021
mdadm: /dev/sda1 appears to be part of a raid array:
level=raid1 devices=4 ctime=Sun Dec 8 21:09:22 2019
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: size set to 2487168K
Continue creating array?
Continue creating array? (y/n) y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
root@ubuntu:~# mkdir /mnt/hoi
root@ubuntu:~# mount /dev/md0 /mnt/hoi
mount: /mnt/hoi: wrong fs type, bad option, bad superblock on /dev/md0, missing codepage or helper program, or other error.As you can see I also tried mounting that /dev/md0 device but apparently that didn't work.
I'm a real linux newbie so I would love some help on this topic.
As of this morning I accidently screwed up my Synology device. I tried to manually install iperf3 on it for which I assumed you had to overwrite some files in the /lib folder on the synology device.
The second I did this operation my SSH connection disconnected and the device was unreachable.
Shit. Where's the CTRL+Z...
(you probably know this feeling)
Anyway, my train of thought on how to fix this is as follows:
1. The Synology device has 4 disks
2. There's 2 raid partitions on there. 1: The system partition (should be raid 1) and 2: The Synology Hybrid Raid partition
3. I'm not interested in the SHR partition I just want to fix those files on the system partition.
4. I thought let's put only drive 1 in an Ubuntu computer. Mount the drive, replace the /lib folder with the original en I'd be done. (I hope if I put this drive in my Synology first that it would sync up the other 3 drives system partitions. Hopefully I'd be right on this. (But please let me know if I'm not)
I haven't been able to get the drive to mount though, what I've tried:
Install mdadm + lvm2
I then followed lots of these commands: https://ubuntuforums.org/archive/ind...t-2331271.html
But I haven't been able to get it to mount.
The last thing that I tried was:
Code:mdadm --create /dev/md0 --assume-clean --verbose --level=raid1 --raid-devices=4 /dev/sda1 missing missing missingThis showed me the following text:
Code:mdadm: /dev/sda1 appears to contain an ext2fs file system
size=2490176K mtime=Wed Jul 21 09:49:03 2021
mdadm: /dev/sda1 appears to be part of a raid array:
level=raid1 devices=4 ctime=Sun Dec 8 21:09:22 2019
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: size set to 2487168K
Continue creating array?
Continue creating array? (y/n) y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
root@ubuntu:~# mkdir /mnt/hoi
root@ubuntu:~# mount /dev/md0 /mnt/hoi
mount: /mnt/hoi: wrong fs type, bad option, bad superblock on /dev/md0, missing codepage or helper program, or other error.As you can see I also tried mounting that /dev/md0 device but apparently that didn't work.
I'm a real linux newbie so I would love some help on this topic.