plugout.net

Hi all,

I installed the latest fvdw on my lacie, only the first disk plugged in, this seemed to work. Upon reinserting the other disks (2 and 5, 3 and 4 are unused), and booting the nas up again, I reverted to the lacie firmware.
No big deal I figured, the original firmware was probably on one of those disks. I booted again, with only the first disk inserted: again the lacie firmware.

Weird...

Decided to do a reinstall, with all 3 disks plugged in. Seems to be fine. Just on the last step (use "reboot -f" to reboot), telnet gets disconnected, but the nas seems to stay on. I shut it down using the switch on the rear, and turned it back on. Again, I reboot to the lacie firmware.

I couldn't find another topic with this problem, but what could be the cause? The fvdw install seems to go fine, and the first time (with just one disk) I actually booted in fvdw and installed a few things etc.

Apart from this issue, the firmware seems awesome. It gives this crappy lacie a second life, bringing it on par with synologies etc, possibly even better!

Hi

I think You read too quickly this topic viewtopic.php?f=7&t=1271#p7900

- Adding extra disks on multi drive devices : 5big1, 2big1, 5big2, 2big2, networkspace max v2 , after installing fvdw-sl on the system disk (sda) and upgrading the firmware to the latest version, you can add the other disks by following this instruction 3. Add additional disks
Do not use multiple system disks in multi disk nas, it will cause erratic behavior because the bootloader may use the wrong disk to load kernel and firmware.

Jocko wrote:Hi

I think You read too quickly this topic http://plugout.net/viewtopic.php?f=7&t=1271#p7900

- Adding extra disks on multi drive devices : 5big1, 2big1, 5big2, 2big2, networkspace max v2 , after installing fvdw-sl on the system disk (sda) and upgrading the firmware to the latest version, you can add the other disks by following this instruction 3. Add additional disks
Do not use multiple system disks in multi disk nas, it will cause erratic behavior because the bootloader may use the wrong disk to load kernel and firmware.

Awh, missed that part indeed!
One thing I had to to different from that guide: i had to plug in the other disk while the NAS was on. If I didn't and plugged them in while the nas was off, it would boot into Lacie's OS, as I didn't have any other device to wipe the drives with.

But all looks good now, thanks!