andreus wrote:I think you are having a similiar problem that "rmar" had.
The boot procedure is:rmar wrote:Did you try to do the factory reset? The red light, bla bla bla... Because I couldn't when this is happening
- On boot the cpu starts executing from some predefined address.
- This address is the entry point of u-boot in flash.
- U-boot detects if the reset button is pressed, and does the red light sequence
- U-boot tries load a kernel from sda10, and if that fails from sda6 (On a 2Big2 also sdb10 and sdb6 are probed, when sda fails)
- The kernel is started, with in the cmdline the rootfs specified, being sda7, read only. When a factory reset is requested, it's also specified in the cmdline.
- The kernel mounts sda7, and runs /sbin/init from it.
- /sbin/init checks if the cmdline specifies a factory reset, if yes, it basically reformats sda9, cleans sda10, and reboots.
If no, a unionfs is created from sda8 (ro) and snapshots on sda9 (the latest snapshot rw), and a rootswitch is done.
Booting continues from unionfs/sbin/init
- A new snapshot is created on sda9, and the rootfs in the capsule file is written to it.
- The kernel from the capsule file is written to sda10.
- When available, some scripts from the capsule are executed.
- The box reboots.
- The kernel is loaded from sda10, and sda7/sbin/init is executed.
- The new unionfs is created, with the new snapshot being the top layer.
- If available some cleanup script from the capsule is executed.
It would be worth a try to cleanup sda10:
Code: Select all
dd if=/dev/zero of=/dev/sda10