[SOLVED] HP Proliant N40L MicroServer native support


Recommended Posts

I installed Trantor 1.2 on a N40L with 6x2tb with the modified Bios. Much of everything seems to work fine, but I have a couple of questions I can't figure out how to do:

 

1. Wake On Lan (WOL) - I retrieved the MAC address of the built-in NIC from the Bios (other people suggested live cd) I am honestly not familiar enough with Linux to figure it out without more detailed instructions (but I am not afraid of the command line). I changed it using this guide http://xpenology.com/forum/viewtopic.php?f=2&t=1353. It was updated in synology assistant, but I not sure what to do next. I saw this thread, but I don't know how to implement the transfer discussed in the 3rd post down in this guide by jasonwu http://xpenology.com/forum/viewtopic.php?f=2&t=665

 

Any help or more detailed step-by-step guide will be greatly appreciated.

 

2. VPN - I have trouble setting up OpenVPN. I enabled on diskstation, set up the privileges, exported config files, installed open vpn client on a windows 7 PC, edited the config file as instructed, and it seems to connect but Fails Authorization when I try to log in any ideas?

 

I was able to get the cloud station working and it is syncing just fine, but not the VPN for some reason. FYI, I also have the Priviate Internet Access (PIA) client installed on my computer, not sure if that affects anything.

Link to post
Share on other sites
  • 2 weeks later...
I found eject USB script on synology forum

 

http://forum.synology.com/enu/viewtopic ... 39&t=35668

sync; /usr/syno/bin/synousbdisk -umount sdq; >/tmp/usbtab

 

Where it can be placed ? For auto-start after full boot.

 

 

p.s. right answer is:

 

1. create new script S99ZZZ_USB_eject.sh

with

sync; /usr/syno/bin/synousbdisk -umount sdk1; >/tmp/usbtab

2. copy it in the /usr/syno/etc/rc.d directory

3. give it the execute permission via ssh

chmod +x S99ZZZ_USB_eject.sh

4. reboot

 

Before placing this into an automatic script I wanted to test it on the command line first to make sure it would work for me, (and to see if my drives span down).

 

I've logged in as root, and then at the command prompt I've done:

sync; /usr/syno/bin/synousbdisk -umount sdk1; >/tmp/usbtab

 

However I receive the response:

Failed to Unmount USB device sdk1.
Error Code: 0x2000

 

This would seem to imply that the USB disk is not mounted?

I have also tried replacing "sdk1" in the command with "sdq" which is present further up in the thread but that receives the same reply.

How do I determine what MY usb stick is being referred to as so that I know what needs to be unmounted to allow the drives to spin down?

I am running "XPEnology_DS3612xs_3211-repack-trantor-v1.2" on an HP Microserver N54L.

 

TIA! :smile:

Link to post
Share on other sites

How do I determine what MY usb stick is being referred to as so that I know what needs to be unmounted to allow the drives to spin down?TIA! :smile:

Try mount command without any options. It should list all mounted devices. Found the one that matches your USB and take a note of the device name.

Link to post
Share on other sites

How do I determine what MY usb stick is being referred to as so that I know what needs to be unmounted to allow the drives to spin down?TIA! :smile:

Try mount command without any options. It should list all mounted devices. Found the one that matches your USB and take a note of the device name.

 

Thanks, this is the output from the MOUNT command:

DiskStation001> mount
/dev/root on / type ext4 (rw,relatime,user_xattr,nosynoacl,barrier=1,journal_checksum,data=ordered)
/tmp on /tmp type tmpfs (0)
none on /dev/pts type devpts (gid=4,mode=620)
/sys on /sys type sysfs (0)
/proc/bus/usb on /proc/bus/usb type usbfs (0)
/dev/vg1000/lv on /volume1 type ext4 (usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl)

 

I only see /proc/bus/usb there that seems to reference "usb" in anyway, and (from the little I know of Linux) I don't believe THAT is the drive?

Link to post
Share on other sites

In addition to the above, (and perhaps related....):

 

I am running "XPEnology_DS3612xs_3211-repack-trantor-v1.2" on an HP Microserver N54L, but I CANNOT perform a 'reset'. If I select 'restart' from the DSM UI, then box goes down, goes through the bios, but then when it attempts to come back up it behaves as if the USB stick is not installed (just a flashing white cursor on the VGA output). If I physically power off, and then power on the box the USB key is seen at boot and all boots properly the way it is supposed to.

 

