Experimental RC4.1 available for the DNS-320L-rev-A1/A2/A3 and the DNS-320-rev-B2

[João Cardoso]

Please read this Update

You can find RC4.1 for the DNS-320L-rev-A1/A2/A3 and the DNS-320-rev-B2 here

The README:

-This firmware is for the D-Link DNS-320L-rev-A1/A2/A3 and for the DNS-320-rev-B2.

The fw for the  DNS-320L-rev-A1/A2/A3 has been tested and is safe to use, the DNS-320-rev-B2 fw has not been tested, please report back.

If you have already flashed Alt-F-0.1RC4 on your box, you must execute the following script

before flashing this firmware:

#!/bin/sh

# RUN THIS SCRIPT *BEFORE* FLASHING RC4.1

if ! grep -q DNS-320 /tmp/board; then

echo "This is not for you, you don't have a DNS-320/320L box."

exit 1

fi

# find and remove fix files

aufs.sh -n

for i in /sbin/poweroff /usr/sbin/sysctrl /usr/sbin/dns320l-daemon \

$(awk '/\+\+\+/{print $2}' /usr/share/fixes/*.fix 2>/dev/null | \

sort -u); do

if test -f /Alt-F/$i; then

rm -f /Alt-F/$i

fi

done

aufs.sh -r

# deactivate the "boot user script"

sed -i '/^USER_SCRIPT=/d' /etc/misc.conf

# save current settings to flash memory

loadsave_settings -sf

After flashing and rebooting, the DNS-320-rev-Bx box will be reported as being a DNS-320L-A1. This is harmless.

There might exists some issues if you are using a mix of RAID1 and JBOD setup with the D-Link firmware, read this and this posts.

Please report any issue and Enjoy

[Erik J]

Thanks a lot João!

Where would we be without your efforts. I just installed it on a 320L rev A3, exploring during a few hours and it works like a charm untill now.

Salutacions!

e.

[Andrew G]

Thanks for producing the RC4.1 build, sorry about delay in testing it.

On Wednesday, 10 December 2014 19:54:14 UTC, João Cardoso wrote:

You can find RC4.1 for the DNS-320L-rev-A1/A2/A3 and the DNS-320-rev-B2 here

Please report any issue and Enjoy

Attempting to flash DNS-320-rev-B2 version using Alt-F web ui fails with error message:-
This firmware file has signature "08c1" and does not seems to be compatible with supported firmware.
Only firmware for the D-Link DNS-320-A1/A2, DNS-320L-A1, D-Link DNS-321-A1/A2, D-Link DNS-323-A1/B1/C1, D-Link DNS-325-A1/A2, Conceptronic CH3SNAS, Fujitsu-Siemens DUO 35-LR is supported.

Attempting to flash DNS-320 rev B stock firmware using Alt-F web ui fails with same error message.

I think this is because the DNS-320 rev B2 box has already been flashed with RC4 for DNS-320L-A1/A2/A3 (split/remerged using dns323-fw-box-arm), so the installed Alt-F firmware will only accept more DNS-320L A1/A2/A3 firmware and rejects DNS-320 rev B firmware whether Alt-F or stock.

Attempt to flash DNS-320L-rev-A1/A2/A3 version using Alt-F web ui works.

After reboot to RC4.1 still get same error messages when trying to flash DNS-320 rev B firmware.

After flashing and rebooting, the DNS-320-rev-Bx box will be reported as being a DNS-320L-A1. This is harmless.

 

Not harmless, box thinks it is DNS-320L-A1/2/3 so cannot reload stock firmware for DNS-320 rev B.

Reload stock firmware should be possible after split/remerge using dns323-fw-box-arm.

Only differnce between the two RC4.1 versions is in the header, not in the flashed firmware:-

cmp -l Alt-F-0.1RC4.1-DNS-320L-rev-A1A2A3.bin Alt-F-0.1RC4.1-DNS-320-rev-B2.bin
    57 114 102
    63  13  14

If the two versions are kept the same then it must accept flashing both DNS-320L rev A1/A2/A3 and DNS-320 rev B1/B2 firmware, or two different versions are needed which only accept reflashing with firmware for same box.

Not sure which I prefer and do not know how many bits of code/scripts are dependent on the board type. But it would be nicer for most users if the box identifies itself as the user would expect from the label, then no need to keep explaining why it is different.

My DNS-320 rev B2 box now running RC4.1 (flashed from DNS-320L rev A1/A2/A3 file), so far seems fairly good.
Status Page: temp/fan-speed working, hard disk correctly identified as in right slot.
Telnet working. Samba working. Blue leds seem ok, but seems strange to see orange leds on for empty usb and left-hdd.

[Chris]

I just flashed the firmware on my DNS302L-Rev A1 and everything seems to be ok, will report back if i encounter any problems.

Thank you 

 

[João Cardoso]

On Sunday, December 14, 2014 8:16:09 AM UTC, Andrew G wrote:

Thanks for producing the RC4.1 build, sorry about delay in testing it.

On Wednesday, 10 December 2014 19:54:14 UTC, João Cardoso wrote:

You can find RC4.1 for the DNS-320L-rev-A1/A2/A3 and the DNS-320-rev-B2 here

Please report any issue and Enjoy

Attempting to flash DNS-320-rev-B2 version using Alt-F web ui fails with error message:-
This firmware file has signature "08c1" and does not seems to be compatible with supported firmware.
Only firmware for the D-Link DNS-320-A1/A2, DNS-320L-A1, D-Link DNS-321-A1/A2, D-Link DNS-323-A1/B1/C1, D-Link DNS-325-A1/A2, Conceptronic CH3SNAS, Fujitsu-Siemens DUO 35-LR is supported.

Attempting to flash DNS-320 rev B stock firmware using Alt-F web ui fails with same error message. 

I think this is because the DNS-320 rev B2 box has already been flashed with RC4 for DNS-320L-A1/A2/A3

yes

 

(split/remerged using dns323-fw-box-arm), so the installed Alt-F firmware will only accept more DNS-320L A1/A2/A3 firmware

Yes

 

and rejects DNS-320 rev B firmware whether Alt-F or stock.

I will fix that. Just to allow and user to flash back the D-Link 320-rev-B fw.

But he might as well flash the D-Link 320L-rev-A fw (and have an upgraded box -- don't know if there is any difference in the software that D-Link ships with both boxes)

I am interested in differentiate boards only when that makes a difference, such as how to control the fan,  read the temperature, read buttons or control leds. From this point of view the 320L-rev-A and 320-rev-B boards are identical, the only difference being the amount of RAM.

The change that I will make will allow an user to flash either the 320L-rev-A or the 320-rev-B firmware files on either a 320L-rev-A or a 320-rev-B boards. This means that if the box bottom attached label says 320-rev-B it might be flashed with the D-Link 320L-rev-A firmware file. And vice versa.

We don't have to support D-Link marketing decisions.

 

Attempt to flash DNS-320L-rev-A1/A2/A3 version using Alt-F web ui works.

After reboot to RC4.1 still get same error messages when trying to flash DNS-320 rev B firmware.

After flashing and rebooting, the DNS-320-rev-Bx box will be reported as being a DNS-320L-A1. This is harmless.

 

Not harmless, box thinks it is DNS-320L-A1/2/3 so cannot reload stock firmware for DNS-320 rev B.

He can flash the 320L-rev-A fw and end up with an improved box :-). But I will fix that.

 

Reload stock firmware should be possible after split/remerge using dns323-fw-box-arm.

Only differnce between the two RC4.1 versions is in the header, not in the flashed firmware:-

cmp -l Alt-F-0.1RC4.1-DNS-320L-rev-A1A2A3.bin Alt-F-0.1RC4.1-DNS-320-rev-B2.bin
    57 114 102
    63  13  14

If the two versions are kept the same then it must accept flashing both DNS-320L rev A1/A2/A3 and DNS-320 rev B1/B2 firmware, or two different versions are needed which only accept reflashing with firmware for same box.

Not sure which I prefer and do not know how many bits of code/scripts are dependent on the board type. But it would be nicer for most users if the box identifies itself as the user would expect from the label,

I agree, but that will be made only for the next major release.

 

then no need to keep explaining why it is different.

My DNS-320 rev B2 box now running RC4.1 (flashed from DNS-320L rev A1/A2/A3 file), so far seems fairly good.
Status Page: temp/fan-speed working, hard disk correctly identified as in right slot.
Telnet working. Samba working. Blue leds seem ok, but seems strange to see orange leds on for empty usb and left-hdd.

All orange leds turn on when a degraded RAID is found.

Do you have swap over a degraded RAID1? If you fix that the orange leds will be turned off. And the poweroff/reboot sequence has been changed so that the swap RAID1 will not become degraded at the next boot.

Please continue reporting any issue, so I will move RC4.1 out of Experimental.

But RC4.1 is a *maintenance* release

Thanks

[Andrew G]

On Sunday, 14 December 2014 18:29:23 UTC, João Cardoso wrote:

 

I will fix that. Just to allow and user to flash back the D-Link 320-rev-B fw.

But he might as well flash the D-Link 320L-rev-A fw (and have an upgraded box -- don't know if there is any difference in the software that D-Link ships with both boxes)

 
Have not got a DNS-320L:, but D-Link say it's "Cloud based", I think they have added some extra "cloud" and "mydlink" functions, might not like running with just 128MB ram. I approve of idea of allowing flashing of either DNS-320 rev B or DNS-320L versions of either stock or alt-f firmware, let the user decide not D-Link.

Note: for next version only, need to warn any who have already installed on DNS-320 rev B that they have to install the DNS-320L version, otherwise it will be rejected, as happened to me.

Could go schizophrenic trying to keep track of which hardware the box is, which version of firmware is installed, which version of new firmware it will allow to be flashed, which version of new firmware you are trying to flash and which version the new firmware claims to be in the header.

Anyway, thanks, keep up the good work.

[Jose Manuel]

Hi Joao,

   I want to install RC4.1 in my DNS320L-A3.

   Before i do this i run the script of the first post, but i'm not sure if it runs correctly, how can i check sh runs ok?, no output its shown.

Thx for your big effort.

[João Cardoso]

On Tuesday, December 16, 2014 4:11:49 PM UTC, Jose Manuel wrote:

Hi Joao,

   I want to install RC4.1 in my DNS320L-A3.

   Before i do this i run the script of the first post, but i'm not sure if it runs correctly, how can i check sh runs ok?, no output its shown.

No news is good news (read as "no error is good news" :-)

I'm preparing a new Experimental RC4.1 that solves the swap over RAID1 and RAID1+JBOD issues, so you might wait a bit more.

[Jose Manuel]

Good news, RC4.1 flashed OK.

[João Cardoso]

A RC4.1.1 update:

-This firmware is for the D-Link DNS-320L-rev-A1/A2/A3 and for the DNS-320-rev-B2.

The firmware for the  DNS-320L-rev-A1/A2/A3 has been tested and is safe to use.

The firmware for the DNS-320-rev-B2 has been user tested and needs more positive reports.

-this firmware fixes a compatibility issue with D-Link disk setup regarding swap over RAID1 and RAID plus JBOD, making it possible to use your existing disks and data without further tweaking.

It also contains fixes for a few known issues found in RC4.

-If you have flashed the previous RC4.1 for the DNS-320-rev-B2, this new firmware will not be accepted by the firmware upgrade webUI, you have to flash the firmware for the DNS-320L-rev-A1/A2/A3, and that will be accepted. This issue is fixed by this new firmware.

The circuit boards for the DNS-320L-rev-Ax and DNS-320-rev-Bx are identical apart from a smaller amount of memory in the DNS-320-rev-Bx.

-If you have already flashed Alt-F-0.1RC4 on your box, you must execute the following script

before flashing this firmware:

...

please read the first post and the README-Experimental.txt file

[Jose Manuel]

I installed RC4.1.1 in my NAS DNS320L-A3.

I followed the initial wizard, all ok.

Shared my smb folders, i can see these in my Windows 8.1

But after some use, it gets me in any option i try this error:

ReadResponse() failed: The server did not return a response for this request.

I only can see the Status page and About. 

I'm using Chrome, the connection with putty works, but i can't do anything with my box

Whats happening?

[Jose Manuel]

Ufff, Its a fake.

I tried to connect from my tablet and i can see all the options of Alt-f.
Must be a problem of Windows, i will try to repair later, must go, i'm in vacation.

Merry christmas.

[yo tu el]

I have a D-Link DNS-320L-rev-A1 with Alt-F-0.1RC4.1

I flashed Alt-F-0.1RC4.1.1 without problems, but I don't know if it's updated correctly because it still appears in status page version Alt-F-0.1RC4.1

Is it correct? how can I check it?

Best regards,

El viernes, 19 de diciembre de 2014 16:59:37 UTC+1, João Cardoso escribió:

A RC4.1.1 update:

-This firmware is for the D-Link DNS-320L-rev-A1/A2/A3 and for the DNS-320-rev-B2.

The firmware for the  DNS-320L-rev-A1/A2/A3 has been tested and is safe to use.

The firmware for the DNS-320-rev-B2 has been user tested and needs more positive reports.

-this firmware fixes a compatibility issue with D-Link disk setup regarding swap over RAID1 and RAID plus JBOD, making it possible to use your existing disks and data without further tweaking.

It also contains fixes for a few known issues found in RC4.

-If you have flashed the previous RC4.1 for the DNS-320-rev-B2, this new firmware will not be accepted by the firmware upgrade webUI, you have to flash the firmware for the DNS-320L-rev-A1/A2/A3, and that will be accepted. This issue is fixed by this new firmware.

The circuit boards for the DNS-320L-rev-Ax and DNS-320-rev-Bx are identical apart from a smaller amount of memory in the DNS-320-rev-Bx.

-If you have already flashed Alt-F-0.1RC4 on your box, you must execute the following script

before flashing this firmware:

...

please read the first post and the README-Experimental.txt file

[Andrew G]

Flashed RC4.1.1 to DNS-320 rev B2, okay.

Afterwards firmware flashing worked as expected:-
    Alt-F firmware will accept either DNS-320-rev-Bx or DNS-320L-rev-Ax firmware, from either D-Link stock or Alt-F.
    D-Link stock firmware for DNS-320-rev-Bx will accept only DNS-320-rev-Bx firmware, from either D-Link stock or Alt-F.
    D-Link stock firmware for DNS-320L-rev-Ax will accept only DNS-320L-rev-Ax firmware, from either D-Link stock or Alt-F.

Nothing really to do with Alt-F itself, but temporarily had D-Link stock firmware for DNS-320L-rev-Ax running on DNS-320 rev B2 hardware. No complaints from the firmware, looked like it was running normally. It accepted the hard disk originally formatted by DNS-320-rev-Bx stock firmware. The DNS-320L-rev-Ax firmware is about 8MB larger than the normal DNS-320-rev-Bx firmware and seems to have extra features such as:-
    My Photos
    My Music
    My Surveillance
    Google Drive
So appear to be able to cross flash the D-Link stock firmware for these two types of box by temporarily loading Alt-F in-between.

Good build, thanks.

[frederic devulder]

HI
I had update my dns 320lw fron 4.1 to 4.1.1.
It work better for the temperature but now my disk became RO.
I've got now this message
<li><pre>Unable to automatically fix sda2, mounting Read Only: fsck 1.41.14 (22-Dec-2010)
/dev/sda2 contains a file system with errors, check forced.
/dev/sda2: Entry 'lightroom Bretagne' in /.systemfile/Photos/2008/Bretagne 2008 (53510149) is a link to directory /.systemfile/Photos/2008/Bretagne 2008/lightroom Bretagne (53510150).


/dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    (i.e., without -a or -p options)</pre>

I tried to find the answer  in the wiki, the faq or this forum but don't know how to run fsck manually.
Thank for you'r job and thank's for help me.
Best regard
F.D.

Le mercredi 10 décembre 2014 20:54:14 UTC+1, João Cardoso a écrit :

Please read this Update

You can find RC4.1 for the DNS-320L-rev-A1/A2/A3 and the DNS-320-rev-B2 here

The README:

-This firmware is for the D-Link DNS-320L-rev-A1/A2/A3 and for the DNS-320-rev-B2.

The fw for the  DNS-320L-rev-A1/A2/A3 has been tested and is safe to use, the DNS-320-rev-B2 fw has not been tested, please report back.

If you have already flashed Alt-F-0.1RC4 on your box, you must execute the following script

before flashing this firmware:

#!/bin/sh

# RUN THIS SCRIPT *BEFORE* FLASHING RC4.1

if ! grep -q DNS-320 /tmp/board; then

echo "This is not for you, you don't have a DNS-320/320L box."

exit 1

fi

# find and remove fix files

aufs.sh -n

for i in /sbin/poweroff /usr/sbin/sysctrl /usr/sbin/dns320l-daemon \

$(awk '/\+\+\+/{print $2}' /usr/share/fixes/*.fix 2>/dev/null | \

sort -u); do

if test -f /Alt-F/$i; then

rm -f /Alt-F/$i

fi

done

aufs.sh -r

# deactivate the "boot user script"

sed -i '/^USER_SCRIPT=/d' /etc/misc.conf

# save current settings to flash memory

loadsave_settings -sf

After flashing and rebooting, the DNS-320-rev-Bx box will be reported as being a DNS-320L-A1. This is harmless.

There might exists some issues if you are using a mix of RAID1 and JBOD setup with the D-Link firmware, read this and this posts.

[michele maceratesi]

hi, I read this post only after the flash the firmware on my 320 rel. B, and so I do not run the script that was recommended instead. Now I find myself with a 320 that is just an ornament cute. In practice, I see it as a network device but there are no shares, the GUI is the same as the previous one, but does not accept any combination user login password but I still can not connect via telnet and ssh after reset even if do not know the password root.Volevo ask if it was possible to solve the problem in some way.
thank you in advance for your help and I apologize for the poor command of the language.

[blacksun]

Hello everyone, I just installed ALT-F 4.1 RC on my d-link DNS320 rev b2 successfully. Everything working perfectly from the first boot and no data loss. Finally my nas can work great

[João Cardoso]

On Saturday, January 3, 2015 6:39:45 PM UTC, michele maceratesi wrote:

hi, I read this post only after the flash the firmware on my 320 rel. B, and so I do not run the script that was recommended instead. Now I find myself with a 320 that is just an ornament cute. In practice, I see it as a network device but there are no shares, the GUI is the same as the previous one, but does not accept any combination user login password but I still can not connect via telnet and ssh after reset even if do not know the password root.Volevo ask if it was possible to solve the problem in some way.
thank you in advance for your help and I apologize for the poor command of the language.

Have you solved the "issues" meanwhile?

[Andrew G]

What firmware did you have on before, was it D-Link or Alt-F RC4 ?
Is your box a DNS-320 rev B1 or B2 ?
Does the box answer a ping?
Can you connect to box by telnet?

On Saturday, 3 January 2015 18:39:45 UTC, michele maceratesi wrote:

hi, I read this post only after the flash the firmware on my 320 rel. B, and so I do not run the script that was recommended instead. Now I find myself with a 320 that is just an ornament cute. In practice, I see it as a network device but there are no shares, the GUI is the same as the previous one, but does not accept any combination user login password but I still can not connect via telnet and ssh after reset even if do not know the password root.Volevo ask if it was possible to solve the problem in some way.
thank you in advance for your help and I apologize for the poor command of the language.

The script is only needed if earlier version of Alt-F RC4 already loaded. After changing from D-Link firmware to Alt-F firmware you may need to clear your browser cache before it will show the Alt-F Status page, the Alt-F shares have to be setup through its GUI.

[michele maceratesi]

no, I just did some tests and I read several posts, but I have not figured out how to fix it

[michele maceratesi]

hi, the version of the nas is b2, the previous firmware was the latest available at d-link, the nas responds to pings. I tried to connect via putty ssh, but at the command prompt I could not come with any combination of username and password, I was able to reset the Log me effettando 320 and then linking up with putty telnet.

[Andrew G]

On Wednesday, 7 January 2015 09:15:21 UTC, michele maceratesi wrote:

hi, the version of the nas is b2, the previous firmware was the latest available at d-link, the nas responds to pings. I tried to connect via putty ssh, but at the command prompt I could not come with any combination of username and password, I was able to reset the Log me effettando 320 and then linking up with putty telnet.

Good. You need to set a root password for ssh login to work, you can use "passwd" command in telnet.

Clear the browser cache, then check if web GUI shows Alt-F Status page and configuration pages.

[michele maceratesi]

tanks!!  it worked ... in fact they are now able to access the web through.
There are clear instructions on how to use this firmware that which seems powerful?

[Andrew G]

Some instructions at http://sourceforge.net/p/alt-f/wiki/Home/, some blue ? help icons also in the web GUI.

[michele maceratesi]

Thank you very much, now my 320 works fine, I just wanted to ask a question, exists in a repository application that lets you manage files and folders? For example if I wanted to move multiple files from one folder to another?

[Kyle Riedel]

Any plans for the DNS-325-rev-A1?

[dicky...@gmail.com]

FYI - Have installed Alt-F-0.1RC4.1.1-DNS-320L-rev-A1A2A3 on a 320L-Rev A3 ok but had wizard issues.

Hi - First time user.

Just to let you know I flashed this ok (twice in fact) but the wizard would not go past the Disk Wizard screen (theres no button to continue and the savse settings seems to save but thats all), so I have had to logout and manually setup the box and raid partitions myself. I specifically wanted the Raid 5 Capabilities which is great.

Currently the Raid is building and it says it will take 20 hours for 3 x 2TB disks to build the raid partition)

Will keep you posted of any issues.

Just have to find out how to remove and re-add a disk to raid and test it before I put real data on it!

Thanks for the software upgrade.

dicky

[dicky...@gmail.com]

After 20 hours the format finished fine. I then went to create a filesystem but the web interface wouldnt work - selected the action and submitted but nothing happened.
I then ssh'd in and formatted md0 with fsck.ext4 then tuned it to have only 1% free blocks.

After that I was able to carry on.

The other thing was I couldnt workout how to create a directory in the web interface so used mkdir to create one in /mnt/md0 then samba could see it and I mounted it there ok.

I have a second new Version A3 NAS - so this time I will try and document my efforts a little more on that one and post a pdf as I reckon I might get stuck again! Will do a raid1 system not raid5 this time as a test.

Dicky

[João Cardoso]

On Friday, January 16, 2015 at 5:38:56 PM UTC, dicky...@gmail.com wrote:

After 20 hours the format finished fine. I then went to create a filesystem but the web interface wouldnt work

what you mean? what part of the web interface? Disk->Filesystem? what was displayed?

 

- selected the action

what action?

 

and submitted but nothing happened.

vague...

 

I then ssh'd in and formatted md0 with fsck.ext4 then tuned it to have only 1% free blocks.

After that I was able to carry on.

The other thing was I couldnt workout how to create a directory in the web interface

Setup->Folders

 

so used mkdir to create one in /mnt/md0 then samba could see it and I mounted it there ok.

I have a second new Version A3 NAS - so this time I will try and document my efforts a little more

It is essential to report any error/warning/strange/odd messages, as well as exactly what was done, and in what sequence.

Follow "The quality of the answer is directly proportional to the amount of work you put into the question” link at the Forum Welcome message.

Sorry for being so harsh, but I can't help or solve "ill-posed problems" :-(

[dicky...@gmail.com]

OK, I understand what you are saying - I will make a detailed report for this new nas and let you know the outcome. Its been flashed only and not logged in yet.

Thanks for the reply.

Dicky

[dicky...@gmail.com]

ok, the new install worked flawlessly as per the 'First time setup' (pdf of screenshots uploaded but nothing to report out of the ordinary) This was a mirrored pair of 500gb drives.

The issue I had before was the wizard would not go past the Disk Wizard screen when pressing the abracadbra button when selecting Raid 5 - so I exited the wizard and created the raid partitions manually then couldnt create a filesystem in the browser. Changing any settings in the 'New FS Operations' section then submit, did nothing at all. thats when i ssh'd in and formatted the filesystem myself.

If I get a chance, I will blow this unit back to stock code and try a raid 5 partition with the 2 500gb disks and a 160gb usb disk I have and report if the wizard fails again.

Thanks a lot,

Dicky

[dicky...@gmail.com]

OK, done a clear settings, put on stock firmware, upgraded to Alt-F 0.1RC4.1 and the wizard came up first time and all worked perfectly this time doing a raid5 system.

So must have been finger trouble on my part on the first nas I setup!

So seems great so far on a rev 3 NAS-320L.

I will start playing around and report any issues.

Thanks again,

dicky

[João Cardoso]

On Friday, January 16, 2015 at 7:33:03 PM UTC, dicky...@gmail.com wrote:

ok, the new install worked flawlessly as per the 'First time setup' (pdf of screenshots uploaded but nothing to report out of the ordinary) This was a mirrored pair of 500gb drives.

So the only difference from your previous attempt are the disks. Your first attempt was with 2TB disks, were they brand new? without a partition table? I do my tests with small old 80GB disks, my only 2TB disk is not available for tests.

There is a know issue with 6TB disks, see https://sourceforge.net/p/alt-f/tickets/358/ and the Disk Partitioner will fail for greater then 2TB unpartitioned disks, see https://sourceforge.net/p/alt-f/tickets/359/

[dicky...@gmail.com]

Hi, technically yes. I have 2 units both the same and brand new. 1 has 2 used 2TB disks in the sata bays and a brand new one on the USB port. This is the one I had difficulty with. I guess they did have old partitions on them actually as they came from a large enterprise linux raid array - didnt think about that at the time so this may have been the issue.

The second one has 2 used 500gb disks and a used 500gb disk on the USB port - worked flawlessly with raid 1 and raid 3. These were also made a raid 1 disk under the Dlink firmware before flashing yours and making them raid 1 and raid 3.

I think i might keep the stock firmware on this with 2 mirrored 1TB disks as it see it supports remote video recording which I might use for house security! Dont know yet though!

Dicky

[noneofmyseeds]

I'm curious how you have remote video recording on this box, or plan
to do it.

[dicky...@gmail.com]

Remote video (my surveillance) is an app on the stock dlink firmware called DNS-320L_Surveillancecenter_2.01 from the dlink website - its not an Alt-F addon as far as I know.

dicky

> use for house security! Dont know yet though! Hi