NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
How do I know when disk rebuild is done?
Hi!
I am replacing 2TB disks with 3TB disks on my Ultra 6. How can I be certain that the disk rebuild is done for each disk? I replaced the first disk and I got messages that it detected that I had removed and replaced the disk, but not that the re-syncing was completed. It has been over 20 hours since I made the disk swap.
(newer to older log entries...)
On the other hand, the RAID configuration states that there are three disks and they are Redundant.
I have an Ultra 6 Plus with RAIDiator 4.2.22.
Thanks for the help!!
I am replacing 2TB disks with 3TB disks on my Ultra 6. How can I be certain that the disk rebuild is done for each disk? I replaced the first disk and I got messages that it detected that I had removed and replaced the disk, but not that the re-syncing was completed. It has been over 20 hours since I made the disk swap.
(newer to older log entries...)
Data volume will be rebuilt with disk 1.
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]
A disk was removed from the ReadyNAS.
Disk removal detected. [Disk 1]
Volume C is approaching capacity: 99% used 64G available
On the other hand, the RAID configuration states that there are three disks and they are Redundant.
I have an Ultra 6 Plus with RAIDiator 4.2.22.
Thanks for the help!!
10 Replies
Replies have been turned off for this discussion
- What do you see under Volumes > Volume Settings in Frontview?
- It says Redundant... Does this mean it is done syncing? If so, shouldn't there be a log entry stating it has completing syncing?
- Yes it should have made a status log entry.
If you download the logs (Status > Logs > Download all logs) and extract the zip contents what are the contents of mdstat.log? - Log file mdstat.log says:
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md2 : active raid5 sdd5[3] sda5[0](F) sdc5[2] sdb5[1]
3897584384 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
md1 : active raid5 sdd2[3] sda2[0](F) sdc2[2] sdb2[1]
1048448 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
md0 : active raid1 sdd1[3] sda1[0](F) sdc1[2] sdb1[1]
4193268 blocks super 1.2 [3/3] [UUU]
unused devices: <none> - And I see in mdconfig.log the following. It seems that the first disk (the one I recently inserted) is NOT in RAID 5 like the others, so it seems something is missing.
Device : /dev/md0
Create Time : 1300061229
Update Time : 1376233511
RAID Level : 1
RAID Capacity : 4193268
Disk Size : 4193268
Chunk Size : 0
Disks : 4
RAID Disks : 3
Active Disks : 3
Working Disks : 3
Failed Disks : 1
Spare Disks : 0
State : 1 [ Clean ]
Disk Device RAID Disk Maj/Min Sectors State
---------------------------------------------------------------------------
0 - -1 8/ 1 4294967295 1 [ Faulty ]
1 /dev/sdb1 1 8/17 8388608 6 [ Active Sync ]
2 /dev/sdc1 2 8/33 8388608 6 [ Active Sync ]
3 /dev/sdd1 0 8/49 8388608 6 [ Active Sync ]
Device : /dev/md1
Create Time : 1300061229
Update Time : 1376219822
RAID Level : 5
RAID Capacity : 1048448
Disk Size : 524224
Chunk Size : 65536
Disks : 4
RAID Disks : 3
Active Disks : 3
Working Disks : 3
Failed Disks : 1
Spare Disks : 0
State : 1 [ Clean ]
Disk Device RAID Disk Maj/Min Sectors State
---------------------------------------------------------------------------
0 - -1 8/ 2 4294967295 1 [ Faulty ]
1 /dev/sdb2 1 8/18 1048576 6 [ Active Sync ]
2 /dev/sdc2 2 8/34 1048576 6 [ Active Sync ]
3 /dev/sdd2 0 8/50 1048576 6 [ Active Sync ]
Device : /dev/md2
Create Time : 1300061229
Update Time : 1376233513
RAID Level : 5
RAID Capacity : 3897584384
Disk Size : 1948792192
Chunk Size : 65536
Disks : 4
RAID Disks : 3
Active Disks : 3
Working Disks : 3
Failed Disks : 1
Spare Disks : 0
State : 1 [ Clean ]
Disk Device RAID Disk Maj/Min Sectors State
---------------------------------------------------------------------------
0 - -1 8/ 5 4294967295 1 [ Faulty ]
1 /dev/sdb5 1 8/21 3897586809 6 [ Active Sync ]
2 /dev/sdc5 2 8/37 3897586809 6 [ Active Sync ]
3 /dev/sdd5 0 8/53 3897586809 6 [ Active Sync ] - Well mdstat.log looks fine. What about partition.log?
- Log file partition.log has:
***** partition output for sdd *****
Disk /dev/sdd: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 502E19AD-F377-43C2-87FD-9F0C29E9E0B5
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 8-sector boundaries
Total free space is 1953509108 sectors (931.5 GiB)
Number Start (sector) End (sector) Size Code Name
1 64 8388671 4.0 GiB FD00 Linux RAID
2 8388672 9437247 512.0 MiB FD00 Linux RAID
5 9437256 3907024064 1.8 TiB FD00 Linux RAID
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 sdb *****
Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 7B55C649-F44F-4421-82C1-EFA1AC8CBAB6
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 8-sector boundaries
Total free space is 5108 sectors (2.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 64 8388671 4.0 GiB FD00 Linux RAID
2 8388672 9437247 512.0 MiB FD00 Linux RAID
5 9437256 3907024064 1.8 TiB FD00 Linux RAID
Disk /dev/sdb: 243201 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+ 242251- 242252- 1953514583+ 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: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 708144C3-E85B-492B-A417-915F3CD52C15
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 8-sector boundaries
Total free space is 5108 sectors (2.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 64 8388671 4.0 GiB FD00 Linux RAID
2 8388672 9437247 512.0 MiB FD00 Linux RAID
5 9437256 3907024064 1.8 TiB FD00 Linux RAID
Disk /dev/sdc: 243201 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+ 242251- 242252- 1953514583+ ee EFI GPT
/dev/sdc2 0 - 0 0 0 Empty
/dev/sdc3 0 - 0 0 0 Empty
/dev/sdc4 0 - 0 0 0 Empty - Again that looks good, but it is missing the output for one of the disks.
- I just reboted and there is no change. Any other ideas?
- Well you could open an Online Support Case (see Online Submission link in my sig) and attach your logs zip file to your case and see what they have to say.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