Is not being able to 'restart' a shortcoming of the trantor v1.2, or do I have something strange going on (and if so can anyone assist me in where / what to look at! - Thanks :smile: )

Link to post
Share on other sites

Sooo.. (just in case anyone is interested!)

 

I decided I had to find out the cause of the reboot issue, so I created a new USB boot drive with "SystemRescueCd" on it, tested it, and sure enough IT was able to reboot as much as it liked and not be lost.

So then I used the USB stick that I had been using for XPEnology and loaded that with "SystemRescueCd" as well... it booted fine from an "Off" cold start, but as per XPEnology would NOT be recognised on a reboot.

I've now taken my second USB stick, re-imaged that with XPEnology and I'm pleased to report that:

 

a ) It DOES now reboot and reload without a problem.

 

b ) The 'mount' command DOES now show my USB stick:

 

/dev/root on / type ext4 (rw,relatime,user_xattr,nosynoacl,barrier=1,journal_checksum,data=ordered)
/tmp on /tmp type tmpfs (0)
none on /dev/pts type devpts (gid=4,mode=620)
/sys on /sys type sysfs (0)
/proc/bus/usb on /proc/bus/usb type usbfs (0)
/dev/sdq1 on /volumeUSB1/usbshare type ext4 (nodelalloc,synoacl)
/dev/vg1000/lv on /volume1 type ext4 (usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl)

 

So it seems ALL of my problems were related to this damn old 1GB HP USB stick I had laying around. :evil:

Weird thing is, the one I am NOW using is a very similar looking, unbranded, 1GB USB stick, with a another company name emblazoned on the cover.

 

Anyway, finally I might be able to make some headway with my server, I just wanted to update this thread so that ( a ) other people would know what was going on, and ( b ) If I am absent minded enough to try and use the HP stick again at some point in the future I might stumble across this thread again in order to slap myself! :grin:

Link to post
Share on other sites

hi all , I found this forum by chance and I'm glad for it

I have one n36 hp proliant , and at the time I made the change in the bios for the n36 and I have been working with windows 7 and windows 2008 without any problem

 

Then use this n36 with freenas , I was testing a while but leave it parked for I saw quite difficult to handle , one day let me and this machine synology yes I enjoyed it.

 

I've been reading all n40l proliant subforum and there are many threads , and lots of information but for a beginner like me, I lose to much information

 

I've tried several versions 3211, 3810 etc, and I've made ​​the change in hexadecimal file "var " , I put up the n36 server with USB disk, and load but stays on one point: " 50.71177 findhostd uses obsolete ( PF_INET , SOCK_PACKET )

 

from another computer that I have connected to the switch, I launch the synology assistant program, I listed the two network cards that I have , with their corresponding mac address changed

 you indicate that I load the file. pat and then ask me the password, I get an error code 38 appears, and he stands

 

I need to do some step?

 

There a manual for dummies ?

 

thank you very much for your help

Link to post
Share on other sites
  • 2 weeks later...

I had the same problem and it turned out that was enough to enter the IP of my HP in the browser and you can already install file. pat

dtovee wrote:

Help! & first post to this forum so I hop it ends up in the right place.

 

I can't seem to see what I am doing wrong but I can't seem to get the installer on the USB stick to run without errors and then stopping.

 

I have tried XPEnology_DS3612xs_2668_4.1++ and the one in this forum synoboot_microserver.img

