pI need to fix the following problems
I do not have experience in linux, so please possible give me simply explanations and the code to type in command line and fix the problems, please!
I checked other threads and I found similar problems but non the same.
Question
manolis#manolis-300-0xx:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
netplan.io
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up grub-efi-amd64-signed (1.93.8+2.02-2ubuntu8.7) ...
Installing for x86_64-efi platform.
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent processing triggers for shim-signed:
shim-signed depends on grub-efi-amd64-signed; however:
Package grub-efi-amd64-signed is not configured yet.
dpkg: error processing package shim-signed (--configure):
dependency problems - leaving triggers unprocessed
Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Backgournd Informations
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
manolis#manolis-300-0xx:~$ echo ${BASH_VERSION%%[^0-9.]*}
4.4.19
manolis#manolis-300-0xx:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 1,9G 0 1,9G 0% /dev
tmpfs 387M 2,0M 385M 1% /run
/dev/sda2 916G 207G 663G 24% /
tmpfs 1,9G 61M 1,9G 4% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 1,9G 0 1,9G 0% /sys/fs/cgroup
/dev/loop0 3,8M 3,8M 0 100% /snap/gnome-system-monitor/51
/dev/loop2 88M 88M 0 100% /snap/core/5742
/dev/loop1 15M 15M 0 100% /snap/gnome-logs/45
/dev/loop4 141M 141M 0 100% /snap/gnome-3-26-1604/70
/dev/loop6 13M 13M 0 100% /snap/gnome-characters/117
/dev/loop7 13M 13M 0 100% /snap/gnome-characters/124
/dev/loop9 140M 140M 0 100% /snap/gnome-3-26-1604/64
/dev/loop10 35M 35M 0 100% /snap/gtk-common-themes/319
/dev/loop8 2,3M 2,3M 0 100% /snap/gnome-calculator/238
/dev/loop5 128K 128K 0 100% /snap/tree/15
/dev/loop11 3,8M 3,8M 0 100% /snap/gnome-system-monitor/54
/dev/loop12 13M 13M 0 100% /snap/gnome-characters/139
/dev/loop13 88M 88M 0 100% /snap/core/5662
/dev/loop3 2,3M 2,3M 0 100% /snap/gnome-calculator/260
/dev/loop14 43M 43M 0 100% /snap/gtk-common-themes/701
/dev/loop15 15M 15M 0 100% /snap/gnome-logs/43
/dev/loop16 15M 15M 0 100% /snap/gnome-logs/40
/dev/loop17 141M 141M 0 100% /snap/gnome-3-26-1604/74
/dev/loop18 88M 88M 0 100% /snap/core/5548
/dev/loop19 2,3M 2,3M 0 100% /snap/gnome-calculator/222
/dev/loop20 3,8M 3,8M 0 100% /snap/gnome-system-monitor/57
/dev/sda1 511M 6,1M 505M 2% /boot/efi
tmpfs 387M 40K 387M 1% /run/user/1000
/dev/sdb1 1,9T 108G 1,8T 6% /media/manolis/Maxtor
tmpfs 387M 16K 387M 1% /run/user/120
manolis#manolis-300-0xx:~$ sudo apt install udo
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
udo
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
Need to get 205 kB of archives.
After this operation, 598 kB of additional disk space will be used.
Get:1 http://it.archive.ubuntu.com/ubuntu bionic/universe amd64 udo amd64 6.4.1-4 [205 kB]
Fetched 205 kB in 0s (1.520 kB/s)
Selecting previously unselected package udo.
(Reading database ... 168775 files and directories currently installed.)
Preparing to unpack .../archives/udo_6.4.1-4_amd64.deb ...
Unpacking udo (6.4.1-4) ...
Setting up udo (6.4.1-4) ...
Setting up grub-efi-amd64-signed (1.93.8+2.02-2ubuntu8.7) ...
Installing for x86_64-efi platform.
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
dpkg: dependency problems prevent processing triggers for shim-signed:
shim-signed depends on grub-efi-amd64-signed; however:
Package grub-efi-amd64-signed is not configured yet.
dpkg: error processing package shim-signed (--configure):
dependency problems - leaving triggers unprocessed
Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Why I have all of these "/dev/loop" ???
How can I clean and increase the space: "Could not prepare Boot variable: No space left on device"
Is correct to do, or dangerous:
rm -r /dev/loop*
All the best!
The following worked well for me on Ubuntu 18.04LTS
on the following commands : use sudo or run as root
sudo apt-get purge grub\*
sudo apt-get install grub-efi
sudo apt-get autoremove
sudo update-grub
-or-
sudo su
enter your password then run
apt-get purge grub\*
apt-get install grub-efi
apt-get autoremove
update-grub
In my case, Ubuntu 18.04 installed on bare metal servers, I had to execute this command:
apt-get install -y grub-pc 'grub-efi*-'
which yielded this change:
The following additional packages will be installed:
grub-gfxpayload-lists grub-pc-bin
Suggested packages:
desktop-base
The following packages will be REMOVED:
grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed shim-signed
The following NEW packages will be installed:
grub-gfxpayload-lists grub-pc grub-pc-bin
After this, the error is gone.
These 2 lines of command worked for me.
apt install grub-efi-amd64-bin
apt upgrade
I don't have enough rep to add a comment, but the answer from "AAA SSS" worked for me. I found the same answer in the AskUbuntu forum. I was directed there by pasting this into a Google search.
Package grub-efi-amd64-signed is not configured yet.
My situation arose from both a fresh install to 18.04 and an upgrade from 16.04 to 18.04, the same errors printed by apt and booting failed. "dpkg -l" reported these errors.
iF grub-efi-amd64-signed (1.93.13+2.02-2ubuntu8.12)
iU shim-signed (1.37~18.04.3+15+1533136590.3beb971-0ubuntu1)
The above attempts were not working for me.
I was getting similar errors, not sure what happened on me, but my /etc/default/grub file had an extra line added during a recent update:
"/etc/default/grub" 34L, 1279C
was at the bottom of that file, I commented it out and things worked for me again!
Run this as one command and answer y (yes) when prompted:
sudo apt-get purge grub\*
sudo apt-get install grub-efi
sudo apt-get autoremove
sudo update-grub
This just a quicker way base off the answer given by AAA SSS. This worked for me.
I had problem which says
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess ret
urned error exit status 127
I found that It's beacuse of bugs which can solve installing mokutil
sudo apt-get install -y mokutil
It looks like you've installed OS with secure boot disabled, but now it is enabled.
Make sure you still have the secure boot option disabled in BIOS.
Related
So I have docker installed on Linux Mint 18.3 (dual-boot with Windows 7) and I can run and work with the containers without an issue. However, ever since I installed it, I keep getting errors while I try to upgrade my packages.
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up docker.io (1.13.1-0ubuntu1~16.04.2) ...
addgroup: The group `docker' already exists and is not a system group. Exiting.
dpkg: error processing package docker.io (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
docker.io
E: Sub-process /usr/bin/dpkg returned an error code (1)
I tried to install docker.io again and see what happens:
$ sudo apt-get install docker.io
Reading package lists... Done
Building dependency tree
Reading state information... Done
docker.io is already the newest version (1.13.1-0ubuntu1~16.04.2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up docker.io (1.13.1-0ubuntu1~16.04.2) ...
addgroup: The group `docker' already exists and is not a system group. Exiting.
dpkg: error processing package docker.io (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
docker.io
E: Sub-process /usr/bin/dpkg returned an error code (1)
Running $ groups returns this:
$ groups
kosara adm dialout cdrom sudo dip plugdev lpadmin sambashare docker
I did some digging and ran $ sudo dpkg --configure -a:
$ sudo dpkg --configure -a
Setting up docker.io (1.13.1-0ubuntu1~16.04.2) ...
addgroup: The group `docker' already exists and is not a system group. Exiting.
dpkg: error processing package docker.io (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
docker.io
But it seems that a package that isn't fully installed is to blame, so I tried to fix it:
$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up docker.io (1.13.1-0ubuntu1~16.04.2) ...
addgroup: The group `docker' already exists and is not a system group. Exiting.
dpkg: error processing package docker.io (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
docker.io
E: Sub-process /usr/bin/dpkg returned an error code (1)
I removed docker and did a clean install, to no avail. I'm not really sure what to try next and I couldn't find a solution that works for me so far. Any help would be welcome!
I've already seen these answers, so please don't link em in solutions:
Installing MongoDB on Ubuntu 16.04
https://unix.stackexchange.com/questions/220467/mongodb-unmet-dependencies/220483
can't install mongodb on ubuntu 16.10
https://www.digitalocean.com/community/tutorials/how-to-install-mongodb-on-ubuntu-16-04
I have already added the required repository for ubuntu 16.04
When I run sudo apt-get install -y mongodb-org, it throws the error:
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
linux-headers-4.4.0-93-generic : Depends: linux-headers-4.4.0-93 but it is not going to be installed
mongodb-org : Depends: mongodb-org-shell but it is not going to be installed
Depends: mongodb-org-server but it is not going to be installed
Depends: mongodb-org-mongos but it is not going to be installed
Depends: mongodb-org-tools but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
And on running apt-get -f install, I get the following error:
Unpacking linux-headers-4.4.0-93 (4.4.0-93.116) ...
dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.4.0-93_4.4.0-93.116_all.deb (--unpack):
unable to create '/usr/src/linux-headers-4.4.0-93/arch/xtensa/include/asm/pgtable.h.dpkg-new' (while processing './usr/src/linux-headers-4.4.0-93/arch/xtensa/include/asm/pgtable.h'): No space left on device
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/linux-headers-4.4.0-93_4.4.0-93.116_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
And the same thing continues when I try to install it again.
Can anyone explain what's this error and how to install it ?
Update:
Running df -h gives:
Filesystem Size Used Avail Use% Mounted on
udev 487M 0 487M 0% /dev
tmpfs 100M 12M 88M 12% /run
/dev/xvda1 7.8G 5.3G 2.1G 72% /
tmpfs 496M 0 496M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 496M 0 496M 0% /sys/fs/cgroup
tmpfs 100M 0 100M 0% /run/user/1000
Running df -i gives:
Filesystem Inodes IUsed IFree IUse% Mounted on
udev 124466 360 124106 1% /dev
tmpfs 126788 480 126308 1% /run
/dev/xvda1 524288 520744 3544 100% /
tmpfs 126788 1 126787 1% /dev/shm
tmpfs 126788 6 126782 1% /run/lock
tmpfs 126788 16 126772 1% /sys/fs/cgroup
tmpfs 126794 4 126790 1% /run/user/1000
Worked after installing libcurl3
sudo apt install libcurl3
I also had the similar issue and it got resolved for me by doing this
Go to this directory /etc/apt/sources.list.d/ and check if there are anyother mongodb-org-*.list files as it would cause conflicts.
then try to install it again, if again issue arises, then run
sudo apt purge mongod*
sudo apt purge mongodb*
sudo apt purge mongodb-org*
to remove any inconsistency and then go to https://docs.mongodb.com/manual/tutorial/install-mongodb-on-ubuntu/ and follow the procedure.
If you're some kind of Ubuntu Derivatives like Linux Mint, Ubuntu GNOME etc, make sure which Ubuntu version is running on your ubuntu derivative version on wiki before pasting the required commands.
As in my case I'm using Linux Mint 17 -> Ubuntu 14.04 and I was installing with Ubuntu 16.04 that made the conflict
Hope this would resolve the issue.
Have you done the update?
sudo apt-get update && sudo apt-get upgrade
If the update does not help, try checking for broken dependencies:
sudo apt-get check
The check command is a diagnostic tool. It used to update package cache and checks for broken dependencies.
I would also try two more things.
First,
sudo dpkg --configure -a
sudo apt-get -f install
and if that does not help, try to unblock the dpkg
sudo rm -rf /var/lib/apt/lists/partial/*
sudo apt-get -f install
I hope it helps.
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 0C49F3730359A14518585931BC711F9BA15703C6
echo "deb [ arch=amd64,arm64 ] http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.4 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-3.4.list
sudo apt-get update
sudo apt-get install -y mongodb-org
sudo service mongod start
mongo
Run the below command:
sudo apt-get -f install
And then try running sudo apt-get install -y mongodb-org
Download the MongoDB Community Server (.dbz) version
Extract it and move it to home directory
Edit the ~/.profile by running:
gedit ~/.profile
Then add this:
echo export PATH=mongodb-linux-x86_64-ubuntu1804-4.0.4/bin:$PATH
Save then update the system variables by running:
source ~/.profile
After that, start server by running:
mongod
I have tried many answers, but at last, I found that make system version is not matched to the mongo repo required version. At MongoDB official website, there is an option to let you choose the correct repo link.
So, check your system version firstly with:
lsb_release -dc
Then if your system version is 18.04, try
echo "deb [ arch=amd64 ] https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.0 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-4.0.list
If your system version is 16.04, try
echo "deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/4.0 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-4.0.list
I was facing the same issue. I tried to install using brew but it didin't work for me. I followed all the steps mentioned on the official website, but it didn't work.
I created a specific sources.list file for MongoDB and added to the sources.list directory which is always used by apt. Make sure you use the same format as sources.list
echo "deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.4 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-4.4.list
Next, we need to update to make apt use updated sources.list. So I used update command.
sudo apt-get update
Finally, I executed the installation command and it worked.
Have you checked inodes on the server? df -h may still show space left but you could be out of inodes. Please try running df -i and see if you have any inodes left on the server.
For installing mongodb 4.0 in ubuntu 16.04
echo "deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/4.0 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-4.0.list
sudo apt install libcurl3
sudo apt-get update
sudo service mongod start
mongo
Remove those files by using this command.
sudo dpkg -i --force-overwrite /var/cache/apt/archives/mongodb-org-mongos_4.4.4_amd64.deb; sudo dpkg -i --force-overwrite /var/cache/apt/archives/mongodb-org-server_4.4.4_amd64.deb; sudo dpkg -i --force-overwrite /var/cache/apt/archives/mongodb-org-tools;
and then run
sudo apt-get install -y mongodb-org;
sudo systemctl start mongod;
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
libao-common
0 upgraded, 1 newly installed, 0 to remove and 52 not upgraded.
4 not fully installed or removed.
Need to get 0 B/11.3 kB of archives.
After this operation, 49.2 kB of additional disk space will be used.
dpkg: regarding .../libao-common_1.1.0-2_armhf.deb containing libao-common:
libao-common conflicts with libao2
libao2 (version 0.8.4-1) is present and unpacked but not configured.
dpkg: error processing /var/cache/apt/archives/libao-common_1.1.0-2_armhf.deb (--unpack):
conflicting packages - not installing libao-common
Errors were encountered while processing:
/var/cache/apt/archives/libao-common_1.1.0-2_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Why is conflicting packages not installing libao-common?
It’s on a Raspberry PI with Raspbian.
apt-get -f install doesn't work
root#raspberrypi:~# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
libao-common
The following NEW packages will be installed:
libao-common
0 upgraded, 1 newly installed, 0 to remove and 52 not upgraded.
4 not fully installed or removed.
Need to get 11.3 kB of archives.
After this operation, 49.2 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://mirrordirector.raspbian.org/raspbian/ wheezy/main libao-common armhf 1.1.0-2 [11.3 kB]
Fetched 11.3 kB in 2s (4,117 B/s)
dpkg: regarding .../libao-common_1.1.0-2_armhf.deb containing libao-common:
libao-common conflicts with libao2
libao2 (version 0.8.4-1) is present and unpacked but not configured.
dpkg: error processing /var/cache/apt/archives/libao-common_1.1.0-2_armhf.deb (--unpack):
conflicting packages - not installing libao-common
Errors were encountered while processing:
/var/cache/apt/archives/libao-common_1.1.0-2_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
notice that message:
4 not fully installed or removed.
maybe you install other package failed. then the apt tool try to install them again.
so, uninstall these error package first.
sudo apt-get --force-yes remove #your-package-name#
you need to remove the 4 not fully installed or removed package first.
then
sudo apt autoremove
now, try to install the new package again.
I'm trying to install things in Linux (Crunchbang Linux - a derivation of Debian), and I'm getting errors which point towards mongodb-20gen.
When I try to remove it using :-
cometbill#Linuxn00b:~$ sudo apt-get remove mongodb-10gen
I get ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
mongodb-10gen
0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 221 MB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 81657 files and directories currently installed.)
Removing mongodb-10gen ...
arg: remove
invoke-rc.d: unknown initscript, /etc/init.d/mongodb not found.
dpkg: error processing mongodb-10gen (--remove):
subprocess installed pre-removal script returned error exit status 100
invoke-rc.d: unknown initscript, /etc/init.d/mongodb not found.
dpkg: error while cleaning up:
subprocess installed post-installation script returned error exit status 100
Errors were encountered while processing:
mongodb-10gen
E: Sub-process /usr/bin/dpkg returned an error code (1)
I read something on here for similar errors with MongoDB, and it suggested removing mongo-clients, so, I tried:-
cometbill#Linuxn00b:~$ sudo apt-get remove mongodb-clients
and get:-
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'mongodb-clients' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up mongodb-10gen (2.4.6) ...
invoke-rc.d: unknown initscript, /etc/init.d/mongodb not found.
dpkg: error processing mongodb-10gen (--configure):
subprocess installed post-installation script returned error exit status 100
Errors were encountered while processing:
mongodb-10gen
E: Sub-process /usr/bin/dpkg returned an error code (1)
This is a difficult state to get out of. You should be able to complete the removal if you create a fake init script:
sudo touch /etc/init.d/mongodb
sudo chmod 755 /etc/init.d/mongodb
This is due to some corruption within the package manager dpkg itself, this thread from Ask Ubuntu: https://askubuntu.com/questions/195950/package-system-broken-e-sub-process-usr-bin-dpkg-returned-an-error-code-1 lists some solutions, more specifically the editing of the status file has been noted as one that always works.
For mongodb v3.4
sudo touch /etc/init.d/mongod
sudo chmod 755 /etc/init.d/mongod
You can force installation of package:
sudo dpkg -i --force-all /var/cache/apt/archives/mongodb-org-tools_3.6.5_amd64.deb
Then resume with:
sudo apt-get install -f
sudo nano /var/lib/dpkg/statoverride
Then remove first 2 line entries and try again
**mongodb mongodb 755 /var/log/mongodb
mongodb mongodb 755 /var/lib/mongodb**
root crontab 2755 /usr/bin/crontab
root mlocate 2755 /usr/bin/mlocate
root ssl-cert 710 /etc/ssl/private
root messagebus 4754 /usr/lib/dbus-1.0/dbus-daemon-launch-helper
According to your question, this process will be break at line.
invoke-rc.d: unknown initscript, /etc/init.d/mongodb not found.
You must be create fake file,
sudo touch /etc/init.d/mongodb
sudo chmod 755 /etc/init.d/mongodb
and process will complete.
I wonder who had such a experience.
We are using diskless linux servers. Before we use ramdisk, recently we are trying to make a diskless server with ramfs, and we successfully created the rootfs image and booted the server.
Then the issue here is that we can not install anything, because yum complains about no disk space. it is quite true that there is no disk thus no space, but for a ramfs, can we update the linux configuration to by pass this issue?
df -kh /
Filesystem Size Used Avail Use% Mounted on
- 0 0 0 - /
yum install w3m -y
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding Packages from Extra Packages for Enterprise Linux 5 - x86_64
Finished
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package w3m.x86_64 0:0.5.1-18.el5 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
====================================================================================================================
Package Arch Version Repository Size
====================================================================================================================
Installing:
w3m x86_64 0.5.1-18.el5 os 1.1 M
Transaction Summary
====================================================================================================================
Install 1 Package(s)
Upgrade 0 Package(s)
Total download size: 1.1 M
Downloading Packages:
Error Downloading Packages:
w3m-0.5.1-18.el5.x86_64: Insufficient space in download directory /var/cache/yum/os/packages
* free 0
* needed 1.1 M
update:
I checked the yum code, it is using statvfs system call to check the diskspace. So other than creating a "real disk", I have no idea how can I bypass this issue.
I have a similar use case. I found this article: but for some reason yum continued to check for free disk space before downloading even with
diskspacecheck=0
I eventually decided to workaround:
yum clean all
mount -t tmpfs -o size=5G tmpfs /var/cache/yum