Increase storage space, disk 2 Inactive

[huffie]

After I got my Disk 1 to synchronize, I swap out Disk 2 and replaced with a higher capacity but now there is no activity. Status for Disk 2 is Inactive and Raid 1 is Degraded. Can someone advise me how do I trigger to synchronize Disk 2? Thanks.
Model: AS302-T
Upgrade: 3TB -> 6TB
ADM Ver: 2.6.5.R9N1

[orion]

Normally NAS should rebuild RAID-1 volume when you plugged disk-2 back to NAS. Did you do this action when NAS is working? Are there any errors under ADM web -> System Information -> Log?
If everything is fine, I think you should send a support request to asustor. http://support.asustor.com/

[huffie]

Hi Orion, yes that was I expected after plugging in the 2nd 6TB drive, however it just reflected Inactive. No error message from Log, it states "Disk plugged in to slot 2." and that was it. Yeah, have submitted a ticket to asustor and awaiting their response. Was tempted to use mdadm to rebuild but think I just see what asustor reply is.

Thanks!

[huffie]

by the way.. here is a log from /var/log/messages after slot 2 was inserted

Code: Select all

2016-10-10T07:29:43.855342+08:00 AS-302T-F98A kernel: [40473.793835] ata1: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
2016-10-10T07:29:43.855390+08:00 AS-302T-F98A kernel: [40473.801237] ata1: irq_stat 0x00400040, connection status changed
2016-10-10T07:29:43.867203+08:00 AS-302T-F98A kernel: [40473.807396] ata1: SError: { HostInt PHYRdyChg 10B8B DevExch }
2016-10-10T07:29:43.867272+08:00 AS-302T-F98A kernel: [40473.813152] ata1: hard resetting link
2016-10-10T07:29:44.600279+08:00 AS-302T-F98A kernel: [40474.539614] ata1: SATA link down (SStatus 0 SControl 300)
2016-10-10T07:29:49.601728+08:00 AS-302T-F98A kernel: [40479.534977] ata1: hard resetting link
2016-10-10T07:29:49.923635+08:00 AS-302T-F98A kernel: [40479.854507] ata1: SATA link down (SStatus 0 SControl 300)
2016-10-10T07:29:54.925793+08:00 AS-302T-F98A kernel: [40484.850439] ata1: hard resetting link
2016-10-10T07:29:55.248535+08:00 AS-302T-F98A kernel: [40485.171233] ata1: SATA link down (SStatus 0 SControl 300)
2016-10-10T07:29:55.248607+08:00 AS-302T-F98A kernel: [40485.176719] ata1.00: disabled
2016-10-10T07:29:55.259173+08:00 AS-302T-F98A kernel: [40485.179813] ata1: EH complete
2016-10-10T07:29:55.259223+08:00 AS-302T-F98A kernel: [40485.182838] ata1.00: detaching (SCSI 0:0:0:0)
2016-10-10T07:29:55.273626+08:00 AS-302T-F98A kernel: [40485.196347] invalidate_partition: scsi device is invalid
2016-10-10T07:29:55.300347+08:00 AS-302T-F98A kernel: [40485.216948] raid1_end_read_request: 8 callbacks suppressed
2016-10-10T07:29:55.300416+08:00 AS-302T-F98A kernel: [40485.222425] md/raid1:md0: sda2: rescheduling sector 456016
2016-10-10T07:29:55.340126+08:00 AS-302T-F98A kernel: [40485.256182] md/raid1:md0: Disk failure on sda2, disabling device.
2016-10-10T07:29:55.340231+08:00 AS-302T-F98A kernel: [40485.256189] md/raid1:md0: Operation continuing on 1 devices.
2016-10-10T07:29:55.340266+08:00 AS-302T-F98A kernel: [40485.268160] handle_read_error: 8 callbacks suppressed
2016-10-10T07:29:55.352094+08:00 AS-302T-F98A kernel: [40485.273246] md/raid1:md0: redirecting sector 456016 to other mirror: sdb2
2016-10-10T07:29:55.372841+08:00 AS-302T-F98A kernel: [40485.294780] md: remove_and_add_spares rdev sda2 disk 0 0 1 0 0
2016-10-10T07:29:55.373019+08:00 AS-302T-F98A kernel: [40485.300862] md: remove_and_add_spares bdev /dev/sda2 exist
2016-10-10T07:29:55.399662+08:00 AS-302T-F98A kernel: [40485.321707] md: remove_and_add_spares rdev sda2 remove sucess
2016-10-10T07:29:57.384644+08:00 AS-302T-F98A kernel: [40487.304054] invalidate_partition: scsi device is invalid
2016-10-10T07:29:58.535566+08:00 AS-302T-F98A kernel: [40488.436550] end_request: I/O error, dev sda, sector 8
2016-10-10T07:29:58.535662+08:00 AS-302T-F98A kernel: [40488.441576] md: super_written gets error=-5, uptodate=0
2016-10-10T07:29:58.535678+08:00 AS-302T-F98A kernel: [40488.446774] md/raid1:md1: Disk failure on sda4, disabling device.
2016-10-10T07:29:58.535690+08:00 AS-302T-F98A kernel: [40488.446777] md/raid1:md1: Operation continuing on 1 devices.
2016-10-10T07:29:58.572209+08:00 AS-302T-F98A kernel: [40488.489282] md: remove_and_add_spares rdev sda4 disk 0 0 1 0 0
2016-10-10T07:29:58.572281+08:00 AS-302T-F98A kernel: [40488.495146] md: remove_and_add_spares bdev /dev/sda4 not exist
2016-10-10T07:29:58.596656+08:00 AS-302T-F98A kernel: [40488.513664] md: remove_and_add_spares rdev sda4 remove sucess
2016-10-10T07:29:59.472567+08:00 AS-302T-F98A kernel: [40489.388656] invalidate_partition: scsi device is invalid
2016-10-10T07:30:01.556433+08:00 AS-302T-F98A kernel: [40491.469327] invalidate_partition: scsi device is invalid
2016-10-10T07:30:03.640439+08:00 AS-302T-F98A kernel: [40493.550041] invalidate_partition: scsi device is invalid
2016-10-10T07:30:05.724642+08:00 AS-302T-F98A kernel: [40495.631164] sd 0:0:0:0: [sda] Synchronizing SCSI cache
2016-10-10T07:30:05.732759+08:00 AS-302T-F98A kernel: [40495.636630] sd 0:0:0:0: [sda]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
2016-10-10T07:30:05.737221+08:00 AS-302T-F98A kernel: [40495.644607] sd 0:0:0:0: [sda] Stopping disk
2016-10-10T07:30:05.742072+08:00 AS-302T-F98A kernel: [40495.649162] sd 0:0:0:0: [sda] START_STOP FAILED
2016-10-10T07:30:05.750025+08:00 AS-302T-F98A kernel: [40495.653909] sd 0:0:0:0: [sda]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
2016-10-10T07:30:05.842751+08:00 AS-302T-F98A kernel: [40495.751396] md: unbind<sda4>
2016-10-10T07:30:05.865266+08:00 AS-302T-F98A kernel: [40495.768506] md: export_rdev(sda4)
2016-10-10T07:30:05.915268+08:00 AS-302T-F98A kernel: [40495.771829] __sync_blockdev bdev not exist, don't sync
2016-10-10T07:30:05.915314+08:00 AS-302T-F98A kernel: [40495.823661] md: unbind<sda2>
2016-10-10T07:30:05.942725+08:00 AS-302T-F98A kernel: [40495.845886] md: export_rdev(sda2)
2016-10-10T07:30:05.985484+08:00 AS-302T-F98A kernel: [40495.849180] __sync_blockdev bdev not exist, don't sync
2016-10-10T07:30:05.985527+08:00 AS-302T-F98A kernel: [40495.884588] md/raid1:md126: Disk failure on sda3, disabling device.
2016-10-10T07:30:05.985541+08:00 AS-302T-F98A kernel: [40495.884592] md/raid1:md126: Operation continuing on 1 devices.
2016-10-10T07:30:06.003586+08:00 AS-302T-F98A kernel: [40495.909089] md: remove_and_add_spares rdev sda3 disk 0 0 1 0 0
2016-10-10T07:30:06.009639+08:00 AS-302T-F98A kernel: [40495.915086] md: remove_and_add_spares bdev /dev/sda3 not exist
2016-10-10T07:30:06.031311+08:00 AS-302T-F98A kernel: [40495.936663] md: remove_and_add_spares rdev sda3 remove sucess
2016-10-10T07:30:06.051572+08:00 AS-302T-F98A kernel: [40495.959932] md: unbind<sda3>
2016-10-10T07:30:06.074735+08:00 AS-302T-F98A kernel: [40495.977666] md: export_rdev(sda3)
2016-10-10T07:30:06.074793+08:00 AS-302T-F98A kernel: [40495.980990] __sync_blockdev bdev not exist, don't sync
2016-10-10T07:33:08.859810+08:00 AS-302T-F98A kernel: [40495.985957] __sync_blockdev bdev not exist, don't sync
2016-10-10T07:33:08.859857+08:00 AS-302T-F98A kernel: [40678.477659] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
2016-10-10T07:33:08.859887+08:00 AS-302T-F98A kernel: [40678.485228] ata1: irq_stat 0x00000040, connection status changed
2016-10-10T07:33:08.870293+08:00 AS-302T-F98A kernel: [40678.491249] ata1: SError: { CommWake DevExch }
2016-10-10T07:33:08.874169+08:00 AS-302T-F98A kernel: [40678.495839] ata1: hard resetting link
2016-10-10T07:33:18.910401+08:00 AS-302T-F98A kernel: [40688.515120] ata1: softreset failed (device not ready)
2016-10-10T07:33:18.910504+08:00 AS-302T-F98A kernel: [40688.520200] ata1: hard resetting link
2016-10-10T07:33:22.227453+08:00 AS-302T-F98A kernel: [40691.825816] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
2016-10-10T07:33:22.234540+08:00 AS-302T-F98A kernel: [40691.832956] ata1.00: ATA-8: TOSHIBA MD04ACA600, FS2A, max UDMA/100
2016-10-10T07:33:22.234658+08:00 AS-302T-F98A kernel: [40691.839193] ata1.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
2016-10-10T07:33:22.247186+08:00 AS-302T-F98A kernel: [40691.847498] ata1.00: configured for UDMA/100
2016-10-10T07:33:22.247285+08:00 AS-302T-F98A kernel: [40691.851844] ata1: EH complete
2016-10-10T07:33:22.258652+08:00 AS-302T-F98A kernel: [40691.855098] scsi 0:0:0:0: Direct-Access     ATA      TOSHIBA MD04ACA6 FS2A PQ: 0 ANSI: 5
2016-10-10T07:33:22.268735+08:00 AS-302T-F98A kernel: [40691.865347] sd 0:0:0:0: [sda] 11721045168 512-byte logical blocks: (6.00 TB/5.45 TiB)
2016-10-10T07:33:22.268918+08:00 AS-302T-F98A kernel: [40691.873328] sd 0:0:0:0: [sda] 4096-byte physical blocks
2016-10-10T07:33:22.279927+08:00 AS-302T-F98A kernel: [40691.879576] sd 0:0:0:0: [sda] Write Protect is off
2016-10-10T07:33:22.290918+08:00 AS-302T-F98A kernel: [40691.886103] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
2016-10-10T07:33:22.290930+08:00 AS-302T-F98A kernel: [40691.895278] sd 0:0:0:0: Attached scsi generic sg0 type 0
2016-10-10T07:33:22.322438+08:00 AS-302T-F98A kernel: [40691.922705]  sda: unknown partition table
2016-10-10T07:33:22.331333+08:00 AS-302T-F98A kernel: [40691.931027] sd 0:0:0:0: [sda] Attached SCSI disk
2016-10-10T07:33:26.805907+08:00 AS-302T-F98A kernel: [40696.399322]  sda: unknown partition table
2016-10-10T07:33:27.851523+08:00 AS-302T-F98A kernel: [40697.443246]  sda: unknown partition table
2016-10-10T07:33:29.461817+08:00 AS-302T-F98A kernel: [40699.051376]  sda: sda1 sda2 sda3 sda4

[sksbir]

hi
is your new disk in hardware compatibility list ?
Maybe disk is not properly inserted....

[huffie]

No, the new disk is not in the HW compatibility list and I don't think Asustor would test all the HDD in the market. I don't think my old 3TB harddisk is in the list as well.
Will try and re-sit the HDD again, but then again if it is not inserted properly the log wouldn't have stated that it is inserted (unless it's really DOA)

[sksbir]

No, the new disk is not in the HW compatibility list and I don't think Asustor would test all the HDD in the market. I don't think my old 3TB harddisk is in the list as well.
Will try and re-sit the HDD again, but then again if it is not inserted properly the log wouldn't have stated that it is inserted (unless it's really DOA)

Ok, your may be lucky until now, or not.

[mdof2]

Was there ever a resolution to this?
I'm running into the identical problem on an AS-2xx NAS.

Appreciate any information you nay have to share on the resolution.