(https://docs.google.com/file/d/0B5tpWhE ... BkN3c/edit).

I used the Win32 Disk Imager to install it on three different USB sticks.

The microserver seems to boot from the memory stick OK but then gets stuck. It seems to see the network card OK but then:

"...

[ 13.552788] sde: sde1 sde2

[ 13.559352] sd 4 :0 :0 :0 [sde] No Caching mode page present

[ 13.559418] sd 4 :0 :0 :0 [sde] Assuming drive cache : write through

[ 13.559476] sd 4 :0 :0 :0 [sde] Attached SCSI removable disk"

 

My HP N40L microserver is standard except it has 8GB of ram, a DVD drive and a Seagate 3TB (it still has the original 250GB installed). I have disconnected the Seagate & DVD ROM.

 

Can anybody give me a hint to where I am going wrong as I would really like to have a go at running this system?

Link to post
Share on other sites
  • 2 weeks later...

DSM 4.3 build 3810++

I have a lot of errors in my /var/log/messages of type:

 

Dec 15 22:45:06 zeus btacd: auto_connect.cpp:247 Failed to get manager. Try to restart bluetoothd...
Dec 15 22:45:06 zeus btacd: auto_connect.cpp:252 Failed to get manager again.
Dec 15 22:45:06 zeus btacd: btacd.cpp:75 Device list is NULL.
Dec 15 22:45:06 zeus bluetoothd[2711]: opening L2CAP socket: Address family not supported by protocol
Dec 15 22:45:06 zeus bluetoothd[2711]: Server initialization failed
Dec 15 22:45:06 zeus bluetoothd[2711]: Unable to start SCO server socket
Dec 15 22:45:06 zeus bluetoothd[2711]: Failed to init audio plugin
Dec 15 22:45:06 zeus bluetoothd[2711]: Can't open HCI socket: Address family not supported by protocol (97)
Dec 15 22:45:06 zeus bluetoothd[2711]: adapter_ops_setup failed

 

It occurs every 4-5 seconds. I haven't plugged in any bluetooth USB dongle. I do I disable this deamon?

Link to post
Share on other sites

Kinda solved it.

With following command

zeus> ps | grep "btacd"
7259 root     20096 S    btacd
7260 root     20096 S    btacd
7261 root     20096 S    btacd
7287 root      3200 S    grep btacd

I found the right process and killed the PID with

kill 7259

and my message log retired.

Link to post
Share on other sites
Has anyone installed 4.3 and found that the files transfer has slowed down?

 

I've got 4.2 running on my N54L MicroServer, and 4.3 update 3 on my N36L.

I haven't noticed any slowdown in transfer speed between them, or from any of my Windows or OSX clients.

Link to post
Share on other sites

Trantor's build is based on Synology's DS3612xs. It's generic and runs ok on many systems including my N40L. But I have the feeling that it can do with a little less DS3612xs and more N40L.

When I look at the output of "dmesg" there is 4 NICs referenced, a few too many md's and more. Quite a few errors too.

[    6.461325] igb: Unknown symbol dca_remove_requester (err 0)
[    6.461504] igb: Unknown symbol dca_add_requester (err 0)
[    6.461559] igb: Unknown symbol dca_unregister_notify (err 0)
[    6.461601] igb: Unknown symbol dca_register_notify (err 0)
[    6.461645] igb: Unknown symbol dca3_get_tag (err 0)

Can we customize it some more and make it more HP N40L??

Link to post
Share on other sites
Trantor's build is based on Synology's DS3612xs. It's generic and runs ok on many systems including my N40L. But I have the feeling that it can do with a little less DS3612xs and more N40L.

When I look at the output of "dmesg" there is 4 NICs referenced, a few too many md's and more. Quite a few errors too.

[    6.461325] igb: Unknown symbol dca_remove_requester (err 0)
[    6.461504] igb: Unknown symbol dca_add_requester (err 0)
[    6.461559] igb: Unknown symbol dca_unregister_notify (err 0)
[    6.461601] igb: Unknown symbol dca_register_notify (err 0)
[    6.461645] igb: Unknown symbol dca3_get_tag (err 0)

Can we customize it some more and make it more HP N40L??

 

For my N54L running 4.2, I made the following changes:

 

internalportcfg="0x3f" 0000 0000 0011 1111 - 6 SATA

esataportcfg="0x00000" 0000 0000 0000 0000 - 0 eSATA

 

so for my USB ports, I have to get 0001 1111 1100 0000

usbportcfg="0x1fc0"

 

This seems to work okay, and I believe is correct for the MicroServer, as compared to the defaults.

 

I've not bothered to try these settings with 4.3, as it all just seems to work, but they'd probably still be appropriate.

Link to post
Share on other sites
Trantor's build is based on Synology's DS3612xs. It's generic and runs ok on many systems including my N40L. But I have the feeling that it can do with a little less DS3612xs and more N40L.

When I look at the output of "dmesg" there is 4 NICs referenced, a few too many md's and more. Quite a few errors too.

[    6.461325] igb: Unknown symbol dca_remove_requester (err 0)
[    6.461504] igb: Unknown symbol dca_add_requester (err 0)
[    6.461559] igb: Unknown symbol dca_unregister_notify (err 0)
[    6.461601] igb: Unknown symbol dca_register_notify (err 0)
[    6.461645] igb: Unknown symbol dca3_get_tag (err 0)

Can we customize it some more and make it more HP N40L??

 

The igb driver needs the dca module to be loaded before him. dca and igb are loaded by standard dsm boot.

These errors will be fixed in v1.1.

Link to post
Share on other sites

I installed 4.3 build 3810++ (repack v1.0) on my N40L with succes. I upgraded the standard 250GB with a WD 500GB 3.0Gbps disc and installed DSM succesfully. After that I installed one 1TB disc for data. My dmesg shows:

[    3.680064] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.686615] ata1.00: ATA-7: SAMSUNG HD103SI, 1AG01113, max UDMA7
[    3.686662] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[    3.693319] ata1.00: configured for UDMA/133
[    3.745945] scsi 0:0:0:0: Direct-Access     SAMSUNG  HD103SI                  1AG0 PQ: 0 ANSI: 5
...
[    3.996071] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.996737] ata6.00: ATA-9: WDC WD5000LPVT-00FMCT0, 01.01A01, max UDMA/133
[    3.996785] ata6.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[    3.997460] ata6.00: configured for UDMA/133
[    4.256631] scsi 5:0:0:0: Direct-Access     WDC      WD5000LPVT-00FMCT0       01.0 PQ: 0 ANSI: 5

 

