Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Matt26]

Hello!

I upgraded the firmware on my DNS-325 to 1.05 and have a couple of questions..

First, I created a RAID 1 volume with 2 x 500 GB hard drives, and noticed that this left over 3 GB of unallocated space, and looks like it can only be allocated to a separate JBOD volume??  Is this by design? Can the unallocated space be assigned to the RAID 1 volume?  I didn’t see any options to do this in the RAID setup or after setup was completed, so not sure if it’s an option..

Second, I noticed the DNS-325 support page now has a newer firmware version, 1.05b09 (beta); does anyone know what changes were made with this release?  The link for the release notes doesn’t seem to go anywhere.. I find it curious that a firmware update was released this long after support ran out for the hardware, any chance it might get out of beta status and become an official release??

Thanks for your time!

[Matt26]

Anyone?

[GreenBay42]

Regarding your second question, where is the beta firmware (what regional dlink site)? The US site only has 1.05B3. The beta firmware may be a regional fix.

[FurryNutz]

Link>Welcome!

• What region are you located?

B09 is a BUILD #.

Hello!

I upgraded the firmware on my DNS-325 to 1.05 and have a couple of questions..

First, I created a RAID 1 volume with 2 x 500 GB hard drives, and noticed that this left over 3 GB of unallocated space, and looks like it can only be allocated to a separate JBOD volume??  Is this by design? Can the unallocated space be assigned to the RAID 1 volume?  I didn’t see any options to do this in the RAID setup or after setup was completed, so not sure if it’s an option..

Second, I noticed the DNS-325 support page now has a newer firmware version, 1.05b09 (beta); does anyone know what changes were made with this release?  The link for the release notes doesn’t seem to go anywhere.. I find it curious that a firmware update was released this long after support ran out for the hardware, any chance it might get out of beta status and become an official release??

Thanks for your time!

[Matt26]

sorry, yes it was the Canadian site- would this be a regional update as suggested, since it doesn't show up on the US site?  any thoughts/comments regarding the first question?  that was really the focal point of my post..

many thanks!

[GreenBay42]

I messaged D-Link Canada to see what the "security fix" is on 1.05B09.

Are both hard drives the same brand/model? If they are different, 1 drive may have more space than the other. The DNS will use the lesser space of the 2 drives. If that is the case you cannot allocate that space to the RAID.

[GreenBay42]

The 1.05B09 BETA firmware fixes a few exploits. Not sure why the US did not get this.

• Fix the Command injection in CGI
• Fix the exploitable stack overflow in the binary
• Fix the security issue on Lighttpd configuration

[Matt26]

thank you!  i'm pretty sure the hard drives are the same model and size, would that be the only thing you can think of to generate the unallocated space for the JBOD?  it makes sense if the drives differ in size, maybe these are slightly different models and therefore the drive space varies slightly between the two- but they're both WD 500 GB.  is there any other reason the DNS-325 would leave this space unallocated?

[GreenBay42]

Since the DNS is letting you allocate the 3GB to JBOD, that is usually from 1 hard drive so the DNS is not seeing it as usable space for RAID 1 on both drives.

That is the only thing I can think of. I know hard drives don't always have the full advertised space available, even if the same brand and model.

[Matt26]

actually, i do recall seeing the unallocated space as being 1.5 GB on each drive, so it looks like maybe this isn't the case of extra space on one hard drive vs the other.  strange.. is there any way to configure settings for the RAID, either during setup or after creation, that would allow this space to be part of the RAID?

[GreenBay42]

It is normal for any NAS to leave a little extra space for RAID information. Whenever you format a drive there is always a little extra space. I am surprised though it is letting you allocate it.

[Matt26]

3 GB worth though?  i know what you mean, but seems like a lot for that extra space for the RAID information.

if i can't change this, then i would like to use the space for storage rather than letting it go to waste- i'm going to be swapping the hard drives for larger ones, so i'm assuming this unallocated space will grow in that case.  my next question is, if i create a JBOD from this unallocated space, will this affect the data on a single hard drive in the event of a software/hardware failure?  for example, the NAS itself or the other hard drive.. from what i understand, you should be able to take a single hard drive from a RAID 1 configuration and plug it into a computer to get the data off of it- would adding a JBOD to these RAIDed hard drives affect the ability to get the data off of that single hard drive in the event of a hardware failure?

[ivan]

Ok, first thing. 

1) What size are your hard drives?
2) Did you deliberately only make a 500GB RAID 1 set?
3) If your drives are larger than 500GB what did you intend to do with any remaining space?

Next.  Since we are dealing with a SOFTWARE RAID setup there can only be ONE RAID array per set of disks.  Hardware RAID is a totally different ball game.

Bearing this in mind you may need to think your disk setup strategy, backup any data you have on the array and, if necessary, reformat to a larger array.
 

[Matt26]

Ok, first thing. 

1) What size are your hard drives?
2) Did you deliberately only make a 500GB RAID 1 set?
3) If your drives are larger than 500GB what did you intend to do with any remaining space?

Next.  Since we are dealing with a SOFTWARE RAID setup there can only be ONE RAID array per set of disks.  Hardware RAID is a totally different ball game.

Bearing this in mind you may need to think your disk setup strategy, backup any data you have on the array and, if necessary, reformat to a larger array.
 

2 x WD 500GB, and yes my intention was to create a 500GB RAID 1 set, but did not expect to see any unallocated space after the RAID was created, let alone 3GB worth.

[RYAT3]

Ok, first thing. 

1) What size are your hard drives?
2) Did you deliberately only make a 500GB RAID 1 set?
3) If your drives are larger than 500GB what did you intend to do with any remaining space?

Next.  Since we are dealing with a SOFTWARE RAID setup there can only be ONE RAID array per set of disks.  Hardware RAID is a totally different ball game.

Bearing this in mind you may need to think your disk setup strategy, backup any data you have on the array and, if necessary, reformat to a larger array.
 

2 x WD 500GB, and yes my intention was to create a 500GB RAID 1 set, but did not expect to see any unallocated space after the RAID was created, let alone 3GB worth.

Which WD 500GB drives? This box is from circa 2011?  Dropping in some 2017 drives might produce problems, although I would hope not.