mdj156

Don't mean to hijack your thread, but I am having the same issues as well, only the GUI errors were different - the system partition was corrupted. Did you try the latest Ubuntu from http://www.ubuntu.com/download/desktop ? I was able to boot with that perfectly, after creating it with Rufus usb Tool. My Mdadm output is this: BusyBox v1.16.1 (2015-11-12 18:06:25 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. NAS> cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md2 : active raid5 sda5[0] sdc3[2] sdb3[1] 5846049792 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [uUU_] md3 : active raid1 sdb4[0] sdc4[1] 976702592 blocks super 1.2 [2/2] [uU] md1 : active raid1 sdd2[3] sdc2[2] sdb2[1] sda2[0] 2097088 blocks [12/4] [uUUU________] md0 : active raid1 sdd1[3] sda1[0] sdb1[1] sdc1[2] 2490176 blocks [12/4] [uUUU________] unused devices: NAS> mdadm --detail /dev/md0 /dev/md0: Version : 0.90 Creation Time : Tue May 3 20:08:11 2016 Raid Level : raid1 Array Size : 2490176 (2.37 GiB 2.55 GB) Used Dev Size : 2490176 (2.37 GiB 2.55 GB) Raid Devices : 12 Total Devices : 4 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Tue May 24 22:26:13 2016 State : clean, degraded Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 UUID : 2ff4a715:bb0bc725:3017a5a8:c86610be Events : 0.42971 Number Major Minor RaidDevice State 0 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1 2 8 33 2 active sync /dev/sdc1 3 8 49 3 active sync /dev/sdd1 4 0 0 4 removed 5 0 0 5 removed 6 0 0 6 removed 7 0 0 7 removed 8 0 0 8 removed 9 0 0 9 removed 10 0 0 10 removed 11 0 0 11 removed NAS> mdadm --detail /dev/md1 /dev/md1: Version : 0.90 Creation Time : Tue May 24 22:16:55 2016 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 : 4 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Tue May 24 22:17:36 2016 State : active, degraded Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 UUID : 0c471b1c:73a4ead1:cced5de7:ca715931 (local to host NAS) Events : 0.19 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 0 0 4 removed 5 0 0 5 removed 6 0 0 6 removed 7 0 0 7 removed 8 0 0 8 removed 9 0 0 9 removed 10 0 0 10 removed 11 0 0 11 removed NAS> mdadm --detail /dev/md2 /dev/md2: Version : 1.2 Creation Time : Fri Feb 20 19:52:31 2015 Raid Level : raid5 Array Size : 5846049792 (5575.23 GiB 5986.35 GB) Used Dev Size : 1948683264 (1858.41 GiB 1995.45 GB) Raid Devices : 4 Total Devices : 3 Persistence : Superblock is persistent Update Time : Tue May 24 22:23:19 2016 State : clean, degraded Active Devices : 3 Working Devices : 3 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Name : NAS:2 (local to host NAS) UUID : 8fcc7e7b:1ec18766:628f40c5:d73e88ef Events : 249 Number Major Minor RaidDevice State 0 8 5 0 active sync /dev/sda5 1 8 19 1 active sync /dev/sdb3 2 8 35 2 active sync /dev/sdc3 3 0 0 3 removed NAS> mdadm --detail /dev/md3 /dev/md3: Version : 1.2 Creation Time : Fri Feb 20 19:52:31 2015 Raid Level : raid1 Array Size : 976702592 (931.46 GiB 1000.14 GB) Used Dev Size : 976702592 (931.46 GiB 1000.14 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Update Time : Tue May 24 22:23:21 2016 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : NAS:3 (local to host NAS) UUID : 7f9dd02e:c98c9a71:c6e96c71:e8d6eae6 Events : 2 Number Major Minor RaidDevice State 0 8 20 0 active sync /dev/sdb4 1 8 36 1 active sync /dev/sdc4 NAS>

Well, took a chance which turned ok. I formatted all the first 2 system partitions of all the disks. After reboot performed a install XPEnoboot, and the diskstation was found and accessible again - with configuration lost. Installed DSM again, I did get a warning which stated that all data would be lost..but after reboot data was still intact.

From what I read, it should be fine. I ordered a new MSI mobo with B150 chipset and the same CPU, I'll let you know if it is working.

Hi, I've been using the XPenology solution for quite some time now, unfortunately after creating some rename scripts the GUI/SSH became inaccessible. The debug option showed a kernel panic and I am unable to access the unit in any way. Is there a way to reset the system partition and reinstall the DSM software and preserving data? Would deleting the smaller partitions do the trick, I suspect that the larger ones are actually the user data? Or just completely wipe all drives and start all over?