Hi everyone
I'm recreating the topic because the original one was in the wrong section and also hard to read.
I bought 2 Seagate Ironwolf 6TB and I created a RAID1.
After that I immediately shared it and copied 1TB of files on it.
After that I had to reboot my NAS, and I found that the RAID1 was gone!
I tried to see with gparted what was happening, and I saw that both the 6TB hard drive didn't even have a partion, it was like I never created and ext4 RAID1.
I checked like tkaiser suggest me if my usb key had problem with f3 and the result is fine.
I'll post here everything:. The RAID1 that disappeared was made with 2 Ironwolf 6TB
- cat /proc/mdsta
Code
root@Delibird:~# cat /proc/mdstat
Personalities : [raid1]
md127 : active raid1 sdb[0] sda[1]
3906887360 blocks super 1.2 [2/2] [UU]
unused devices: <none>
- blkid
Code
root@Delibird:~# blkid
/dev/sda: UUID="ed696fd2-96fe-ba4f-ab44-fb72b800fb01" UUID_SUB="05959c09-ecb2-6cf8-facc-6603333b02f6" LABEL="NAS:Data" TYPE="linux_raid_member"
/dev/sdb: UUID="ed696fd2-96fe-ba4f-ab44-fb72b800fb01" UUID_SUB="47bf0e53-a2c5-2b44-1db5-c0e2eadf7300" LABEL="NAS:Data" TYPE="linux_raid_member"
/dev/sde1: LABEL="Test1" UUID="e2e97456-a32f-4c7b-82f2-8ba5d8320dc1" TYPE="ext4" PARTLABEL="HDDTest" PARTUUID="c3e5ef33-dd1a-46d5-84bc-d66470473ed3"
/dev/sde2: LABEL="Test2" UUID="b34f8189-6a4e-4a02-bcf0-1fc73641d055" TYPE="ext4" PARTLABEL="HDDTest" PARTUUID="dfdbab85-4777-416e-8f09-51e55840336b"
/dev/md127: LABEL="Dati" UUID="8d1d82dc-45af-438d-9c7c-271640aed5b2" TYPE="ext4"
/dev/sdf1: UUID="3ea78407-b370-43c7-ae25-290c365a4927" TYPE="ext4" PARTUUID="a94754ac-01"
/dev/sdf5: UUID="462536b4-33a7-439b-8ed3-13e27998acdb" TYPE="swap" PARTUUID="a94754ac-05"
/dev/sdc: PTUUID="8defa52c-34a0-4c6e-8508-3c922ba3807d" PTTYPE="gpt"
/dev/sdd: PTUUID="36911ee8-885f-4a0e-8662-a913cd447094" PTTYPE="gpt"
- fdisk -l | grep "Disk "
Code
root@Delibird:~# fdisk -l | grep "Disk "
Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk /dev/sdc: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
Disk identifier: 8DEFA52C-34A0-4C6E-8508-3C922BA3807D
Disk /dev/sdd: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
Disk identifier: 36911EE8-885F-4A0E-8662-A913CD447094
Disk /dev/sde: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk identifier: 62DA6565-E8B7-4E50-AF25-0DA69B3B5CB4
Disk /dev/md127: 3.7 TiB, 4000652656640 bytes, 7813774720 sectors
Disk /dev/sdf: 14.3 GiB, 15376000000 bytes, 30031250 sectors
Disk identifier: 0xa94754ac
Alles anzeigen
- cat /etc/mdadm/mdadm.conf
Code
root@Delibird:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# definitions of existing MD arrays
ARRAY /dev/md127 metadata=1.2 name=NAS:Data UUID=ed696fd2:96feba4f:ab44fb72:b800fb01
# instruct the monitoring daemon where to send mail alerts
MAILADDR pestotosto@outlook.com
Alles anzeigen
- mdadm --detail --scan --verbose