I've added a a 5th Drive lately and initialised it tried to create Volume. Due to too many disk failures it couldn't be created.
Adding the Drive during operation worked quite well.
Unplugging the Drive during usage without removing it first in DSM didnt work well.
I'm now stuck on Running NAS with SSH enable but Webpage is down and can't access via Samba... i assume the DSM which is cloned on each disk is somehow ******* up (Seriously... isn't that why it's cloned on ALL disks so this DOESNT happen? -.-)
So anyone has a Disaster recovery guid handy i could try to get this stuff working again?
Repluging the 5th HDD did not help.
Any other ideas except reinstalling DSM via Loader?
Here s a output from fdisk.... just in case.
fdisk output
ash-4.3# fdisk -l
Disk /dev/sda: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
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: gpt
Disk identifier: 6E64C596-1EEE-4E32-8713-2D8BE2212912
Device Start End Sectors Size Type
/dev/sda1 2048 4982527 4980480 2.4G Linux RAID
/dev/sda2 4982528 9176831 4194304 2G Linux RAID
/dev/sda3 9437184 11720840351 11711403168 5.5T Linux RAID
Disk /dev/sdb: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
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: gpt
Disk identifier: C40B80C5-1B54-4C4B-9DB8-BB7358FE965C
Device Start End Sectors Size Type
/dev/sdb1 2048 4982527 4980480 2.4G Linux RAID
/dev/sdb2 4982528 9176831 4194304 2G Linux RAID
/dev/sdb3 9437184 11720840351 11711403168 5.5T Linux RAID
Disk /dev/sdc: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
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: gpt
Disk identifier: FE50AFAD-F6F8-46D4-B69E-DBAFA5A43D39
Device Start End Sectors Size Type
/dev/sdc1 2048 4982527 4980480 2.4G Linux RAID
/dev/sdc2 4982528 9176831 4194304 2G Linux RAID
/dev/sdc3 9437184 11720840351 11711403168 5.5T Linux RAID
Disk /dev/sdd: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
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: gpt
Disk identifier: B7A01EEE-916D-4DE3-B17C-109626623B0D
Device Start End Sectors Size Type
/dev/sdd1 2048 4982527 4980480 2.4G Linux RAID
/dev/sdd2 4982528 9176831 4194304 2G Linux RAID
/dev/sdd3 9437184 11720840351 11711403168 5.5T Linux RAID
Disk /dev/sde: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xdc5adc5a
Device Boot Start End Sectors Size Id Type
/dev/sde1 2048 4982527 4980480 2.4G fd Linux raid autodetect
/dev/sde2 4982528 9176831 4194304 2G fd Linux raid autodetect
/dev/sde3 9437184 976568351 967131168 461.2G fd Linux raid autodetect
GPT PMBR size mismatch (102399 != 7860223) will be corrected by w(rite).
Disk /dev/synoboot: 3.8 GiB, 4024434688 bytes, 7860224 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C94E55EA-A4D2-4E78-9D73-46CBAE7A03EF
Device Start End Sectors Size Type
/dev/synoboot1 2048 32767 30720 15M EFI System
/dev/synoboot2 32768 94207 61440 30M Linux filesystem
/dev/synoboot3 94208 102366 8159 4M BIOS boot
Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/zram0: 1.1 GiB, 1194328064 bytes, 291584 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/zram1: 1.1 GiB, 1194328064 bytes, 291584 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
ash-4.3#
Question
haldi
Howdy,
I've added a a 5th Drive lately and initialised it tried to create Volume. Due to too many disk failures it couldn't be created.
Adding the Drive during operation worked quite well.
Unplugging the Drive during usage without removing it first in DSM didnt work well.
I'm now stuck on Running NAS with SSH enable but Webpage is down and can't access via Samba... i assume the DSM which is cloned on each disk is somehow ******* up (Seriously... isn't that why it's cloned on ALL disks so this DOESNT happen? -.-)
So anyone has a Disaster recovery guid handy i could try to get this stuff working again?
Repluging the 5th HDD did not help.
Any other ideas except reinstalling DSM via Loader?
Here s a output from fdisk.... just in case.
P.S Running a HP Microserver Gen8
Link to comment
Share on other sites
10 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.