This all makes sense. I have two volumes in DSM webadmin environment. Both show as Hybrid RAID (SHR) (Without data protection).

But I don't understand this part of my dmesg:

[    5.936187] md: Waiting for all devices to be available before autodetect
[    5.936233] md: If you don't use raid, use raid=noautodetect
[    5.936680] md: Autodetecting RAID arrays.
[    5.987362] md: invalid raid superblock magic on sda5
[    5.987408] md: sda5 does not have a valid v0.90 superblock, not importing!
[    6.026641] md: invalid raid superblock magic on sdf5
[    6.026687] md: sdf5 does not have a valid v0.90 superblock, not importing!
[    6.026747] md: Scanned 6 and added 4 devices.
[    6.026786] md: autorun ...
[    6.026824] md: considering sda1 ...
[    6.026872] md:  adding sda1 ...
[    6.026913] md: sda2 has different UUID to sda1
[    6.026956] md:  adding sdf1 ...
[    6.026997] md: sdf2 has different UUID to sda1
[    6.027062] md: created md0
[    6.027100] md: bind
[    6.027159] md: bind
[    6.027209] md: running: 
[    6.027524] bio: create slab  at 1
[    6.027739] md/raid1:md0: active with 2 out of 12 mirrors
[    6.027822] md0: detected capacity change from 0 to 2549940224
[    6.027957] md: considering sda2 ...
[    6.028020] md:  adding sda2 ...
[    6.028063] md:  adding sdf2 ...
[    6.028473] md: created md1
[    6.028514] md: bind
[    6.028563] md: bind
[    6.028617] md: running: 
[    6.029143] md/raid1:md1: active with 2 out of 12 mirrors
[    6.029226] md1: detected capacity change from 0 to 2147418112
[    6.029363] md: ... autorun DONE.
[    6.050623]  md1: unknown partition table
[    6.051047] RAMDISK: gzip image found at block 0
[    6.284247] VFS: Mounted root (ext2 filesystem) on device 1:0.

 

There are: unknown partitions, superblock and UUID messages that I don't like. Should I worry and try to fix before I add another 1TB for data redundancy?

Link to post
Share on other sites
I installed 4.3 build 3810++ (repack v1.0) on my N40L with succes. I upgraded the standard 250GB with a WD 500GB 3.0Gbps disc and installed DSM succesfully. After that I installed one 1TB disc for data. My dmesg shows:

[    3.680064] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.686615] ata1.00: ATA-7: SAMSUNG HD103SI, 1AG01113, max UDMA7
[    3.686662] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[    3.693319] ata1.00: configured for UDMA/133
[    3.745945] scsi 0:0:0:0: Direct-Access     SAMSUNG  HD103SI                  1AG0 PQ: 0 ANSI: 5
...
[    3.996071] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.996737] ata6.00: ATA-9: WDC WD5000LPVT-00FMCT0, 01.01A01, max UDMA/133
[    3.996785] ata6.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[    3.997460] ata6.00: configured for UDMA/133
[    4.256631] scsi 5:0:0:0: Direct-Access     WDC      WD5000LPVT-00FMCT0       01.0 PQ: 0 ANSI: 5

 

This all makes sense. I have two volumes in DSM webadmin environment. Both show as Hybrid RAID (SHR) (Without data protection).

But I don't understand this part of my dmesg:

