#1 Le 03/01/2025, à 16:39
- celtos
Monter en external USB 1 des 2 disques RAID1 d'un NAS Synology
Bonjour et bonne année !
Mon NAS Synology à rendu l'âme (il fait disjoncter le tableau électrique !) mais les disques en RAID1 sont intacts.
J'essaye de monter un des disque via un adaptateur SATA-USB pour récupérer le contenu, je vois bien le disque mais je galère à le monter, il y a qques chose que je ne dois pas bien faire dans la construction du RAID.
Le disque est en /dev/sda, et je veux monter la partition 3, ie /dev/sda3 :
sudo fdisk -l
...
Disk /dev/sda: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Generic
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x2e860600
Device Boot Start End Sectors Size Id Type
/dev/sda1 63 4980149 4980087 2,4G fd Linux raid autodetect
/dev/sda2 4980150 6024374 1044225 509,9M fd Linux raid autodetect
/dev/sda3 6281415 3907024064 3900742650 1,8T fd Linux raid autodetect
Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Je construit un array RAID avec seulement 1 des 2 disques en /dev/md0 :
sudo mdadm --create /dev/md0 --raid-devices=2 --level=1 /dev/sda3 missing
mdadm: /dev/sda3 appears to contain an ext2fs file system
size=1950371200K mtime=Thu Feb 16 18:27:31 1911
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
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
mdadm semble Ok :
sudo mdadm --examine /dev/sd*
/dev/sda:
MBR Magic : aa55
Partition[0] : 4980087 sectors at 63 (type fd)
Partition[1] : 1044225 sectors at 4980150 (type fd)
Partition[2] : 3900742650 sectors at 6281415 (type fd)
mdadm: No md superblock detected on /dev/sda1.
mdadm: No md superblock detected on /dev/sda2.
/dev/sda3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 841a9d3b:401e79a8:dda0d7d8:24f6bb31
Name : yle-HP202411:0 (local to host yle-HP202411)
Creation Time : Fri Jan 3 14:45:32 2025
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 3900478458 sectors (1859.89 GiB 1997.04 GB)
Array Size : 1950239168 KiB (1859.89 GiB 1997.04 GB)
Used Dev Size : 3900478336 sectors (1859.89 GiB 1997.04 GB)
Data Offset : 264192 sectors
Super Offset : 8 sectors
Unused Space : before=264112 sectors, after=122 sectors
State : active
Device UUID : 96444d79:841997e0:3461eafa:e5f2e563
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Jan 3 14:45:32 2025
Bad Block Log : 512 entries available at offset 16 sectors
Checksum : 7f46f641 - correct
Events : 0
Device Role : Active device 0
Array State : A. ('A' == active, '.' == missing, 'R' == replacing)
Donc j'assemble le RAID :
sudo mdadm --assemble --readonly /dev/md0 /dev/sda3
mdadm: /dev/md0 has been started with 1 drive (out of 2).
A cette étape le RAID me parait fini, non ?
Donc j'essaye de monter la partition /dev/md0 :
sudo mount /dev/md0 /mnt/disk
mount: /mnt/disk: wrong fs type, bad option, bad superblock on /dev/md0, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
dmesg :
[ 7590.987396] EXT4-fs (md0): VFS: Can't find ext4 filesystem
Même message avec -t options : ext2, ext3, btrfs ...
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 linux_raid_member 0.90.0 b51b784c-429f-ce19-c4ee-86b89aa5bc1a
├─sda2 linux_raid_member 0.90.0 c1a2aad6-e324-b0a0-c44f-a1ff69c21353
└─sda3 linux_raid_member 0.90.0 5a827f2d-0f7e-b097-9155-809b0da8f21d
└─md0
Hors ligne
#2 Le 03/01/2025, à 16:59
- celtos
Re : Monter en external USB 1 des 2 disques RAID1 d'un NAS Synology
J'ai trouvé le problème !!!
C'est une histoire de version de metadata --metadata=0.9
Je laisse le post pour les prochains en galère !
sudo mdadm --create /dev/md0 --raid-devices=2 --level=1 --metadata=0.9 /dev/sda3 missing
mdadm: /dev/sda3 appears to contain an ext2fs file system
size=1950371200K mtime=Thu Feb 16 18:27:31 1911
Continue creating array? y
mdadm: array /dev/md0 started.
cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sda3[0]
1950371200 blocks [2/1] [U_]
bitmap: 15/15 pages [60KB], 65536KB chunk
unused devices: <none>
sudo mdadm --examine /dev/sd*
/dev/sda:
MBR Magic : aa55
Partition[0] : 4980087 sectors at 63 (type fd)
Partition[1] : 1044225 sectors at 4980150 (type fd)
Partition[2] : 3900742650 sectors at 6281415 (type fd)
mdadm: No md superblock detected on /dev/sda1.
mdadm: No md superblock detected on /dev/sda2.
/dev/sda3:
Magic : a92b4efc
Version : 0.90.00
UUID : f65e01b8:f226c7c5:886f79b9:2f1f81cf (local to host yle-HP202411)
Creation Time : Fri Jan 3 16:51:29 2025
Raid Level : raid1
Used Dev Size : 1950371200 (1860.02 GiB 1997.18 GB)
Array Size : 1950371200 (1860.02 GiB 1997.18 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Fri Jan 3 16:51:29 2025
State : active
Internal Bitmap : present
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0
Checksum : 8c6f720c - correct
Events : 1
Number Major Minor RaidDevice State
this 0 8 3 0 active sync /dev/sda3
0 0 8 3 0 active sync /dev/sda3
1 0 0 0 0 spare
sudo mount /dev/md0 /mnt/disk
Hors ligne