JRA Posted July 23, 2018 Posted July 23, 2018 Hi everyone, I've a Synology rack server as our SAN here, doing something slightly odd concerning what DSM shows RAID as doing and what MDADM reckons RAID is doing! Anyone reading have any expertise this way? Just in case, the story follows... Webpage/DSM says all fine with the disks, however cat /proc/mdstat and I see the following: CODE: SELECT ALL Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md3 : active raid1 sdh1[0] sdl1[1] 468846784 blocks super 1.2 [2/2] [uU] md2 : active raid10 sda3[0] sdk3[9] sdj3[8] sdi3[7] sdg3[6] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[10] 19510982080 blocks super 1.2 64K chunks 2 near-copies [10/10] [uUUUUUUUUU] md1 : active raid1 sda2[0] sdb2[1] sdc2[2] sdd2[3] sde2[4] sdf2[5] sdg2[6] sdi2[8] sdj2[9] sdk2[10] 2097088 blocks [12/10] [uUUUUUU_UUU_] md0 : active raid1 sdk1[9] sdj1[7] sda1[0] sdb1[1] sdc1[2] sdd1[3] sde1[4] sdf1[5] sdg1[6] sdi1[8] 2490176 blocks [12/10] [uUUUUUUUUU__] unused devices: Somewhat worrying, so I dig a teensy bit: CODE: SELECT ALL mdadm -D /dev/md1 /dev/md1: Version : 0.90 Creation Time : Sat Jan 1 00:00:09 2000 Raid Level : raid1 Array Size : 2097088 (2048.28 MiB 2147.42 MB) Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB) Raid Devices : 12 Total Devices : 10 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Sun Jul 22 11:08:07 2018 State : clean, degraded Active Devices : 10 Working Devices : 10 Failed Devices : 0 Spare Devices : 0 UUID : 865d1d4d:f23ce308:c69de3af:22ddbed7 Events : 0.99 Number Major Minor RaidDevice State 0 8 2 0 active sync /dev/sda2 1 8 18 1 active sync /dev/sdb2 2 8 34 2 active sync /dev/sdc2 3 8 50 3 active sync /dev/sdd2 4 8 66 4 active sync /dev/sde2 5 8 82 5 active sync /dev/sdf2 6 8 98 6 active sync /dev/sdg2 7 0 0 7 removed 8 8 130 8 active sync /dev/sdi2 9 8 146 9 active sync /dev/sdj2 10 8 162 10 active sync /dev/sdk2 11 0 0 11 removed Weird, disks are all physically in, lights green, again the console/DSM says all fine and there's only 12 bays in it, all populated. Could this have something to do with the two SSDs for caching? Have I really just got 'regular' failed disks I need to replace? Thanks any and everyone!
JRA Posted July 23, 2018 Author Posted July 23, 2018 I now have it on good authority that this is deliberate behaviour when you have two SSDs used for caching (the 'absent' disks are indeed the SSDs) and Synology told me off for using the command line! Lool! 1
bossman Posted July 23, 2018 Posted July 23, 2018 @JRA I actually had this written up to post but got called away before I had chance to submit..... Apologies as it would have saved you getting wrong for using the CLI as Synology don't like that you have undermined their DSM system which is all you require to check your systems... Alls well that ends well though.... 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now