Internal drive MPC X SE

yes, that should work

The device is mmcblk1, thats the ssd for user. The mmcblk0 is for the system. I had the same Problem and for me it works. The fstab entry is /dev/mmcblk /media/az01-internal-sd ext4 rw 0 0. After the running e2fsck delete the fstab entry and reboot.

Sry, the right entry for fstab is /dev/mmcblk1 /media/az01-internal-sd ext4 rw 0 0

hello, thank you for your precious help! for the moment in fstab, I just have this: /dev/root / auto ro 0 1. I just add the line that you provided me?

first backup the fstab file
then add that line below to instruct the os to mount it at boot time.
Before you reboot to take this into account, issue a mount -av command, and check the fs is properly mounted (-a mount all entries from fstab). you see a message like "sucessfully mounted" if any error, revert back and let's us know

Patrick Lambotte wrote:hello, thank you for your precious help! for the moment in fstab, I just have this: /dev/root / auto ro 0 1. I just add the line that you provided me?

Yes, only add the line in a new line. Reboot and run e2fsck.

I have this error : root@mpc-key-61:~# e2fsck /dev/mmcblk1
e2fsck 1.45.6 (20-Mar-2020)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/mmcblk1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>

Found a gpt partition table in /dev/mmcblk1

it works thank you all, I added this line to fstab: /dev/mmcblk1p1 /media/az01-internal-sd ext4 rw 0 0 and did an e2fsck on this partition and everything is back to normal!! Great thank you

/etc runs off a fifo. if you edit anything in etc first do this:

umount /etc

otherwise you will contaminate the etc fifo. it is super-imposed from /media/az01-internal somewhere i forget the file path but if you contaminate it you may run into issues with timestamps on links and files being incorrect and it causing the system to be a bit of a jerk when you boot it up.

Once its unmounted then make your edits and reboot the machine and it should update the fifo in /media/az01-internal/whateverthehellitwasagain