Restore RAID1 with an old disk (I've been hacked) - NAS320
Comments
-
Strange. Does this disk needs more power than the encrypted disks do?
No, I don't think. One of the encrypted disk is exactly the same as this one. Before the wrong repair process, the disk was seen through the Zyxel interface.So now:root@ubuntu:/home/ubuntu# mdadm --examine /dev/sdc2<br>/dev/sdc2:<br> Magic : a92b4efc<br> Version : 0.90.00<br> UUID : 346361d3:cbfe4cbd:f4fc2a5c:e6a2d6d5<br> Creation Time : Tue Oct 23 14:16:55 2012<br> Raid Level : raid1<br> Used Dev Size : 1952997888 (1862.52 GiB 1999.87 GB)<br> Array Size : 1952997888 (1862.52 GiB 1999.87 GB)<br> Raid Devices : 2<br> Total Devices : 2<br>Preferred Minor : 0<br><br> Update Time : Tue Dec 18 15:51:00 2018<br> State : clean<br> Active Devices : 1<br>Working Devices : 2<br> Failed Devices : 1<br> Spare Devices : 1<br> Checksum : a665828a - correct<br> Events : 1618289<br><br><br> Number Major Minor RaidDevice State<br>this 2 8 2 2 spare /dev/sda2<br><br> 0 0 8 18 0 active sync<br> 1 1 0 0 1 faulty removed<br> 2 2 8 2 2 spare /dev/sda2
As requested, I tried:root@ubuntu:/home/ubuntu# modprobe raid1<br>root@ubuntu:/home/ubuntu# cat /proc/mdstat<br>Personalities : [raid1] <br>md0 : inactive sdc2[2](S)<br> 1952997888 blocks<br> <br>unused devices: <none>
In my point of view, it's not absolutely necessary to remount the raid. Do you think just mounting the HD only is possible? I can then backup the important things.Thanks!
0 -
Do you think just mounting the HD only is possible?
Fortunately that should be quite easy. According to your header listing the array uses a version 0.9 superblock. That is at the end of the partition, so the physical start of the filesystem is also the physical start of the partition. In other words, the partition can simply be mounted.
According to this bootlog an NSA320 uses (or at least used to use) ext3 as filesystem.
So to mount it:
<p>mkdir /tmp/mountpoint</p><p><br></p><p>mount -t ext3 /dev/sdc2 /tmp/mountpoint<br></p><p></p>
0 -
I tried but got the same result as explained here:Should I try the:
</code><code>mdadm --assemble --run /dev/md0 /dev/sdc1
trick ?More info about the disk
0 -
[quote]Should I try the:
</code><code>mdadm --assemble --run /dev/md0 /dev/sdc1
trick ?[/quote]It won't hurt, although in your case it'smdadm --assemble --run /dev/md0 /dev/sdc2
Another suggestion in that forum which is worth trying is[quote]If anyone still gets themdadm: /dev/sdb1 is busy - skipping message
you can stop the device on withmdadm --stop /dev/mdx
or check the/proc/mdstat
to check if the device was automatically mount by your system.[/quote]
1
Categories
- All Categories
- 415 Beta Program
- 2.5K Nebula
- 152 Nebula Ideas
- 101 Nebula Status and Incidents
- 5.8K Security
- 296 USG FLEX H Series
- 281 Security Ideas
- 1.5K Switch
- 77 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.5K Consumer Product
- 254 Service & License
- 396 News and Release
- 85 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 87 About Community
- 76 Security Highlight