[    5.936187] md: Waiting for all devices to be available before autodetect
[    5.936233] md: If you don't use raid, use raid=noautodetect
[    5.936680] md: Autodetecting RAID arrays.
[    5.987362] md: invalid raid superblock magic on sda5
[    5.987408] md: sda5 does not have a valid v0.90 superblock, not importing!
[    6.026641] md: invalid raid superblock magic on sdf5
[    6.026687] md: sdf5 does not have a valid v0.90 superblock, not importing!
[    6.026747] md: Scanned 6 and added 4 devices.
[    6.026786] md: autorun ...
[    6.026824] md: considering sda1 ...
[    6.026872] md:  adding sda1 ...
[    6.026913] md: sda2 has different UUID to sda1
[    6.026956] md:  adding sdf1 ...
[    6.026997] md: sdf2 has different UUID to sda1
[    6.027062] md: created md0
[    6.027100] md: bind
[    6.027159] md: bind
[    6.027209] md: running: 
[    6.027524] bio: create slab  at 1
[    6.027739] md/raid1:md0: active with 2 out of 12 mirrors
[    6.027822] md0: detected capacity change from 0 to 2549940224
[    6.027957] md: considering sda2 ...
[    6.028020] md:  adding sda2 ...
[    6.028063] md:  adding sdf2 ...
[    6.028473] md: created md1
[    6.028514] md: bind
[    6.028563] md: bind
[    6.028617] md: running: 
[    6.029143] md/raid1:md1: active with 2 out of 12 mirrors
[    6.029226] md1: detected capacity change from 0 to 2147418112
[    6.029363] md: ... autorun DONE.
[    6.050623]  md1: unknown partition table
[    6.051047] RAMDISK: gzip image found at block 0
[    6.284247] VFS: Mounted root (ext2 filesystem) on device 1:0.

 

There are: unknown partitions, superblock and UUID messages that I don't like. Should I worry and try to fix before I add another 1TB for data redundancy?

 

And again: Synology installs the OS to EVERY hard drive. Meaning, sd[x]2 is a RAID array that contains the OS. There are no unknown arrays and partitions, simply ones that do not show up in the UI, on purpose (so that you cannot go and fuck around with them, to delete the whole system, etc.).

Link to post
Share on other sites

Does Synology install OS to every harddrive? Really?

How come in DSM both my volumes show 'Hybrid RAID (SHR) (Without data protection).' If Synology makes two partitions on disk if there is only one disk available, data protection is available. Correct?

Link to post
Share on other sites
Does Synology install OS to every harddrive? Really?

How come in DSM both my volumes show 'Hybrid RAID (SHR) (Without data protection).' If Synology makes two partitions on disk if there is only one disk available, data protection is available. Correct?

 

Well, I don't think that the post right above yours is trying to be funny when stating that the OS is written on ALL discs.

Your question about data protection is confusing: do you have one disk or two in the system?

Two partitions on the same harddiscs is NOT considered data protection: a crash of that drive will affect al your data.

If you have two drives, things are different.

Link to post
Share on other sites

I apologize, English is not my native tongue. I did mean "really", I'm not trying to be sarcastic or something. I just didn't know Synoloy/Xpenology installed OS on all drives. I find that strange and surprising.

I have one 2.5 inch sata drive (position 6, in optical drive bay) meant for system OS and one 3.5 inch sata drive (position 1) meant for data. When everything is up and runnig I'm adding a second identical 3.5 sata data disc for RAID 1 configuration.

 

So when I install the third drive for RAID 1 configuration, partitions on the already installed 3.5 data disc get replaced or changed?

Link to post
Share on other sites

You mixing up the system (OS) partitions and data partitions. They are different and allocated differently.

System partitions (small) are installed on all detected fixed drives. They shown as "initialized" and that provide redundancy for system to assure that its bootable as long as at least one drive exist. Its not user accessible area.

Rest of the drive's space is allocated for data partitions. Here you can get creative with volumes and RAIDs. You can remove and create them arranging on any manner you can fancy.

Link to post
Share on other sites
I apologize, English is not my native tongue. I did mean "really", I'm not trying to be sarcastic or something. I just didn't know Synoloy/Xpenology installed OS on all drives. I find that strange and surprising.

I have one 2.5 inch sata drive (position 6, in optical drive bay) meant for system OS and one 3.5 inch sata drive (position 1) meant for data. When everything is up and runnig I'm adding a second identical 3.5 sata data disc for RAID 1 configuration.

 

So when I install the third drive for RAID 1 configuration, partitions on the already installed 3.5 data disc get replaced or changed?

 

No need to apologize.

XPEH already gave more information on the allocation of the OS over all drives, so I hope that's clear now; it's just a matter of keeping the NAS's availability as high as possible.

