Kali Linux install failes read only file system

[Thomas van Dalen]

THIS POST SHOULD BE DELETED, im VERY sorry

 

Xorg.0.log

https://pastebin.com/hHAzB5Te

 

Hardware Summary:

https://pastebin.com/WQDVNR9K

 

partman:

https://pastebin.com/WLEQKqhx

 

syslog:

https://pastebin.com/DF4MZW1i

 

Following line in syslog got my attantion:

1. Sep  6 17:40:53 main-menu[774]: (process:13733): mkdir: can't create directory '/mnt/install': Read-only file system

 

Anyone done kali before? and know how to get a writable file system?

 

and

1. Sep  6 17:40:06 kernel: [  186.273924] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: errors=remount-ro

but there is no harware failure so im not sure why it thinks so, dont have this issue on a non VM  install (same disk)

 

 

Edited September 6, 2017 by Thomas van Dalen

[Squid]

Yup, the error is there.  Without your diagnostics however there's nothing to really put it into perspective.

[Thomas van Dalen]

1 hour ago, Squid said:

Yup, the error is there.  Without your diagnostics however there's nothing to really put it into perspective.

 

Posted at Kali its forum and found the solution myself.

 

Hereby the post, sorry to bother, this post should be deleted at all

 

syslog:
https://pastebin.com/DF4MZW1i

it says the disk is while, while its 30GB and empty before install

With auto disk with lvm im getting the below partitions.. Seems odd to me
https://imgur.com/xGdxJFn

EDIT: Just found out t hat the crypto volumes contains the lvm and the lvm volume contains the data and swap. It was just confusing cause when i look down to my hard disk, like tree, or filezilla its tree, android, all tree start at the root so the physical disk should be on top. 
Maybe you guys should think about it and change the way it looks by having the lvm volume beneath the /root of the disk itself...

Anyway looks like when we create the partition manually the sizes are correct.
I am Using unRAID as a hyper visor and the virtual disk size is 40.0 GB (42,949,672,960 bytes). 
When i let the installer partition automatically the sizes doesn't match up and in the log is every time says that the install failed, 
Sep  6 17:40:41 main-menu[774]: (process:13576): tar: write error: No space left on device

But when we followed this video on YouTube.. it all made sense. We did the partition manually and it worked directly.
https://www.youtube.com/watch?v=Z9pn2PYbDdA

There may be a bug in the installer which prevents us to auto create a full encryption disk with lvm.
I am willing to test and provide you with logs or you can even TV in my pc to see how it run.

Anyway,, I am in whatsoever and the install is completed now. Just wanted to share this information.