ReadyNas Pro6 - rebuild-doesn-t-start

Old thread ( still valid )
https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/ReadyNas-Pro-6-rebuild-doesn-t-start/td-p/1650938

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 2019 System is up. Wed Oct 2 14:13:25 CEST 2019 Please 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 2019 Data volume will be rebuilt with disk 1. Wed Oct 2 09:57:34 CEST 2019 System is up. Wed Oct 2 09:47:38 CEST 2019 Please 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 2019 Data volume will be rebuilt with disk 1. Tue Oct 1 19:08:08 CEST 2019 New 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 2019 A 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.

19 Replies

Replies have been turned off for this discussion

Swetarkus2
Aspirant
Oct 02, 2019
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.

Smart log;
Device Model: ST4000DM004-2CV104
Serial Number: ZFN1V62W
LU WWN Device Id: 5 000c50 0b47633a2
Firmware Version: 0001
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
from enclosure.log
disk!!1!!status=ok::descr=Channel 1: Seagate ST33000650NS 2794 GB, 0C/32F
disk!!2!!status=ok::descr=Channel 2: ST33000650NS 2794 GB, 41C/105F
disk!!3!!status=ok::descr=Channel 3: TOSHIBA DT01ABA300 2794 GB, 36C/96F
disk!!4!!status=ok::descr=Channel 4: ST33000650NS 2794 GB, 43C/109F
disk!!5!!status=ok::descr=Channel 5: ST33000650NS 2794 GB, 46C/114F
disk!!6!!status=ok::descr=Channel 6: ST33000650NS 2794 GB, 44C/111F
- Swetarkus2
  Aspirant
  Oct 02, 2019
  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]...
- StephenB
  Guru - Experienced User
  Oct 02, 2019
  Perhaps post mdstat.log?
  - Swetarkus2
    Aspirant
    Oct 02, 2019
    Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
    md2 : active raid5 sdb3[1] sdf3[5] sde3[4] sdd3[3] sdc3[6]
    14627723520 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/5] [_UUUUU]
    
    md1 : active raid6 sdb2[1] sdf2[5] sde2[4] sdd2[3] sdc2[6]
    2096896 blocks super 1.2 level 6, 64k chunk, algorithm 2 [6/5] [_UUUUU]
    
    md0 : active raid1 sdb1[1] sdf1[5] sde1[4] sdd1[3] sdc1[6]
    4193268 blocks super 1.2 [5/5] [UUUUU]
    
    unused devices: <none>