You mentioned you've got two harddrives and planning on buying a third one. What you could do is create a disk group for your data on the 3.5 inch sata-drive for now and expand it with the new 3.5 data once that's there: that will increase the protection of your data, but will not increase the amount of available storage.

Perhaps you already have looked at the Raid-calculator on the Synology website (http://www.synology.com/en-global/suppo ... calculator) that shows you exactly what you can achieve when combining harddisks.

Good Luck!

P.s. My N54L needs a BIOS-hack to achieve high performance on the 6th bay, I assume the N40 needs the same.

Link to post
Share on other sites
Does Synology install OS to every harddrive? Really?

How come in DSM both my volumes show 'Hybrid RAID (SHR) (Without data protection).' If Synology makes two partitions on disk if there is only one disk available, data protection is available. Correct?

 

Try to use the search function, really, it's been explained at least a dozen times. But just for you, I will do so again.

Synology creates the following partition layout (minimal footprint shown, this is not the WHOLE layout!):

|MBR| System Partition, ~2GB, RAID1| Data space|

 

This is an initialized drive. The system partition gets all the OS data copied upon initialization, so that in case of a drive failure, another drive can take over and boot the OS. The data space part is available to the user, to create volumes.

 

It says "Hybrid RAID (SHR) (without data protection)" because you created a volume with such parameters, made up of all your drives "data spaces". So no, your statement is not correct.

 

This is pretty much like partitioning your Windows computer into two: a C drive for the system, and a D for data. Even though there are two partitions, none of them are available for "data protection". Besides, what would be the point of halving the disk for RAID? If the disk fails, you can't use it any more, no matter how many duplicates you had on it.

 

Data protection on Synology will only be available with 2 or more disks. But if you have only one disk, then there's no point in running a NAS with a specialized OS - Windows Server would be completely sufficient.

 

I apologize, English is not my native tongue. I did mean "really", I'm not trying to be sarcastic or something. I just didn't know Synoloy/Xpenology installed OS on all drives. I find that strange and surprising.

I have one 2.5 inch sata drive (position 6, in optical drive bay) meant for system OS and one 3.5 inch sata drive (position 1) meant for data. When everything is up and runnig I'm adding a second identical 3.5 sata data disc for RAID 1 configuration.

 

So when I install the third drive for RAID 1 configuration, partitions on the already installed 3.5 data disc get replaced or changed?

 

No, it is not strange. As I said before, it is so even if any disk fails, you can still boot the OS and see what's the problem.

 

No, nothing will be replaced on the disk that already is in the storage volume. Synology will initialize the second disk, and you can extend the array onto it, but I'm not sure that SHR allows conversion into RAID1. Maybe staying with SHR and adding a third, identical drive would be a good idea?

 

 

You mentioned you've got two harddrives and planning on buying a third one. What you could do is create a disk group for your data on the 3.5 inch sata-drive for now and expand it with the new 3.5 data once that's there: that will increase the protection of your data, but will not increase the amount of available storage.

Perhaps you already have looked at the Raid-calculator on the Synology website (http://www.synology.com/en-global/suppo ... calculator) that shows you exactly what you can achieve when combining harddisks.

Good Luck!

P.s. My N54L needs a BIOS-hack to achieve high performance on the 6th bay, I assume the N40 needs the same.

 

Actually, a better solution would be keeping the 2.5 drive separately, and having the two 3.5 drives work the array out. 2.5" drives have usually slower performance, worse throughput, and higher fault-rate. I wouldn't really trust my sensitive data on a 2.5" drive, especially if it's touched frequently.

 

That drive would be perfect for serving OS-specific stuff, e.g. if you want to run the Web Server service, or download apps, etc.

 

All the NxxL series (N36L, N40L, N54L) need the BIOS mod, as they're basically the same board, but with slightly different CPU. I'd suggest the latest, November 2013 release, hacked. It got rid of the pinkeye problem for me.

Link to post
Share on other sites

All the NxxL series (N36L, N40L, N54L) need the BIOS mod, as they're basically the same board, but with slightly different CPU. I'd suggest the latest, November 2013 release, hacked. It got rid of the pinkeye problem for me.

fonix232 - please explain - or link.

I haven't heard about the "pinkeye problem"?

And I'm curious if there is a newer BIOS to my little baby - what have been changed. HP only states that a hang issue in Win2012R2 has been solved.

 

At the moment I'm using TheBay 041, which is working as expected.

Edited by Guest
Link to post
Share on other sites
Guest
This topic is now closed to further replies.