- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: rn214not expanding
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
rn214not expanding
i have a readynas 214 with 1x 4tb an thd 3 x 3tb hoever the capacity is coming outon the admin page as 6.35 tb i think i should be getting in the region of 7.4tb based on the readynas calculator giving 8.26tiB x 0.9095 conversion tiB to TB although thes um of all srives lesslargest = 9 is that the correct raid 5 calculation for array capacity?
eith eay f its not expandibg correctly how can i fix? ideally without having to delet the volume and recreating then restoring backup. as the backup does not include my time machine bckups
the
tia
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
And XRAID is enabled?
A TB is smaller than a TiB, so you did the conversion wrong. You should be getting 8.16TiB. But I think the NAS thinks you still have two 2TB drives and either two 3TB or one 3TB and one 4TB (because the extra 1TB of 4 would currently be unused). That indicates that the expansion problem occurred before you made your latest disk swap.
If you post the contents of mdstat.log from the downloaded log .zip file (using the </> "code" tool in the forum works best) and describe the starting drive configuratrion and what changes have been made along the way, we may be able to see if there is a way to fix it.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md126 : active raid5 sda4[4] sdd4[3] sdb4[1] 3906745856 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU] resync=DELAYED md127 : active raid5 sda3[6] sdd3[4] sdc3[5] sdb3[1] 2915738496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU] [==================>..] resync = 90.5% (880496640/971912832) finish=46.4min speed=32810K/sec md1 : active raid10 sda2[0] sdd2[3] sdc2[2] sdb2[1] 1046528 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU] md0 : active raid1 sda1[6] sdd1[4] sdc1[5] sdb1[1] 4190208 blocks super 1.2 [4/4] [UUUU] unused devices: <none> /dev/md/0: Version : 1.2 Creation Time : Tue Feb 20 20:47:29 2018 Raid Level : raid1 Array Size : 4190208 (4.00 GiB 4.29 GB) Used Dev Size : 4190208 (4.00 GiB 4.29 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Sat Sep 5 08:02:34 2020 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Consistency Policy : unknown Name : 568aca8b:0 (local to host 568aca8b) UUID : 6ca489e0:ea2dfd6f:1330a41a:83693582 Events : 5723 Number Major Minor RaidDevice State 6 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1 5 8 33 2 active sync /dev/sdc1 4 8 49 3 active sync /dev/sdd1 /dev/md/1: Version : 1.2 Creation Time : Thu Sep 3 19:36:40 2020 Raid Level : raid10 Array Size : 1046528 (1022.00 MiB 1071.64 MB) Used Dev Size : 523264 (511.00 MiB 535.82 MB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Sat Sep 5 07:54:47 2020 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : near=2 Chunk Size : 512K Consistency Policy : unknown Name : 568aca8b:1 (local to host 568aca8b) UUID : e083319b:882c0819:3d5e4ae3:d4d4c232 Events : 19 Number Major Minor RaidDevice State 0 8 2 0 active sync set-A /dev/sda2 1 8 18 1 active sync set-B /dev/sdb2 2 8 34 2 active sync set-A /dev/sdc2 3 8 50 3 active sync set-B /dev/sdd2 /dev/md/data-0: Version : 1.2 Creation Time : Tue Feb 20 20:48:03 2018 Raid Level : raid5 Array Size : 2915738496 (2780.66 GiB 2985.72 GB) Used Dev Size : 971912832 (926.89 GiB 995.24 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Sat Sep 5 08:02:38 2020 State : clean, resyncing Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Consistency Policy : unknown Resync Status : 90% complete Name : 568aca8b:data-0 (local to host 568aca8b) UUID : 55af480e:f05a8c92:bc26929e:bd16d3eb Events : 72474 Number Major Minor RaidDevice State 6 8 3 0 active sync /dev/sda3 1 8 19 1 active sync /dev/sdb3 5 8 35 2 active sync /dev/sdc3 4 8 51 3 active sync /dev/sdd3 /dev/md/data-1: Version : 1.2 Creation Time : Wed Feb 21 04:51:56 2018 Raid Level : raid5 Array Size : 3906745856 (3725.76 GiB 4000.51 GB) Used Dev Size : 1953372928 (1862.88 GiB 2000.25 GB) Raid Devices : 3 Total Devices : 3 Persistence : Superblock is persistent Update Time : Sat Sep 5 08:02:38 2020 State : clean, resyncing (DELAYED) Active Devices : 3 Working Devices : 3 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Consistency Policy : unknown Name : 568aca8b:data-1 (local to host 568aca8b) UUID : 9e75db3f:24081c6f:d1515f20:e59052df Events : 130022 Number Major Minor RaidDevice State 4 8 4 0 active sync /dev/sda4 1 8 20 1 active sync /dev/sdb4 3 8 52 2 active sync /dev/sdd4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
many thanks for the reply
cant remember the very original drive cobination but befr the most recent change i hink it was 4tb,3,2tb,3tb
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md126 : active raid5 sda4[4] sdd4[3] sdb4[1] 3906745856 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU] resync=DELAYED md127 : active raid5 sda3[6] sdd3[4] sdc3[5] sdb3[1] 2915738496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU] [==================>..] resync = 90.5% (880496640/971912832) finish=46.4min speed=32810K/sec md1 : active raid10 sda2[0] sdd2[3] sdc2[2] sdb2[1] 1046528 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU] md0 : active raid1 sda1[6] sdd1[4] sdc1[5] sdb1[1] 4190208 blocks super 1.2 [4/4] [UUUU] unused devices: <none> /dev/md/0: Version : 1.2 Creation Time : Tue Feb 20 20:47:29 2018 Raid Level : raid1 Array Size : 4190208 (4.00 GiB 4.29 GB) Used Dev Size : 4190208 (4.00 GiB 4.29 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Sat Sep 5 08:02:34 2020 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Consistency Policy : unknown Name : 568aca8b:0 (local to host 568aca8b) UUID : 6ca489e0:ea2dfd6f:1330a41a:83693582 Events : 5723 Number Major Minor RaidDevice State 6 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1 5 8 33 2 active sync /dev/sdc1 4 8 49 3 active sync /dev/sdd1 /dev/md/1: Version : 1.2 Creation Time : Thu Sep 3 19:36:40 2020 Raid Level : raid10 Array Size : 1046528 (1022.00 MiB 1071.64 MB) Used Dev Size : 523264 (511.00 MiB 535.82 MB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Sat Sep 5 07:54:47 2020 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : near=2 Chunk Size : 512K Consistency Policy : unknown Name : 568aca8b:1 (local to host 568aca8b) UUID : e083319b:882c0819:3d5e4ae3:d4d4c232 Events : 19 Number Major Minor RaidDevice State 0 8 2 0 active sync set-A /dev/sda2 1 8 18 1 active sync set-B /dev/sdb2 2 8 34 2 active sync set-A /dev/sdc2 3 8 50 3 active sync set-B /dev/sdd2 /dev/md/data-0: Version : 1.2 Creation Time : Tue Feb 20 20:48:03 2018 Raid Level : raid5 Array Size : 2915738496 (2780.66 GiB 2985.72 GB) Used Dev Size : 971912832 (926.89 GiB 995.24 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Sat Sep 5 08:02:38 2020 State : clean, resyncing Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Consistency Policy : unknown Resync Status : 90% complete Name : 568aca8b:data-0 (local to host 568aca8b) UUID : 55af480e:f05a8c92:bc26929e:bd16d3eb Events : 72474 Number Major Minor RaidDevice State 6 8 3 0 active sync /dev/sda3 1 8 19 1 active sync /dev/sdb3 5 8 35 2 active sync /dev/sdc3 4 8 51 3 active sync /dev/sdd3 /dev/md/data-1: Version : 1.2 Creation Time : Wed Feb 21 04:51:56 2018 Raid Level : raid5 Array Size : 3906745856 (3725.76 GiB 4000.51 GB) Used Dev Size : 1953372928 (1862.88 GiB 2000.25 GB) Raid Devices : 3 Total Devices : 3 Persistence : Superblock is persistent Update Time : Sat Sep 5 08:02:38 2020 State : clean, resyncing (DELAYED) Active Devices : 3 Working Devices : 3 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Consistency Policy : unknown Name : 568aca8b:data-1 (local to host 568aca8b) UUID : 9e75db3f:24081c6f:d1515f20:e59052df Events : 130022 Number Major Minor RaidDevice State 4 8 4 0 active sync /dev/sda4 1 8 20 1 active sync /dev/sdb4 3 8 52 2 active sync /dev/sdd4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
Did you just replace the disk? If so, you just needed to wait longer (likely it is already expanding by now).
Also, what disk models do you have?
This is the original RAID group, which is still resyncing (which looks like you just replaced a disk).
md127 : active raid5 sda3[6] sdd3[4] sdc3[5] sdb3[1] 2915738496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU] [==================>..] resync = 90.5% (880496640/971912832) finish=46.4min speed=32810K/sec
After this completes, the expansion step will begin.
md126 : active raid5 sda4[4] sdd4[3] sdb4[1] 3906745856 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU] resync=DELAYED
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
according to the admin pgsges is stopped resyncing a good few days ago it has ximpleted the resync without moving onto expansion it would seem
drive models are:
- wdwdc w040efax-6h 68jh4n0
- wd wdc030efrx-68euzn0
- toshiba hdwd130
- toshiba hdwd130
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
@Petroc wrote:
according to the admin pgsges is stopped resyncing a good few days ago
What is the current mdstat?
@Petroc wrote:
- wdc wd40efax-6h 68jh4n0
I was wondering about that. That is an SMR drive, which is not well suited for RAID. I have no idea what WDC was thinking when they used that technology in a NAS-purposed drive. The newer "WD Red Plus" line has the WD40EFRX, which doesn't have that problem.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
so sounds like if i reoplace the 1st drive the wd smar drive i might be able to use full capacity what is the conflict between smr and raid?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
@Petroc wrote:
what is the conflict between smr and raid?
Look here: https://www.servethehome.com/wd-red-smr-vs-cmr-tested-avoid-red-smr/2/
Note particularly the section that says:
Unfortunately, while the SMR WD Red performed respectably in the previous benchmarks, the RAIDZ resilver test proved to be another matter entirely. While all three CMR drives comfortably completed the resilver in under 17 hours, the SMR drive took nearly 230 hours to perform an identical task.
The RAIDZ resilver operation is similar to what your NAS does with a resync and vertical expansion.
@Petroc wrote:
so sounds like if i reoplace the 1st drive the wd smar drive i might be able to use full capacity
I think the next step is to re-download the log zip file, and see what the current status of the mdstat.log is. I understand that the web ui might show the resync as completed, but I think it makes sense to look more closely in the logs.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
tankyou so much fpr your time on this today's md stat:
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md126 : active raid5 sda4[4] sdd4[3] sdb4[1] 3906745856 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU] md127 : active raid5 sda3[6] sdd3[4] sdc3[5] sdb3[1] 2915738496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU] md1 : active raid10 sda2[0] sdd2[3] sdc2[2] sdb2[1] 1046528 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU] md0 : active raid1 sda1[6] sdd1[4] sdc1[5] sdb1[1] 4190208 blocks super 1.2 [4/4] [UUUU] unused devices: <none> /dev/md/0: Version : 1.2 Creation Time : Tue Feb 20 20:47:29 2018 Raid Level : raid1 Array Size : 4190208 (4.00 GiB 4.29 GB) Used Dev Size : 4190208 (4.00 GiB 4.29 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Sun Sep 6 21:58:35 2020 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Consistency Policy : unknown Name : 568aca8b:0 (local to host 568aca8b) UUID : 6ca489e0:ea2dfd6f:1330a41a:83693582 Events : 5723 Number Major Minor RaidDevice State 6 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1 5 8 33 2 active sync /dev/sdc1 4 8 49 3 active sync /dev/sdd1 /dev/md/1: Version : 1.2 Creation Time : Thu Sep 3 19:36:40 2020 Raid Level : raid10 Array Size : 1046528 (1022.00 MiB 1071.64 MB) Used Dev Size : 523264 (511.00 MiB 535.82 MB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Sun Sep 6 21:58:28 2020 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : near=2 Chunk Size : 512K Consistency Policy : unknown Name : 568aca8b:1 (local to host 568aca8b) UUID : e083319b:882c0819:3d5e4ae3:d4d4c232 Events : 19 Number Major Minor RaidDevice State 0 8 2 0 active sync set-A /dev/sda2 1 8 18 1 active sync set-B /dev/sdb2 2 8 34 2 active sync set-A /dev/sdc2 3 8 50 3 active sync set-B /dev/sdd2 /dev/md/data-0: Version : 1.2 Creation Time : Tue Feb 20 20:48:03 2018 Raid Level : raid5 Array Size : 2915738496 (2780.66 GiB 2985.72 GB) Used Dev Size : 971912832 (926.89 GiB 995.24 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Sun Sep 6 21:58:35 2020 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Consistency Policy : unknown Name : 568aca8b:data-0 (local to host 568aca8b) UUID : 55af480e:f05a8c92:bc26929e:bd16d3eb Events : 72486 Number Major Minor RaidDevice State 6 8 3 0 active sync /dev/sda3 1 8 19 1 active sync /dev/sdb3 5 8 35 2 active sync /dev/sdc3 4 8 51 3 active sync /dev/sdd3 /dev/md/data-1: Version : 1.2 Creation Time : Wed Feb 21 04:51:56 2018 Raid Level : raid5 Array Size : 3906745856 (3725.76 GiB 4000.51 GB) Used Dev Size : 1953372928 (1862.88 GiB 2000.25 GB) Raid Devices : 3 Total Devices : 3 Persistence : Superblock is persistent Update Time : Sun Sep 6 21:58:35 2020 State : clean Active Devices : 3 Working Devices : 3 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Consistency Policy : unknown Name : 568aca8b:data-1 (local to host 568aca8b) UUID : 9e75db3f:24081c6f:d1515f20:e59052df Events : 130048 Number Major Minor RaidDevice State 4 8 4 0 active sync /dev/sda4 1 8 20 1 active sync /dev/sdb4 3 8 52 2 active sync /dev/sdd4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
@Petroc wrote:
tankyou so much fpr your time on this today's md stat:
md126 : active raid5 sda4[4] sdd4[3] sdb4[1]
3906745856 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU] md127 : active raid5 sda3[6] sdd3[4] sdc3[5] sdb3[1]
2915738496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
The resync has completed. Your array has 2 RAID groups (shown above)..
The problem is that md126 is missing one of the disks (sdc).
Can you also look in disk_info.log at sdc? It'd be useful to know what disk it is (and double-check the size).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
this s the disc )=-info.log
Device: sda Controller: 0 Channel: 0 Model: WDC WD40EFAX-68JH4N0 Serial: WD-WX12D40ED0P1 Firmware: 82.00A82W Class: SATA RPM: 5400 Sectors: 7814037168 Pool: data PoolType: RAID 5 PoolState: 1 PoolHostId: 568aca8b Health data ATA Error Count: 0 Reallocated Sectors: 0 Reallocation Events: 0 Spin Retry Count: 0 Current Pending Sector Count: 0 Uncorrectable Sector Count: 0 Temperature: 36 Start/Stop Count: 16 Power-On Hours: 251 Power Cycle Count: 16 Load Cycle Count: 6 Device: sdb Controller: 0 Channel: 1 Model: WDC WD30EFRX-68EUZN0 Serial: WD-WCC4N6LSVTR7 Firmware: 82.00A82W Class: SATA RPM: 5400 Sectors: 5860533168 Pool: data PoolType: RAID 5 PoolState: 1 PoolHostId: 568aca8b Health data ATA Error Count: 0 Reallocated Sectors: 0 Reallocation Events: 0 Spin Retry Count: 0 Current Pending Sector Count: 0 Uncorrectable Sector Count: 0 Temperature: 41 Start/Stop Count: 7691 Power-On Hours: 28090 Power Cycle Count: 793 Load Cycle Count: 9470 Device: sdc Controller: 0 Channel: 2 Model: TOSHIBA HDWD130 Serial: Z7A4K1AAS Firmware: MX6OACF0T Class: SATA RPM: 7200 Sectors: 5860533168 Pool: data PoolType: RAID 5 PoolState: 1 PoolHostId: 568aca8b Health data ATA Error Count: 0 Reallocated Sectors: 0 Reallocation Events: 0 Spin Retry Count: 0 Current Pending Sector Count: 0 Uncorrectable Sector Count: 0 Temperature: 42 Start/Stop Count: 6904 Power-On Hours: 16397 Power Cycle Count: 765 Load Cycle Count: 6906 Device: sdd Controller: 0 Channel: 3 Model: TOSHIBA HDWD130 Serial: 68AU6MYAS Firmware: MX6OACF0T Class: SATA RPM: 7200 Sectors: 5860533168 Pool: data PoolType: RAID 5 PoolState: 1 PoolHostId: 568aca8b Health data ATA Error Count: 0 Reallocated Sectors: 0 Reallocation Events: 0 Spin Retry Count: 0 Current Pending Sector Count: 0 Uncorrectable Sector Count: 0 Temperature: 42 Start/Stop Count: 5242 Power-On Hours: 10345 Power Cycle Count: 541 Load Cycle Count: 5242
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
if i deleted the volume and created a new one and restored data from a backup would i be sure to get the full capacity expected? or am i looking for a needle in a haystack trying to work this out?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
The space you are missing is on disk 3 (sdc).
Perhaps remove disk 3, and then reformat it (or unformat it) in a Windows PC. Then reinsert it, and see if after resync you get the full space. If you reformat it in Windows then you'll need to reformat it again in the NAS.
Definitely make sure your backup is up to date first though.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
i only have a msc so will only be able to format it using disk utility any particular format type i.e fat32 macos extended etc? is it possible to format that individual drive in the nas itself?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
@Petroc wrote:
i only have a msc
What is an msc?
The format used in the PC actually doesn't matter - the point is really to remove the NAS formatting, and then have the NAS reformat it again. Unformatting (for instance with the windows disk manager), or zeroing the disk (using a number of utilities) will work just as well.
You'll need to remove the disk from the NAS though, as it won't let you remove the disk from the array.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
Typically, just removing any partitioning with a PC is sufficient, especially removing any system reserved partition since the NAS can't handle them (can't even delete them).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
will that be enouggh t make te nas think its a completely new drive?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
@Petroc wrote:
will that be enouggh t make te nas think its a completely new drive?
Yes. Unformattng the drive (removing the partitions) will make the NAS think it's a new drive.
So will zeroing the drive with vendor tools (seatools or lifeguard), or other low-level tools.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
Maybe try powering down the NAS, and removing the existing disks (labeling by slot).
Then try powering up with the disk in slot 1 (other slots empty), and see if it is recognized. You'll need to do a factory default procedure from the boot menu.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
@Petroc wrote:
Do you mean the disk just inserted in slot one feafault reset and then Reload with the disks in correct position?
The idea is to first double-check that the NAS can detect the disk (the original disk 3) in any slot. So start with slot 1, and do a factory default - that should install the OS on the disk, and create a jbod volume. If it works, then power down, move the disk to slot 2 and reboot. Continue until you've tested all 4 slots.
Assuming the disk is detected and will boot from any slot, then the next step is to try again. You'd remove the disk, and power up with all the other disks in their correct places. The system should boot, though the RAID system might say that it's degraded.
Then connect the problem disk to your mac and format it again. Hot insert it into the NAS (while it is running). The disk should appear on the volume page. If you select it, you should be able to format it. If XRAID is on, then it should be immediately added back into the array.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: rn214not expanding
i've taken the nuclear option of filling the unit with all drives i have available and doing a factory default now restoring data from backup the volume ca[acity is 8.17 tb with 1x4 3x3 drives better than i had for sure and at least i'm now usingall my disks that are otherwise unused
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content