AndyMcC

Gottit guys, thanks. It's a bit of a learning curve for me, not done much sysadmin stuff for a decade or so.. eg. I still think of USB as a dodgy 'consumer' thing.. lol.. I could always have two copies of the USB stick fitted, then if one dies it'd be a quick job to flip the BIOS to boot from the other one. I intend to do some DR testing with this rig before comitting it to a full production role with all my precious data on it. I still haven't figured out how I'll do backups.. My NC365T loads the 'igb' kernel module, Intel 82580 chip, and is device id PCI\VEN_8086&DEV150E.

Hi, (1st. post so be nice..) I've not used DSM before, but it looked like an interesting option for a new home/small business NAS I need to build. I just installed DSM 6.2.2/DS3615 onto a HP Microserver N54L, using Jun's loader 1.03b. The system has two disks currently in RAID1. I fitted an HP NC365T 4-port card prior to the installation. This was all quite straightforward. However, I find that after installation, the installation USB drive must remain present, for the system to start up ? This is no good at all, as a fundamental requirement for the system is that there should be no storage devices that are single points of failure. I had assumed, that DSM would install each hard disk with a working boot environment, so the system could be started up in the event that any one disk failed. Is this not the case ? If this is a design limitation with Xpenology, or if it can be fixed, I'd like to know ASAP... Thanks.