Cannot add HD to storage pool.

Currently reading
Cannot add HD to storage pool.

4
0
NAS
DS1813+
Operating system
  1. Windows
Mobile operating system
  1. Android
  2. iOS
Any idea about the reason can't I add a HD to a storage pool on my 1813+?

It is a 4TB Seagate which was working fine in another volume until yesterday, but I was running out of space on that volume so I replaced it with an 8TB HD.

The thing is that the old HD (Drive 3 in the attached image) does not appear in the list of available HDs for another storage pool.

The system reports it as "Not Initialized".

The specific HD and another identical on the same NAS (Drives 3 & 6) are reported in Critical Health Status because a few years back a faulty Synology backplane left a recconection history on all my HDs.
 

Attachments

  • SynDisk.jpg
    SynDisk.jpg
    46 KB · Views: 112
This could be the reason it cant be added but one more questions is what exact type and configuration is the array that this 4TB is trying to be a part of?
Well, my intention was to create a JBOD array consisting of this HD and an 8TB one, for backup purposes. Didn't work. Then I tried all configurations, RAID0, RAID1, Basic etc but the specific drive never appeared as an option. One 8TB and one 1TB HD on the system and not assigned to any storage pool, were shown as available to select without any problem.
 
Well, my intention was to create a JBOD array consisting of this HD and an 8TB one, for backup purposes. Didn't work. Then I tried all configurations, RAID0, RAID1, Basic etc but the specific drive never appeared as an option. One 8TB and one 1TB HD on the system and not assigned to any storage pool, were shown as available to select without any problem.
So even if you try and make a new pool?
 
So even if you try and make a new pool?
Tried it, no luck. I finally created a new storage pool with the 8TB plus a spare 3TB I had lying around.
The 4TB is the only unassigned HD on the machine , but still I cannot start making any new pools.
 
Tried it, no luck. I finally created a new storage pool with the 8TB plus a spare 3TB I had lying around.
The 4TB is the only unassigned HD on the machine , but still I cannot start making any new pools.
Then it might be too far corrupt for DSM to allow it to be a part of any pool.
 
Then it might be too far corrupt for DSM to allow it to be a part of any pool.
I am afraid you are right. The thing is that it is not corrupt. The faulty synology backplane marked ten reconnections on it and it has been reporting a critical status for quite a few years now, with no operational problems.
 
To follow-up the theory that disk health flagged as Critical can't be added to a storage pool...

A while ago my DS215j had one if its WD Red 3TB flagged as Failing, so I replaced it before the other might also do the same (bought at the same time). So I've had this 'failing' disk lying around and had already done a full platter scan using <some, I forget, PC or Mac based> utility which resulted it passing all tests.​
Having spare bays in the new NAS I put in this old disk with the hope to have it as temporary storage for large stuff that took enough time to generate but can be lost... a pre-delete store as it were.​

All the reading I've done states that the criteria for creating a new storage pool requires the allocation status to be Initialized or Not Initialized. But I think that there's a second [undocumented?] criteria that the disk's health status must be Healthy.

Checking SMART details, via the 'Failing' disk's Health Info, I did a Quick Test and this now reported the disk as healthy but the previous 'Failing' status was maintained by the NAS - so still can't create a new pool with it. An overnight running of Extended Test gave a second healthy result. But now the NAS has the disk's health status as Healthy and the Create buttons are now available.
  • 'Not Initialized' + 'Failing': Create buttons are greyed out.
  • 'Not Initialized' + 'Healthy': Create buttons are available.
 
Just FYI... When I was rebuilding a RAID0 pool recently, DSM warned me that one of the disks had bad sectors (it's had 4 bad sectors - all reallocated - for years with no further issues). Still, it begrudgingly permitted me to add it to the pool and create the RAID.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

Thank you. I just went through the same thing... Setting up a new RS2423+ (DSM7.2) with 2x 8TB drives...
Replies
2
Views
4,721
  • Question
Thanks, it finally worked I didn't pay attention to the next button at the bottom
Replies
6
Views
1,434
S
  • Question
Thanks Telos and others! Well, my problem is solved (before reading your post), it may have been an error...
Replies
5
Views
4,204
scooby_nas
S
  • Question
Gents, there is just single SATA 3 specification valid for all drives, then it doesn’t matter: - if the...
Replies
18
Views
11,922

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Back
Top