SG-3100 M.2 install

mcury

Edit: Will look up in my logs later if I can get more information.

Thanks FSC830, any help would be much appreciated.

I did some tests here by making manual edits to /etc/fstab, and its working, however, eMMC is still being used during the boot process.

I know that because I wiped the entire eMMC and the system no longer boots
I suppose there is something different with the 23.01 firmware.

So now what I have is:

23.01 system installed in the eMMC, clean install.
Once it booted to the eMMC, edited /etc/fstab and pointed both entries to the M.2 disk which already has 23.01 installed.
Reboot and it works but not exactly what I want since I don't want to use the eMMC.
I would like it completely disabled.

stephenw10

At the Marvell > prompt (u-boot) enter:

setenv bootcmd 'run setLED; run m2boot;'
saveenv
reset

It should now boot from the m.2 ssd everytime

Steve

mcury

@stephenw10 said in SG-3100 M.2 install:

setenv bootcmd 'run setLED; run m2boot;'
saveenv
reset

Thanks stephenw10, I tried that but it didn't work.
According to the TAC, there is an env missing here in my system.
Unfortunately I can't test right now, but definitely I'll try later

I'll try:

At this moment, printenv shows m2dev=0, TAC suggested me to change it to 1 like this:

setenv m2dev=1
setenv bootcmd 'run setLED; run emmcboot;'
saveenv
reset

Then, once this env is applied, I'll try as you suggested:

setenv bootcmd 'run setLED; run m2boot;'
saveenv
reset

stephenw10

Hmm, well that's odd. Yes m2dev should be 1 by default on the 3100.

mcury

@stephenw10 said in SG-3100 M.2 install:

Hmm, well that's odd. Yes m2dev should be 1 by default on the 3100.

I did something horrible..
Believe me or not, I ran the command, env default -f -a

As I didn't know how to restore defaults, I created everything again, from scratch, all setenvs one by one, then confirmed if everything was correct using meld app.

Luck that during the TAC follow up, they asked me to send them the printenv, so I could just replicate that in my SG-3100 exactly like it was before.. Now its booting again :)

Edit1:
The good thing about all this is that I learned a lot.. Nothing like fire to make us learn something...

Edit2: Boot from M.2 with eMMC empty working.

Thanks every one for the help, and I have to say something.

The guys in the TAC are amazing, they helped me a lot and I only have TAC Lite..
I can say that I'm definitely a happy customer. Thanks Netgate!

eyes

What did you do to get it to boot from the M.2?

I have the same. Its stuck in the boot

Starting application at 0x00200000 ...

Can you post a copy of your printenv? plz

/simon

mcury

@eyes said in SG-3100 M.2 install:

Can you post a copy of your printenv? plz

I sold my SG-3100, bought a SG-4100..

You probably need to change the setting m2dev.

Check this: https://forum.netgate.com/topic/178623/sg-3100-upgraded-storage-to-m-2-but-disk-is-still-reading-emmc-storage

stephenw10

Yup almost certainly that issue. ^

There is a known bug in the 3100 installer that fails to update the uboot values. It requires you change them manually.

Steve

eyes

@stephenw10

The address its trying to boot from is that on the M.2 or Ram of the 3100?

I tried booting with m2dev=0 and another instance with m2dev=1

same result. stuck at the memory address
Starting application at 0x00200000 ...

I still have a working system installed on the emmc, is that an issue for the m.2 to work?

From the instructions I should use m2dev=0
since I use the long m.2 2280 scsi in the J10 slot.

https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/m-2-sata-installation.html

stephenw10

Usually you only need to change the bootcmd value from emmcboot to m2boot.

stephenw10

It may also be booting from the m.2 and then mounting root from eMMC confusing the issue.

mcury

@eyes said in SG-3100 M.2 install:

From the instructions I should use m2dev=0

To be able to boot from the M2 SSD, m2dev should be 1.
and setenv bootcmd 'run setLED; run m2boot;'

I always wipe the entire eMMC disk when using SSD to avoid the problem described below:

https://docs.netgate.com/pfsense/en/latest/troubleshooting/multiple-disks.html

Edit:

In addition to the described above, I usually set:

Create the file /boot/loader.conf.local and add to it:
hint.mmcsd.0.disabled="1"

eyes

@mcury

I might want to try to wipe the drive then

Before i do that. This is the M.2 I use.

Sata III is working with the device right?

https://www.proshop.dk/SSD/Intenso-SSD-M2-2280-SATA-III-High-Performance-240GB/2628894

stephenw10

If you were able to install to it as ada0 then it should be fine.

eyes

What is the command in U-boot to erase the eMMC? if i want to wipe it clean.

I cant do it in root, since its the active partition

mcury

I don't have that written down here, but as far as I remember, you will need:

1- Connect to the console
2- Boot the device in single user mode:

At the SG-3100 console press any key to interrupt the boot loader when you see:
Hit [Enter] to boot immediately, or any other key for command prompt.

At the prompt enter: boot -s

That will boot in single user mode to a question asking for a path to the shell, just press return to reach the # prompt.

3- Run the command to wipe the eMMC as described in the link posted above;
Wipe the first 1MB of the disk
dd if=/dev/zero of=/dev/mmcsd0 bs=1M count=1 status=progress
or:
Wipe the entire disk:
dd if=/dev/zero of=/dev/mmcsd0 bs=1M status=progress

Then, boot through USB drive and perform a normal install using ada0 drive.

@stephenw10 can you confirm if these steps are correct ? I really don't recall exactly what I did at that time..

stephenw10

You should be able to run run m2boot manually then choose single user mode to reach a prompt you can erase the eMMC from.

Or at the uboot prompt try: mmc erase 0 400000

jimp

I recently updated the 3100 M.2 install doc with better info on all this, so make sure you are following the new doc and not older instructions:

https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/m-2-sata-installation.html

FSC830

Just to still my curiosity...

I checked my Putty log from serial port and as far as I can see I did not run any printenv/setenv command when installing the 22.05 software at ada0.
Also I looked up in my downloaded manual which do not contain this recently added commands.

Because I installed m.2 devices in two appliances at nearly the same time without running in trouble, my question is: was that luck or does the issue only occur in special circumstances/releases?

Regards

stephenw10

I would have expected it to apply there if you added the SSD. Though looking at the internal bug report I opened for this it applied in 22.01-Beta and was present in 23.01 but I couldn't say for sure if it happened in 22.05.