« previous next »
Pages: [1]

Author Topic: Copy2Ram broken on 4.3.5  (Read 17778 times)

The_Raven

  • Jr. Member
  • **
  • Posts: 53
Copy2Ram broken on 4.3.5
« on: June 27, 2018, 10:36:09 AM »
Seemes like copy2ram is broken on new plop.
Boot ends in "No space left on the device" message.
Is the ramdisk to small?
Maybe because i added some additional drivers (bnx2)?
Logged

Elmar

  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • a command shell is enough to do amazing things
Re: Copy2Ram broken on 4.3.5
« Reply #1 on: June 27, 2018, 14:32:11 PM »
How much RAM has your computer?

Regards
Elmar
Logged

The_Raven

  • Jr. Member
  • **
  • Posts: 53
Re: Copy2Ram broken on 4.3.5
« Reply #2 on: June 27, 2018, 14:35:44 PM »
512GB  ;D

Tested ond diffrent systems.
Funny: Only USB-Stick is not working. PXE works. :o
Logged

Elmar

  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • a command shell is enough to do amazing things
Re: Copy2Ram broken on 4.3.5
« Reply #3 on: June 27, 2018, 14:40:36 PM »
Quote from: The_Raven on June 27, 2018, 14:35:44 PM
512GB  ;D

What! Really!?!

When you boot from USB without copy2ram, whats the size of rootfs? You get that info with 'df -h'.
Logged

The_Raven

  • Jr. Member
  • **
  • Posts: 53
Re: Copy2Ram broken on 4.3.5
« Reply #4 on: June 27, 2018, 14:55:54 PM »
Quote from: Elmar on June 27, 2018, 14:40:36 PM
What! Really!?!
Yes  ;)
Code: [Select]
              total        used        free      shared  buff/cache   available
Mem:      528350304     1077580   526010832       10200     1261892   524925200
Swap:        999996           0      999996
It is a server btw.

Quote from: Elmar on June 27, 2018, 14:40:36 PM
When you boot from USB without copy2ram, whats the size of rootfs? You get that info with 'df -h'.
USB: 1,6GB, used 64MB.
PXE: 932MB, used 394MB
Logged

Elmar

  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • a command shell is enough to do amazing things
Re: Copy2Ram broken on 4.3.5
« Reply #5 on: June 27, 2018, 15:06:10 PM »
Usually, the rootfs gets 50% of the RAM. Thats the default of the mount command.

I will update the code for copy2ram, to allocate at least the required space for rootfs.
Logged

The_Raven

  • Jr. Member
  • **
  • Posts: 53
Re: Copy2Ram broken on 4.3.5
« Reply #6 on: June 27, 2018, 15:59:43 PM »
Wait, something is strange :o
I use the i486 version of plop.
And it see's "only" 1942196kb of RAM.
Why?
If it has only <2GB, and the rootfs is 1.6GB -> no wonder that it does not work!
But i ask me why is the rootfs 1.6GB when booting from USB and only 932MB from PXE? :o
Maybe because of the customized initrd?
Logged

Elmar

  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • a command shell is enough to do amazing things
Re: Copy2Ram broken on 4.3.5
« Reply #7 on: June 27, 2018, 16:04:49 PM »
The i486 version should see about 3 GB RAM.
Logged

The_Raven

  • Jr. Member
  • **
  • Posts: 53
Re: Copy2Ram broken on 4.3.5
« Reply #8 on: June 27, 2018, 16:07:25 PM »
3.2GB i know. But it sees only <2GB. :o

Option 1: Find out why it see's only 2GB
Option 2: Find out why rootfs need 1.6GB
Logged

Elmar

  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • a command shell is enough to do amazing things
Re: Copy2Ram broken on 4.3.5
« Reply #9 on: August 27, 2018, 13:55:29 PM »
I updated the copy2ram script. It automatically resizes the rootfs, if required.

Please try it.

https://www.plop.at/en/ploplinux/upcoming/index.html
Logged

The_Raven

  • Jr. Member
  • **
  • Posts: 53
Re: Copy2Ram broken on 4.3.5
« Reply #10 on: September 04, 2018, 15:42:48 PM »
Sorry for the late response. I am busy ATM.
But i will try it for sure!  8)
Give you feedback when done.
Logged

The_Raven

  • Jr. Member
  • **
  • Posts: 53
Re: Copy2Ram broken on 4.3.5
« Reply #11 on: September 19, 2018, 17:04:44 PM »
Tested and it did not work.
4GB Ram (3GB available), Rootfs 1.5GB, Required 52GB :o
Looks like it tries to copy my wohle usb-pen to ramdisk (it is a 64GB-Pen but with 52GB partition).
And i ask me why is rootfs so big? Is this normal?

Edit: Ok, can not add picture sorry.
Logged

Elmar

  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • a command shell is enough to do amazing things
Re: Copy2Ram broken on 4.3.5
« Reply #12 on: September 19, 2018, 18:23:10 PM »
 ??? yes, you are right.

But the fix is easy. Replace your syslinux/kernel/initramfs.gz with this one https://download.plop.at/tmp/initramfs.gz
Logged

The_Raven

  • Jr. Member
  • **
  • Posts: 53
Re: Copy2Ram broken on 4.3.5
« Reply #13 on: September 20, 2018, 08:12:22 AM »
Kernel-Dump ::)
I have i486 kernel, initramfs is 64bit right?
Logged

Elmar

  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • a command shell is enough to do amazing things
Re: Copy2Ram broken on 4.3.5
« Reply #14 on: September 20, 2018, 08:22:02 AM »
Yes, 64 bit.

Use this for 32 bit https://download.plop.at/tmp/initramfs32.gz

You have to rename the file to initramfs.gz.
Logged

The_Raven

  • Jr. Member
  • **
  • Posts: 53
Re: Copy2Ram broken on 4.3.5
« Reply #15 on: September 20, 2018, 10:08:04 AM »
Now it works!
Required: 482432kb  8)
Logged

Elmar

  • Administrator
  • Hero Member
  • *****
  • Posts: 2491
  • a command shell is enough to do amazing things
Re: Copy2Ram broken on 4.3.5
« Reply #16 on: September 20, 2018, 10:35:56 AM »
Great. I make a minor release for the Live Version.
Logged

The_Raven

  • Jr. Member
  • **
  • Posts: 53
Re: Copy2Ram broken on 4.3.5
« Reply #17 on: April 01, 2020, 12:38:57 PM »
Very important to know:
If you get the error "no space left on the device", and you boot from syslinux, keep in mind that the folder "/syslinux" is loaded to ram!
If there are too many things inside this folder, you get this error.
« Last Edit: April 01, 2020, 19:44:07 PM by The_Raven »
Logged
Pages: [1]
« previous next »