Duplicate device detected for

Questions about SNMP, Power, System, Logs, disk, & RAID.
Post Reply
crmdevuser
New here
Posts: 3
Joined: Thu Sep 23, 2021 10:18 pm

Duplicate device detected for

Post by crmdevuser »

Hi all , I have a TS 869 PRO in Raid 5, 7 disk + hot spare

I received this error "RAID Group recovery failed"

in ssh i do:

Code: Select all

[~] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md322 : active raid1 sdf5[7](S) sda5[0] sdh5[6](S) sdg5[5](S) sde5[4](S) sdd5[3](S) sdc5[2](S) sdb5[1]
                 7235136 blocks super 1.0 [2/2] [UU]
                 bitmap: 0/1 pages [0KB], 65536KB chunk

md13 : active raid1 sdf4[6] sda4[0] sdg4[7] sdh4[5] sde4[4] sdd4[3] sdc4[2] sdb4[1]
                 458880 blocks [12/8] [UUUUUUUU____]
                 bitmap: 1/1 pages [4KB], 65536KB chunk

md9 : active raid1 sdf1[6] sda1[0] sdg1[7] sdh1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1]
                 530048 blocks [12/8] [UUUUUUUU____]
                 bitmap: 1/1 pages [4KB], 65536KB chunk

unused devices: <none>

Code: Select all

[~] # df -h
Filesystem                Size      Used Available Use% Mounted on
none                    200.0M    183.3M     16.7M  92% /
devtmpfs                  1.5G      8.0K      1.5G   0% /dev
tmpfs                    64.0M    636.0K     63.4M   1% /tmp
tmpfs                     1.5G         0      1.5G   0% /dev/shm
tmpfs                    16.0M         0     16.0M   0% /share
/dev/md9                509.5M    166.6M    342.8M  33% /mnt/HDA_ROOT
cgroup_root               1.5G         0      1.5G   0% /sys/fs/cgroup
/dev/md13               371.0M    336.5M     34.5M  91% /mnt/ext
/dev/ram2               433.9M      2.3M    431.6M   1% /mnt/update
tmpfs                    64.0M      2.4M     61.6M   4% /samba
tmpfs                    16.0M     28.0K     16.0M   0% /samba/.samba/lock/msg.lock
tmpfs                    16.0M         0     16.0M   0% /mnt/ext/opt/samba/private/msg.sock
tmpfs                     1.0M         0      1.0M   0% /mnt/rf/nd

Code: Select all

[~] # md_checker

Welcome to MD superblock checker (v1.4) - have a nice day~

Scanning system...

HAL firmware detected!
Scanning Enclosure 0...

RAID metadata found!
UUID:           d2415754:719330c6:e32781cd:40701f19
Level:          raid5
Devices:        7
Name:           md2
Chunk Size:     64K
md Version:     1.0
Creation Time:  Jul 21 12:18:00 2014
Status:         OFFLINE
===============================================================================
 Disk | Device | # | Status |   Last Update Time   | Events | Array State
===============================================================================
   1  /dev/sda3  0  Rebuild   Sep 15 10:05:29 2021 38563934   AAAAARA
   2  /dev/sdb3  1   Active   Sep 15 10:05:29 2021 38563934   AAAAARA
   3  /dev/sdc3  2   Active   Sep 15 10:05:29 2021 38563934   AAAAARA
   4  /dev/sdd3  3   Active   Sep 15 10:05:29 2021 38563934   AAAAARA
   5  /dev/sde3  4   Active   Sep 15 10:05:29 2021 38563934   AAAAARA
   6  /dev/sdf3  5   Active   Sep 15 09:56:09 2021 38556715   AAAAAAA
   8  /dev/sdh3  5  Rebuild   Sep 15 10:05:29 2021 38563934   AAAAARA
   7  /dev/sdg3  6   Active   Sep 15 10:05:29 2021 38563934   AAAAARA
===============================================================================
 WARNING: Duplicate device detected for #(5)!
What i have to do?
Last edited by OneCD on Fri Sep 24, 2021 3:17 am, edited 1 time in total.
Reason: added code tags
User avatar
dolbyman
Guru
Posts: 35248
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: Duplicate device detected for

Post by dolbyman »

any backstory to this ? .. what happened ?
crmdevuser
New here
Posts: 3
Joined: Thu Sep 23, 2021 10:18 pm

Re: Duplicate device detected for

Post by crmdevuser »

First the disk 6 got error so we substitute it, suddently after the disk 1 gave error and we try to substitute also this
we don't know when the status goes offline.
later we reinserted the original discs
User avatar
dolbyman
Guru
Posts: 35248
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: Duplicate device detected for

Post by dolbyman »

so you had a raid5 with 2 failed drives ... raid5 can only survive 1 failed drive ...you will have to resort to backups
Thisisnotmyname
Easy as a breeze
Posts: 447
Joined: Mon Nov 19, 2018 1:21 am

Re: Duplicate device detected for

Post by Thisisnotmyname »

Adding here some best practice information. With modern large size spinning disks it is no longer recommended that single parity (RAID5/RAIDz) be used. The chances that if you lose one drive you would then lose a second drive (and thus the entire array) during a rebuilt are significantly high. If you are using modern multi-TB drives I'd recommend you at least use double parity (RAID6/RAIDz2) or higher. Also look at URE rates of your drives, if you purchase 18TB drives with URE rate of 1x10^14 for example (I don't know whether that's an existing combination, this is an example) there's a very high chance you'll have a URE during rebuild and fail.
crmdevuser
New here
Posts: 3
Joined: Thu Sep 23, 2021 10:18 pm

Re: Duplicate device detected for

Post by crmdevuser »

dolbyman wrote: Fri Sep 24, 2021 7:41 pm so you had a raid5 with 2 failed drives ... raid5 can only survive 1 failed drive ...you will have to resort to backups
drive 6 seems to be ready, Can i get out drive 8 and put online the array ?
Post Reply

Return to “System & Disk Volume Management”