forum.excito.com

You need to add the following lines at the end of the install.ini file (remove the wipe if necessary):
They were missing in the version 1.1 of the install archive, I've reuploaded a corrected version.

Thanks

The logs tells there is no image in the configuration so I need to see the content of the install.ini file first. The USB key does _not_ perform an upgrade, it's a simple install. It's fairly quick on the b3, usually no more than 2-3 minutes mostly depending of the total disk size being formatted. T...

Can you post the content of install.ini on your usb key ?

It's likely that U-Boot doesn't like too large ext3 filesystems. You could try to flash to the rodeus version available at http://install.excito.org/b3/uboot/beta/ using the instructions on the wiki page you mentioned earlier. It's more recent so it may work. I don't have 3tb drive to test it.

I just saw your edited comment, good news.

So with the default disk size, you get a 10g root, and it boots. Then you grew it to 2T and it still works. When you grow it above the 2T limit, the b3 won't boot anymore ?

The version you use is the version mentioned in the wiki. So this should not be a problem.

Just to be sure, when you try to boot what is the led pattern ? (purple then red or is it another sequence)

OK that seems fine. I need to run a couple of tests at home to try identify the cause of the red led. I'll get back to you in a couple of days.

Hello, I'll try to help you debug this. First, the ext3 signature error is not relevant, it's just a warning that there is exisiting data on the disk getting wiped. Do you know which version of u-boot your b3 is running ? If not can you run the rescue system and give the output of this command : str...

I've done a few tests and I got it to work on the stretch image of the b3. The main issue preventing the system from booting is the type of the partition created. You must set it to 29 in order for the kernel to autodetect the arrays on boot : root@b3:~# fdisk -l /dev/sda Disk /dev/sda: 149.1 GiB, 1...

It looks good. I'm going to have to test it on my b3 with a serial console to sort it out. I'll try to recreate your setup and see how it goes with your previously posted commands. I'll keep you updated in the next couple of days.

Can you show the output of fw_printenv ?

Small update to the stretch image, to fix mtd modules in the rescue/install system.

Sorry this is a bug of the rescue install os which doesn't load the proper module for the mtd device. I will fix that but all you need to do is load the proper module first : [root@b3-install devices]# modprobe m25p80 m25p80 spi0.0: m25p16 (2048 Kbytes) 3 ofpart partitions found on MTD device spi0.0...

It seems to work well.

You can connect either to the wan or the lan to a DHCP enabled network. Once the rescue system is up and running, the LED will animate with yellow and cyan colors to dictate the relevant part of the IP address acquired by DHCP.

That would probably work but I'd stay away from u-boot changes as I've seen a lot a problems with that at home. Why can't you boot the rescue system ? Is it because of the error about image None cannot be found ? That should not stop the rescue system from booting, but to fix it you need to comment ...