Having previously tried with 2 different 3TB HD's to start a rebuild, thought maybe it could be size? So,, got a 4TB to be on the safe side, but - same issue. Rebuild doesn't start. Shut the box down, took out all drives, left powerless for 15min, inserted everything and tried again - no difference. On the LCD display, it does start new drive found - new drive being tested - new drive passed, etc, but still, the Readynas does NOT start a rebuild whatever I do.
NOTES; While drive removal / reinstall is noted correctly BOTH hotswap and power off/on, the data about the drive inserted doesn't get updated and still shows the drive that failed over 2 years ago. This regardless of whatever drive I install.
From Raidiator;
Data volume will be rebuilt with disk 1.Wed Oct 2 14:55:09 CEST 2019System is up.Wed Oct 2 14:13:25 CEST 2019Please close this browser session and use RAIDar to reconnect to the device after it is powered back on. System powering off...Wed Oct 2 09:58:23 CEST 2019Data volume will be rebuilt with disk 1.Wed Oct 2 09:57:34 CEST 2019System is up.Wed Oct 2 09:47:38 CEST 2019Please close this browser session and use RAIDar to reconnect to the device after it is powered back on. System powering off...Tue Oct 1 19:09:15 CEST 2019Data volume will be rebuilt with disk 1.Tue Oct 1 19:08:08 CEST 2019New disk detected. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time. [Disk 1]Tue Oct 1 19:02:15 CEST 2019A disk was removed from the ReadyNAS. One or more RAID volumes are currently unprotected, and an additional disk failure or removal may result in data loss. Please add a replacement disk as soon as possible.
Interesting additional info; Did the download all logs, from disk_smart_log, I can see all drives of correct size and model, in the enclosure.log file - there it still states the model and size for the drive that died 2 years ago.
Additional info again then; The failed drive is drive 0, /sda; checking expansion.log, seems I've got a known issue, or at least not the first to have it; Something about readynas DO seeing and talking with the drive but doing something wrong when creating required partition on it;
sfdisk: no partition table present. [2019/10/02 17:10:16 2040] Input target disk 4K align partition problem: 256, use old partition. [2019/10/02 17:10:16 2040] LINE 3723: exec command: sfdisk --force -L /dev/sda < /var/log/frontview/.known_cfgdir/75UA76PGS
Disk /dev/sda: 486401 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature /dev/sda: unrecognized partition table type Old situation: No partitions found New situation: No partitions found
sfdisk: no partition table present. [2019/10/02 17:10:16 2040] LINE 3730: exec command: sgdisk -g -a 8 /dev/sda Creating new GPT entries. The operation has completed successfully. [2019/10/02 17:10:19 2040] Succeed to convert mbr to gpt /dev/sdb. [2019/10/02 17:10:19 2040] Input target disk partition problem: 256 [2019/10/02 17:10:19 2040] Failed to add disk to md [2019/10/02 17:10:19 2040] Added drive to md, grown=0/0xff830f18 [2019/10/02 17:10:19 2040] LINE 4852: exec command: /usr/sbin/expand_md -a super >> /var/log/frontview/expand_md.log 2>&1 & [2019/10/02 17:10:19 2040] LINE 4855: exec command: /frontview/bin/volumescan &
[2019/10/02 17:10:19 2040] LINE 4939: exec command: ps -ef | grep expand_md | grep -v grep > /var/log/frontview/.V_E.snapshotstat [2019/10/02 17:10:19 2040] STAGE_WIPE: Clean my_pid 2040 [2019/10/02 17:10:20 3472] STAGE_CHECK: saved my_pid 3472 in check mode. [2019/10/02 17:10:20 3472] RAID MODE: 1, sn= [2019/10/02 17:10:20 3472] LINE 4591: exec command: lvs > /var/log/frontview/.V_E.snapshotstat [2019/10/02 17:10:20 3472] Current file system status: ext4 [2019/10/02 17:10:20 3472] LINE 5305: exec command: rm -fr /var/log/frontview/.V_E.* [2019/10/02 17:10:20 3472] Running disk SMART quick self-test on new disk 1 [/dev/sda]...
md0 : active raid1 sdb1[1] sdf1[5] sde1[4] sdd1[3] sdc1[6] 4193268 blocks super 1.2 [5/5] [UUUUU]
unused devices: <none>
Interesting thing from expansion.log, google'd this and saw that others have had the same issue;
sfdisk: no partition table present. [2019/10/02 17:10:16 2040] Input target disk 4K align partition problem: 256, use old partition. [2019/10/02 17:10:16 2040] LINE 3723: exec command: sfdisk --force -L /dev/sda < /var/log/frontview/.known_cfgdir/75UA76PGS
Disk /dev/sda: 486401 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature /dev/sda: unrecognized partition table type Old situation: No partitions found New situation: No partitions found
sfdisk: no partition table present. [2019/10/02 17:10:16 2040] LINE 3730: exec command: sgdisk -g -a 8 /dev/sda Creating new GPT entries. The operation has completed successfully. [2019/10/02 17:10:19 2040] Succeed to convert mbr to gpt /dev/sdb. [2019/10/02 17:10:19 2040] Input target disk partition problem: 256 [2019/10/02 17:10:19 2040] Failed to add disk to md [2019/10/02 17:10:19 2040] Added drive to md, grown=0/0xff830f18 [2019/10/02 17:10:19 2040] LINE 4852: exec command: /usr/sbin/expand_md -a super >> /var/log/frontview/expand_md.log 2>&1 & [2019/10/02 17:10:19 2040] LINE 4855: exec command: /frontview/bin/volumescan &
[2019/10/02 17:10:19 2040] LINE 4939: exec command: ps -ef | grep expand_md | grep -v grep > /var/log/frontview/.V_E.snapshotstat [2019/10/02 17:10:19 2040] STAGE_WIPE: Clean my_pid 2040 [2019/10/02 17:10:20 3472] STAGE_CHECK: saved my_pid 3472 in check mode. [2019/10/02 17:10:20 3472] RAID MODE: 1, sn= [2019/10/02 17:10:20 3472] LINE 4591: exec command: lvs > /var/log/frontview/.V_E.snapshotstat [2019/10/02 17:10:20 3472] Current file system status: ext4 [2019/10/02 17:10:20 3472] LINE 5305: exec command: rm -fr /var/log/frontview/.V_E.* [2019/10/02 17:10:20 3472] Running disk SMART quick self-test on new disk 1 [/dev/sda]...
well, it first looks as if the post/reply back is ok, then in say 10 sec's, forum comes back with "forbidden" i red. Haven't tried unformatting, could do of course,, but this now is the 3rd brand new, unopened HD causing the same thing...
Given that the drives are Seagate, there's always the risk that WD's SW wont help, but either way; SSH to the box, I've deleted any partition on this new drive, making it very empty - to no avail. This quick erase or any form of format, doable via CLI ?
Somehow, the Readynas both understands this new drive to be a 4tb drive and yet,, does NOT understand it; Last login: Wed Oct 2 16:49:59 2019 from 192.168.68.10 Last login: Wed Oct 2 21:31:25 2019 from 192.168.68.10 on pts/0 Linux Ekero-Nas2 2.6.37.6.RNx86_64.2.4 #1 SMP Thu May 28 16:29:46 PDT 2015 x86_6 4 GNU/Linux Ekero-Nas2:~# fdisk -l | grep '^Disk' fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sda: 4294967295 sectors, 2047G Disk identifier (GUID): 7beecc0d-c191-41fa-ba25-84757a1e644a fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sdb: 4294967295 sectors, 2047G Disk identifier (GUID): b1a2854e-5c9e-4373-8633-5c8bf3e94b9d fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sdc: 4294967295 sectors, 2047G Disk identifier (GUID): 4f9c97ab-f4d3-49b2-95d4-723816a2a657 fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sdd: 4294967295 sectors, 2047G Disk identifier (GUID): d7b07bd9-eebc-434a-9579-3e83e7c8bcc9 fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sde: 4294967295 sectors, 2047G Disk identifier (GUID): 77b79d32-5dc4-488c-b950-cf91f039de76 fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sdf: 4294967295 sectors, 2047G Disk identifier (GUID): 464bc1b1-dc96-4724-ac15-fb4636677e7b Disk /dev/md0: 4293 MB, 4293906432 bytes Disk /dev/md0 doesn't contain a valid partition table Disk /dev/dm-0: 2199.0 GB, 2199023255040 bytes Disk /dev/dm-0 doesn't contain a valid partition table Ekero-Nas2:~#
The SDA, disk0, should be seen as 4tb and not 3tb.
Also - I am assuming that you are inserting the disk in slot 1 (sda). Please post back if that's not the case.
mdstat shows [6/5] [_UUUUU]for md1 and md2. sda is missing from the list, but the _ means that mdadm is expecting to see it as part of the volume. Note md0 is a bit different - [5/5] [UUUUU] - showing that the NAS didn't attempt to add sda to the OS partition.
Given that the drives are Seagate, there's always the risk that WD's SW wont help
Seagate's Seatools also has a "write zeros" advanced test you can use. Lifeguard's quick erase is faster (it zeros some sectors at the beginning and end of the disk, which is enough to delete all partition information).
well, it's the 1st disk in the first slot, and given that all other drives are 3tb and this one's 4tb, looks safe to assume that it's SDA.
question is; why is Readynas failing with 3 different, all brand new, HD's ? Should be some work-around....I know,, a unit way after warranty, but still.
question is; why is Readynas failing with 3 different, all brand new, HD's ? Should be some work-around....I know,, a unit way after warranty, but still.
One obvious thing is to see if the sata interface in that slot has failed. That does happen sometimes.
The way to test that is to power down, removing all the disks, and insert a blank new one in slot 2 (other slots empty). Then power up, and let the system do a fresh factory install. Check that the system is working normally.
Then power down the NAS, shift that disk to slot 1, and reboot. If the system boots successfully, then make sure that you can read/write to the data volume.
Another possibility (less likely IMO) is that this is power-related. It's possible that the PSU is marginal, and no longer able to reliably power all 6 disks at once.
I think the sata connector, slot and PS seems to be working. Via SSH, connected and ran a reformat/write-zeros overwrite on the new drive which took quite some hours. Then rebooted and still same issue.
My "personal" hang-up on this; System in disk_smart.logm expansion and partition.log reports the drive correctly as a new 4TB seagate drive, but then enclosure.log still states the old 3tb drive that's gone.
How far back (OS versions) was your volume created? I recall there being a point at which one had to do a factory default in order to be able to use 4K sector drives.
Can't remember actually,,, it's been a while for sure so no can't pinpoint when it was that I set it up. But,, since it's failing also with the 3k drive which is the exact same space and series as the exisiting ones, it feels like that shouldn't be the issue.
***** partition output for sda *****
Disk /dev/sda: 7814037168 sectors, 3.6 TiB Logical sector size: 512 bytes Disk identifier (GUID): E023799C-2F0E-481F-80F6-CFE01051657D Partition table holds up to 128 entries First usable sector is 34, last usable sector is 7814037134 Partitions will be aligned on 2048-sector boundaries Total free space is 7814037101 sectors (3.6 TiB)
Number Start (sector) End (sector) Size Code Name
Disk /dev/sda: 486401 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8257536 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System /dev/sda1 0+ - 0- 2147483647+ ee EFI GPT /dev/sda2 0 - 0 0 0 Empty /dev/sda3 0 - 0 0 0 Empty /dev/sda4 0 - 0 0 0 Empty
***** partition output for sdb *****
Disk /dev/sdb: 5860533168 sectors, 2.7 TiB Logical sector size: 512 bytes Disk identifier (GUID): B1A2854E-5C9E-4373-8633-5C8BF3E94B9D Partition table holds up to 128 entries First usable sector is 34, last usable sector is 5860533134 Partitions will be aligned on 64-sector boundaries Total free space is 4092 sectors (2.0 MiB)
Number Start (sector) End (sector) Size Code Name 1 64 8388671 4.0 GiB FD00 2 8388672 9437247 512.0 MiB FD00 3 9437248 5860529072 2.7 TiB FD00
Disk /dev/sdb: 364801 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8257536 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System /dev/sdb1 0+ - 0- 2147483647+ ee EFI GPT /dev/sdb2 0 - 0 0 0 Empty /dev/sdb3 0 - 0 0 0 Empty /dev/sdb4 0 - 0 0 0 Empty
***** partition output for sdc *****
Disk /dev/sdc: 5860533168 sectors, 2.7 TiB Logical sector size: 512 bytes Disk identifier (GUID): 4F9C97AB-F4D3-49B2-95D4-723816A2A657 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 5860533134 Partitions will be aligned on 64-sector boundaries Total free space is 4092 sectors (2.0 MiB)
Number Start (sector) End (sector) Size Code Name 1 64 8388671 4.0 GiB FD00 2 8388672 9437247 512.0 MiB FD00 3 9437248 5860529072 2.7 TiB FD00
Disk /dev/sdc: 364801 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8257536 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System /dev/sdc1 0+ - 0- 2147483647+ ee EFI GPT /dev/sdc2 0 - 0 0 0 Empty /dev/sdc3 0 - 0 0 0 Empty /dev/sdc4 0 - 0 0 0 Empty
***** partition output for sdd *****
Disk /dev/sdd: 5860533168 sectors, 2.7 TiB Logical sector size: 512 bytes Disk identifier (GUID): D7B07BD9-EEBC-434A-9579-3E83E7C8BCC9 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 5860533134 Partitions will be aligned on 64-sector boundaries Total free space is 4092 sectors (2.0 MiB)
Number Start (sector) End (sector) Size Code Name 1 64 8388671 4.0 GiB FD00 2 8388672 9437247 512.0 MiB FD00 3 9437248 5860529072 2.7 TiB FD00
Disk /dev/sdd: 364801 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8257536 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System /dev/sdd1 0+ - 0- 2147483647+ ee EFI GPT /dev/sdd2 0 - 0 0 0 Empty /dev/sdd3 0 - 0 0 0 Empty /dev/sdd4 0 - 0 0 0 Empty
***** partition output for sde *****
Disk /dev/sde: 5860533168 sectors, 2.7 TiB Logical sector size: 512 bytes Disk identifier (GUID): 77B79D32-5DC4-488C-B950-CF91F039DE76 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 5860533134 Partitions will be aligned on 64-sector boundaries Total free space is 4092 sectors (2.0 MiB)
Number Start (sector) End (sector) Size Code Name 1 64 8388671 4.0 GiB FD00 2 8388672 9437247 512.0 MiB FD00 3 9437248 5860529072 2.7 TiB FD00
Disk /dev/sde: 364801 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8257536 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System /dev/sde1 0+ - 0- 2147483647+ ee EFI GPT /dev/sde2 0 - 0 0 0 Empty /dev/sde3 0 - 0 0 0 Empty /dev/sde4 0 - 0 0 0 Empty
***** partition output for sdf *****
Disk /dev/sdf: 5860533168 sectors, 2.7 TiB Logical sector size: 512 bytes Disk identifier (GUID): 464BC1B1-DC96-4724-AC15-FB4636677E7B Partition table holds up to 128 entries First usable sector is 34, last usable sector is 5860533134 Partitions will be aligned on 64-sector boundaries Total free space is 4092 sectors (2.0 MiB)
Number Start (sector) End (sector) Size Code Name 1 64 8388671 4.0 GiB FD00 2 8388672 9437247 512.0 MiB FD00 3 9437248 5860529072 2.7 TiB FD00
Disk /dev/sdf: 364801 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8257536 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System /dev/sdf1 0+ - 0- 2147483647+ ee EFI GPT /dev/sdf2 0 - 0 0 0 Empty /dev/sdf3 0 - 0 0 0 Empty /dev/sdf4 0 - 0 0 0 Empty
I think the sata connector, slot and PS seems to be working. Via SSH, connected and ran a reformat/write-zeros overwrite on the new drive which took quite some hours. Then rebooted and still same issue.
I stiill suggest the test I proposed above - a factory install on a single disk in slot 2, then see if it boots in slot 1.
