On 1/13/21 11:45 PM, Jamenson Espindula via lfs-dev wrote:
Em qua., 13 de jan. de 2021 às 12:47, Pierre Labastie via lfs-dev
<lfs-dev@lists.linuxfromscratch.org> escreveu:
On Wed, 2021-01-13 at 10:05 -0300, Jamenson Espindula via lfs-dev
wrote:
Looks like you haven't send the whole story. You should have seen
something like:
Mounting virtual file systems: /run /proc /sys /dev
+ maybe an error message before "FAILURE ..."
The mail subject tells "read-only file system failure", but there is no
evidence in the error message you sent us...
Thank you for your response. In fact, there are other error messages.
I am sorry.
= = = = = Begin of transcription = = = = =
chmod: cannot access '/run/lock': No such file or directory
Lets start here. That is the very 1st boot script. It is doing:
mount /run
mkdir -p /run/lock /run/shm
chmod 1777 /run/shm /run/lock
And failing.
-----
What we need is to see your file system. What is the output of
'ls /' (or 'ls /mnt/lfs' from the host). It should be.
bin dev home lib lost+found mnt proc run sources sys usr
boot etc lib64 media opt root sbin srv tmp var
Second don't just say the /etc/fstab is right. Paste it in. It should
be close to:
/dev/<your dev> / ext4 defaults 1 1
/dev/<your dev> swap swap pri=1 0 0
proc /proc proc nosuid,noexec,nodev 0 0
sysfs /sys sysfs nosuid,noexec,nodev 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /run tmpfs defaults 0 0
devtmpfs /dev devtmpfs mode=0755,nosuid 0 0
The last five lines should be identical to what you have. If /run is
correctly mounted as a tmpfs, then the next two lines should not fail.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
