Posts by mglae
-
-
Do you really expect that I'm able to theoretically choose the the correct combination of uid, gid, forceuid and forcegid parameters needed in your configuration?
-
LE is useing the quiet kernel parameter by default. If you did not have removed it before to see the messages, systemd was starting logging because of a seen error.
-
-
Read "FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS" in man mount.cifs
-
1. The kernel file can not be opened. But the legacy image was only created to in case the usual GPT disk is not possible.
2. The size of the used stick is unknown so we start with a small 32MiB file system that is expanded at first boot.
The filesystem repair may have been started because you pulled the stick before any data was flushed.
A. Don't be afraid of the installer, you have to select the installation, choose the disk and then being asked twice if you really like to erase the HD.
B. We do use a GPT image. The changes will be used if accepted by the team.
-
Usually a log is generated when kodi crashed and is restarted. Use pastecrash or the crash log uploader of LibreELEC-Settings.
-
1. Yes, write 100 times: there is no /etc/fstab used in LE.
With UUIDs this should work. Only with a second copy attached the same time you don't know which is mounted.
2. A long we don't know why the LE image is not accepted this cannot be corrected. Use what is working.
I've created two additional test images, please test on a spare stick if you see the syslinux boot messages.
-
1.) The randomly generated UUIDs can be read from any linux system and then stored in the syslinux.cfg. LE is not using /etc/fstab.
boot=/dev/sdb1 disk=/dev/sdb2 is possible but not reliable because it depend on the disk initialization order. Another possibility is to use boot=LABEL=xxx disk=LABEL=yyy if the file system labels are defined.
The UUID was not incorrect, it still pointed to the original file system of the copied syslinux.cfg
2) No. ISO is read only.
Boot problems are very rare, although reported from time to time.
-
Great.
You can create an universal service:
Code: [email protected][Unit] Description=Wait for SMB server After=time-sync.target [Service] Type=oneshot ExecStart=/bin/sh -c "until nc -z %I 139;do sleep 1;done;sleep 5" RemainAfterExit=yes
To use it in the mount service:
-
2. Does this mean I will have to do manual config every time there is a new install?
It is the nature of UUIDs to be unique. So yes, with any new created file system.
3. On my current config ( Syslinux 6.0.4 boot showing fat32 in my 14.9 GB USB space, and copy over Kernel and System files), how do I add ext4 partition to enable run mode?
Shrink the fat32 partition and create an additional ext4 one. (Don't forget to replace the disk=UUID= in syslinux.cfg)
I'm not aware of any Windows tool capable of doing this. Use e.g. gparted from any Linux distribution or Gparted Live.
-
Now it's failing with timeout. Try adding ;sleep 5 after the done.
-
Now the error message is different: "Could not mount UUID=1706..."
syslinux.cfg must have matching UUIDs. Replace 1706-4700 with 0E96-8A79.
But then you can only boot installer and live. For run the second ext4 partition (sdb2) is required.
-
-
Now I'm confused: do you have always seen the syslinux boot screen?
4. Question: Can I type anything at the debug shell to troubleshoot ?
In this case:
-
Which thread? My web search foo seem not to be good enough to find it.
To shorten this thread I've created an empty legacy boot only image with DOS partitioning scheme. After creating the stick you have to copy the LINUX and SYSTEM files of the desired LE release.
-
I've no knowledge about the structure of an Ubuntu UUI stick therefore I can't answer this question.
-
When the Dell heuristic is not accepting the disk layout in legacy boot mode no configuration change can help.
If you succeed in creating an disk image that boot on the Dell into any linux boot loader (e.g syslinux or grub) LibreELEC can be manually added to it.