Pro/Forums - View Single Post

Werner_q · 03-30-2009, 07:55 AM

I just stumbled across the same Problem, unfortunately I completely killed (somehow, don't ask ...) the Guardian OS. Initially I just wanted to upgrade from 4x250GB to 4x1TB, and since I saw the SnapServer 410 beeing sold with that config, I thought, it wouldn't be a Problem.

Ok, so I made the same experiences, Drive swapping, all fine - until reboot. When I successfully had destroyed GuardianOS even on the original Disks , I mailed Overland Storage Support - they told me I had to buy a Warranty Extension ($500,-) before they could send me the OS-Image. I have already payed for that, so w.t.f.; but didn't want to arguee with them.

Next, I decided to try FeeNAS, inserted an PCI Graphics Card, attached USB-Keyboard and USB-CD-ROM. Might be worth to mention, that an ATI Rage IIc didn't work (no Picture after BIOS Post-Messages). I found a stone-old S3Trio64 working perfectly. Probably you don't even need a graphics card when you connect over the serial line. But its more fun (faster !) with a graphics card. Also you have to disable this Watchdog-thing in the BIOS (all other BIOS Options can stay unchanged).

And then I noticed that my (only ?) problem was the SATA-Controller, which stuck shortly after recognizing the first Drive !! And, funny thing, when I removed the Drive(s), rebooted FreeNAS from CD-ROM, re-attched the Drives once FreeNAS had booted, everything worked fine ! The Drives were recognized and working !

OK, BIOS Update for the SATA Controller (which is a SiI3114 - PCI to 4 Port SATA150):
The BIOS Version of SnapServer was 08.00.13 09/01/06, BIOS of SiI3114 was 5.0.56 dated 10-20-2005. In other Forums I learned, that this BIOS only supports Drives <=250GB, but there were newer BIOS Verisons.
On the Silicon Image Homepage you can find a "abbreviated BIOS intended for integration into system BIOS" 5.4.03 vom 09-22-2006.
With the "HP USB Disk Storage Format Tool" I made a MS-DOS-Boot USB-Stick and with the official AFUDOS.EXE from Ami I then saved the original SnapServer BIOS to file.
With the (probably not so official) MMTOOL.EXE 3.12 one is able to integrate the SiI-BIOS into the SnapServers Ami-BIOS (it's the fourth PCI Option ROM with Vendor ID 0x1095).
Save as, transfer to USB-Stick, flash with AFUDOS.exe and - Tadaahhh !!!

I was extremly happy that this worked for me, so I hope this will be helpfull/usefull to others. (What still is broken is the GuardianOS, but hey, FreeNAS doesn't look so bad after all ?)

03-30-2009, 07:55 AM	#10
Werner_q Cooling Neophyte Join Date: Mar 2009 Location: Austria Posts: 2	Re: Upgrade drives on a 410 I just stumbled across the same Problem, unfortunately I completely killed (somehow, don't ask ...) the Guardian OS. Initially I just wanted to upgrade from 4x250GB to 4x1TB, and since I saw the SnapServer 410 beeing sold with that config, I thought, it wouldn't be a Problem. Ok, so I made the same experiences, Drive swapping, all fine - until reboot. When I successfully had destroyed GuardianOS even on the original Disks , I mailed Overland Storage Support - they told me I had to buy a Warranty Extension ($500,-) before they could send me the OS-Image. I have already payed for that, so w.t.f.; but didn't want to arguee with them. Next, I decided to try FeeNAS, inserted an PCI Graphics Card, attached USB-Keyboard and USB-CD-ROM. Might be worth to mention, that an ATI Rage IIc didn't work (no Picture after BIOS Post-Messages). I found a stone-old S3Trio64 working perfectly. Probably you don't even need a graphics card when you connect over the serial line. But its more fun (faster !) with a graphics card. Also you have to disable this Watchdog-thing in the BIOS (all other BIOS Options can stay unchanged). And then I noticed that my (only ?) problem was the SATA-Controller, which stuck shortly after recognizing the first Drive !! And, funny thing, when I removed the Drive(s), rebooted FreeNAS from CD-ROM, re-attched the Drives once FreeNAS had booted, everything worked fine ! The Drives were recognized and working ! OK, BIOS Update for the SATA Controller (which is a SiI3114 - PCI to 4 Port SATA150): The BIOS Version of SnapServer was 08.00.13 09/01/06, BIOS of SiI3114 was 5.0.56 dated 10-20-2005. In other Forums I learned, that this BIOS only supports Drives <=250GB, but there were newer BIOS Verisons. On the Silicon Image Homepage you can find a "abbreviated BIOS intended for integration into system BIOS" 5.4.03 vom 09-22-2006. With the "HP USB Disk Storage Format Tool" I made a MS-DOS-Boot USB-Stick and with the official AFUDOS.EXE from Ami I then saved the original SnapServer BIOS to file. With the (probably not so official) MMTOOL.EXE 3.12 one is able to integrate the SiI-BIOS into the SnapServers Ami-BIOS (it's the fourth PCI Option ROM with Vendor ID 0x1095). Save as, transfer to USB-Stick, flash with AFUDOS.exe and - Tadaahhh !!! I was extremly happy that this worked for me, so I hope this will be helpfull/usefull to others. (What still is broken is the GuardianOS, but hey, FreeNAS doesn't look so bad after all ?) Last edited by Werner_q; 03-30-2009 at 08:12 AM. Reason: Poor English ...