I suddenly don't see my folders into /mnt/md0.
mdadm --detail /dev/md*
/dev/md0:
Version : 1.2
Creation Time : Fri Jan 18 09:54:27 2019
Raid Level : raid1
Array Size : 1953383488 (1862.89 GiB 2000.26 GB)
Used Dev Size : 1953383488 (1862.89 GiB 2000.26 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 18 10:03:38 2019
State : active, resyncing
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Resync Status : 4% complete
Name : myuser:0 (local to host myuser)
UUID : 26f5fe1c:1c272ebe:74d72e1e:0360a892
Events : 112
Number Major Minor RaidDevice State
0 8 16 0 active sync /dev/sdb
1 8 32 1 active sync /dev/sdc
cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdc[1] sdb[0]
1953383488 blocks super 1.2 [2/2] [UU]
[>....................] resync = 4.5% (89573888/1953383488) finish=214.3min speed=144938K/sec
bitmap: 15/15 pages [60KB], 65536KB chunk
unused devices: <none>
Sorry if this question seems silly, but i have seen sillier than that: did you mount the FS(es)? Look at the output of
mount | grep md0
mount | grep md0
root@myuser:/mnt/md0# sudo mount /dev/md0 /mnt/md0
mount: /dev/md0: can't read superblock
RudiC
January 18, 2019, 6:37am
4
It seems to be syncing - sure that doesn't influence the superblock / mounting?
I noticed something strange now. My md change number, look
cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md127 : active (auto-read-only) raid1 sdb[0] sdc[1]
1953383488 blocks super 1.2 [2/2] [UU]
resync=PENDING
bitmap: 12/15 pages [48KB], 65536KB chunk
unused devices: <none>
sudo mkfs.ext4 -F /dev/md127
mke2fs 1.43.4 (31-Jan-2017)
/dev/md127 contains a ext4 file system
last mounted on /mnt/md0 on Thu Oct 11 09:44:02 2018
Creating filesystem with 488345872 4k blocks and 122093568 inodes
Filesystem UUID: 5458e532-e0f1-4cf9-9cdd-d016d16c21fd
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information:
done
Maybe to wait no to finish sync?
You don't need to wait for it to finish syncing, no.
The device changing number may have been due to a reboot, i.e. one boot was a device you made, the next reboot was auto-assembled and the device number chosen automatically.
By running mkfs on it again you wiped out whatever was on it before.
The question is, why was this raid1 array rebuilding?
It could be that the resilvering has, for some reason, occurred in the wrong direction, meaning that your replacement disk has been mirrored over the running disk causing the data to be lost.
Did you initiate the rebuild of the raid1? Or did it start automatically?
1 Like
hicksd8:
The question is, why was this raid1 array rebuilding?
It could be that the resilvering has, for some reason, occurred in the wrong direction, meaning that your replacement disk has been mirrored over the running disk causing the data to be lost.
Did you initiate the rebuild of the raid1? Or did it start automatically?
Do I have some chance to restore md0 or I must get data back and make raid again
joker
January 20, 2019, 3:54pm
9
Since you likely destroyed your data by reformatting I would suppose data recovery very difficult.
Better have your backup restored.