Kali Linux filesystem is corrupted after install

[Headline]

Hello,
I've been trying to install Kali Linux on my laptop for 3 days now. After I installed it, I do 'apt update && apt upgrade'. And after some time he tells me 'The file system is read-only'. Then I typed 'fsck' and at the next reboot after about 5 minutes he tells me the same 'The file system is read only'.
I found out I can not boot from MBR, just from GPT for some reason.
I have also looked at some tutorials on the Internet, but nothing helped, so I'll ask in the Official Forum.
And after I run fsck I get errors after every reboot.


System information:


CPU: Intel Apollo Lake N3350
GPU: Intel HD Graphics500 650MHZ
RAM: 4GB
ROM: 64GB
Screen size: 14 inches
Resolution: 1366 * 768 TN
WIFI: WIFI 802.11b / g / n
Bluetooth: 4.0


Windows was previously installed on the laptop, but I would like to use it as a Kali laptop.


With regards,


Headline

[Mister_X]

What command do you run that leads to the filesystem being read only? Exact commands and program outputs will help.

What make you say it can't boot from MBR?

What official forum are you talking about?

Just FYI, ROM stands for Read-Only Memory, you probably mean to write SSD/HDD/Disk

[Headline]

Hello,

What command do you run that leads to the filesystem being read only? Exact commands and program outputs will help.

I only typed 'apt update' (that works) and at 'apt upgrade' it says after some time 'File system is read-only'

What make you say it can't boot from MBR?

I actually want to dualboot with Windows after I set the Partition Table to MBR my disk were gone (in the BIOS/UEFI) and Windows won't install too.

What official forum are you talking about?

I mean this forum, because it is the official Kali Linux forum, isn't it?

Just FYI, ROM stands for Read-Only Memory, you probably mean to write SSD/HDD/Disk

I only copied it from the Amazon Listing. It can be a misunderstanding, because it stands at many Amazon Listings e.g. Smartphones etc.

Best Regards,

Headline

[Mister_X]

I mean the WHOLE output from the command that resulted in the error message. Knowing what leads to an error message often helps.

Could you run df -h and post the results? I suspect you don't have enough storage on the system.

Regarding MBR/GPT, I'm pretty sure I've done MBR install of Windows 10 and it worked just fine.

I thought you mentioned you would post to another official kali forum.

[Headline]

Hello,

That's the problem, I do not know when and with which commands it occurs, because it is quite different when it occurs. Sometimes with 'apt upgrade' or sometimes later with other commands. I wait and hope until the error message occurs.


I usually have 64 GB eMMC but here is the message from 'df -h':

root@kali:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 378M 6.4M 372M 2% /run
/dev/mmcblk1p2 53G 11G 40G 22% /
tmpfs 1.9G 8.3M 1.9G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/mmcblk1p1 511M 132K 511M 1% /boot/efi
tmpfs 378M 12K 378M 1% /run/user/133
tmpfs 378M 28K 378M 1% /run/user/0
root@kali:~#

The laptop I use for this probably does not support MBR booting. And Windows showed me that he can not install it on EFI systems because of this MBR.

Best Regards,

Headline

[Mister_X]

There is enough storage, so ruling that out.

Could you show the exact output when the error happens? Clear dmesg before running the update (dmesg -c) and give the output after the error happens.

[broomdodger]

I usually have 64 GB eMMC but here is the message from 'df -h'
...
/dev/mmcblk1p2 53G 11G 40G 22% /
...

Are you trying to install on an SD Card?

[Headline]

Hello,

I run the System now for 1 Day and the errors are starting again (These are other errors that I usually get):

IMG_20181126_222919copy.jpgIMG_20181126_222959copy.jpgIMG_20181126_223011copy.jpgIMG_20181126_223019copy.jpg

The laptop will probably continue to run, but it does not make sense to keep it running like this.

The laptop will probably continue to run, but it does not make sense to keep it running like this.

I install it on the internal eMMC, but there is a Slot for an HDD/SSD too. This can't be the problem, can it?

Best regards,

Headline

[Mister_X]

I still don't see that apt update caused the issue. The eMMC might be broken.