XigmaNAS

Thank you.
I will check it.

Daoyama san,

Miss your request.

I am unable to test my server until 2nd week in March. Should you still want my server results, please let me know.

Hi all,

Just joined the forum a moment ago (because I get stuck at the same install loop again)

This time, I have to thanks for jasch, his info enlightened me. Below were my story:

I've got a HP N54L previously, during test I put 1 x 80G SATA + 2 x 4TB SATA into it, everything fine, I can boot with USB cdrom, install to either USB disk or local HDD (the 80GB is intended for this purpose) without issue.

A week later, I've got another set of computer, Asrock C2550D4i (Avoton quad-core) + 16GB ECC + Lian Li PC-Q25 case (with 5 hot swap 3.5" + 3 x 2.5" drive space). Because I want to make use of some even older HDD, so I pulled an old 60GB 2.5" from drawer (didn't use it on HP N54L due to no converting mount), other than that, I used the same HDD set from HP N54L (i.e. 80G + 2 x 4T), but this time I get exactly the same install loop. The installer never presents me any possible installation media, checking from the beginning of thread, I give up the 7-in-1 card reader (that's the only one can access CF card), using another single SD card reader and put a 8GB SD card in, still, no luck.

Until I read the comment from jasch, wow!!! My old 60GB 2.5" HDD exactly is a Toshiba HDD! I've never thought about this could be an issue (I've installed Ubuntu/Debian on the same setup and it was proven to be working, no error was found on Toshiba 60GB at all.), after pulling out that disk, installation process became normal (although it still prompted me weird device /dev/pass3 which is the Marvell controller itself) and I can choose to install to another USB stick or the 80G 3.5" internal drive, amazing!

To prove this is no an issue with FreeBSD 9.3, I also downloaded FreeNAS 9.3 to try, installation works even with the Toshiba drive in, I'm wondering why a specific brand of drive will trigger this issue.

Anyway, now we know the keyword for this install loop issue: Toshiba (not sure if 2.5" should be counted as well)

The same here!
HP N54L
Toshiba 2,5 " (MK1652GSX) >> No destination for installation
Pulled Toshi out insertetd Hitachi 3,5" instead >> Install works

The interesting thing:
This issue is known since about 3 Months, the actual Version has been released on 10th May, but the Flaw hasn't been fixed! It seems to be absolutely clear that this issue is Nas4Free specific while FreeBSD installs with present Toshiba Disks.


It seems that Nas4Free 9.3 is a "retrospective" OS, because it's about 25 years ago (or more) that HDDs from specific Vendors are Problematic in some constellations (it was the time of Master and Slave on PATA) *just kidding*

4 Months!!!!!!!
ANY NEWS!!!!!!!!!!!!!!!!!!

Yeah, I'm kinda screwed here. Trying to upgrade to 9.3.0.2.latest, and I'm getting the install looping. I've got 25x <Toshiba MBF2300RC DA07> 300GB drives that are part of my ZFS array, so I can't pull them. And of course I can't download a 9.2.x.x release any more... my NAS (and about 35 virtual servers) are down.

ccie4526 wrote:Yeah, I'm kinda screwed here. Trying to upgrade to 9.3.0.2.latest, and I'm getting the install looping. I've got 25x <Toshiba MBF2300RC DA07> 300GB drives that are part of my ZFS array, so I can't pull them. And of course I can't download a 9.2.x.x release any more... my NAS (and about 35 virtual servers) are down.

At least the installer for 10.1.0.2.1702 is able to read all my disks and let me install. I didn't really want to upgrade to the beta release yet, but now I don't have much choice.

ccie4526 wrote:

ccie4526 wrote:Yeah, I'm kinda screwed here. Trying to upgrade to 9.3.0.2.latest, and I'm getting the install looping. I've got 25x <Toshiba MBF2300RC DA07> 300GB drives that are part of my ZFS array, so I can't pull them. And of course I can't download a 9.2.x.x release any more... my NAS (and about 35 virtual servers) are down.

At least the installer for 10.1.0.2.1702 is able to read all my disks and let me install. I didn't really want to upgrade to the beta release yet, but now I don't have much choice.

Don't worry, same change is reflected to 9.3 branch.
So, you only need wait next 9.3 build.