Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible issue with Entware mounting #2

Open
fonix232 opened this issue May 15, 2020 · 0 comments
Open

Possible issue with Entware mounting #2

fonix232 opened this issue May 15, 2020 · 0 comments

Comments

@fonix232
Copy link

Hey!

Following your PHP script, I've created an installer package that does the same, without the need of a PHP runner, or a separate server with qemu, but rather, right on the FileHub.

The script set is available here. As you can see, it follows your script step by step:

  1. Creates a temporary EXT2 chroot image for Entware to run the install in
  2. Mounts tempFS to $(pwd)/build
  3. Creates minimal viable file system for chroot, adds busybox and symlinks, mounts /dev and /proc
  4. Chroot's into $(pwd)/build, retrieves Entware install script, and runs it
  5. Installs busybox, entware-opt and dropbear packages
  6. Creates final extern_image, a 128MB EXT2 image, and mounts it to $(pwd)/entware
  7. Copies the $(pwd)/build/opt folder to $(pwd)/entware
  8. Destroys the original chroot and unmounts the images, cleaning up the remains
  9. Copies an updated rc.local to /etc, and runs etc_tools p to persist this change

The image is created properly, and for some mysterious reasons, my firmware (2.000.018) came with /opt existing, but /extern does not - which is why the rc.local changes are necessary. I also took some liberty to make the script itself a bit more dynamic.

This new rc.local runs fine on boot, however... When it is executed, the /data/*DiskN mounts do not exist yet, meaning it never succeeds on its own to mount these.

As you've previously managed to get it working, would you mind giving a few pointers on how to get this mount to work? I thought about adding some repeat retries to the script (try in first few minutes of boot), or possibly patching the script responsible for mounting the disk partitions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant