I need to get LILO to boot a ramdisk in which the root file system is on /dev/ramdisk. I have tried many iterations of lilo.conf files. The following is one that I would think would work because it worked under 2.4 kernels:
default=linux
boot=/dev/hda
install=/mnt/flash/boot/boot.b
[code]...
I am using fc11(32-bit) and i want to boot the system using initial ramdisk by setting the root to /dev/ram in the /etc/grub.conf.c
View 2 Replies View RelatedI work in a very restrictive environment and I want to use linux on my work laptop (currently running Windows XP prof). I am planning to install linux in a dual boot mode but I dont want to install grub/lilo or any other boot loader. i cannot even modify Windows bootloader to boot into linux partition.
Is there a way I can boot into linux partition without installing new boot loader or modifying the current windows boot loader? Any boot CD etc available that can boot into linux partition from my laptops HDD?
I attempted to install slackware 13 on my laptop and was moderately successful. However in the process of attempting to configure it I appear to have messed something up. After reading about the problems I'm having I decided it would probably be easier to remove the current installation and start over.
I am now trying to install fedora from the dvd, but for some reason the computer will not boot the dvd. I have set the bios to boot from the drive first, and have tried burning the dvd twice, but every time the dvd spins up and shortly thereafter the computer loads lilo. Have I simply burned the dvd wrong twice? I used disk manager on mac os x and the disc reads just fine on the mac that burned it, but still no luck booting.
I installed Ubuntu 10.04 on a spare partition, but didn't want to install Grub since I'm sure Ubuntu isn't going to be around for more than a little test drive. The problem I have is that lilo doesn't like the initrd.img file, complaining that it's too large. I'm assuming this file should be in the initrd line for the lilo entry. If someone is booting Ubuntu 10.04 with lilo it would be nice to see the lilo entry or any tips.
View 4 Replies View RelatedI'm running Ubuntu 10.10 with Lilo as my boot loader instead of Grub. I want to boot, temporarily, to a command line prompt instead of X-windows. How do I do this? Is there a combination of keys to press when the Lilo screen appears?
View 2 Replies View RelatedIm planning on installing a beta of my favorite distro to /dev/hdb from a mounted iso on an /dev/hda partition.Im not exactly a newbie, but i cant say i have ever done this before. Anyone aware of any issues i might encounter? Is lilo ok booting from one drive to another? Is it ok to just install lilo on the mbr of /dev/hda to boot a distro on /dev/hdb?
View 4 Replies View RelatedI am installing slackware 13 on a machine that already has slackware 64- current. I'm doing this to try LFS which needs a 32 bit host (I know about CFLS, but I'm trying to keep it simple). My current installation is on sda with / being on sda1. My new 32 bit installation is on sdb with / being on sdb2.
I didn't install LILO as I figured it would be easy enough to just edit the current lilo.conf and run lilo after rebooting from the installation and then rebooting again into the new 32 bit install. What keeps happening is that the system boots seemingly fine, but after some wierdness I realized that it is booting a kernel from the 64 bit install on sda1. I'm assuming this is a simple screw up in my lilo.conf but I'm not sure exactly how to fix it.
lilo.conf:
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0 quiet"
[Code]...
I have a fresh install of COS5.6 installed a test laptop. I have following instructions to set up the PXE server based on the following: http:[url]......The base PXE installation seems to work fine (The menu labeled CentOS 5.6 works fine ). The whole purpose of this was to be able to boot iso's like Hirens and Imaging software ISO's.The issue is that whenever i try to pick an iso from the list it just says "Could not find ramdisk image:" [path to iso][path to iso] being either of the two iso i had set up to test this.
I would like to think that i made a typo but i can find one. The files i used are from the source of syslinux v4.0.4.The following information should be pertinent
Contents of /tftpboot/pxelinux.0/default[code].....
I have a limited experice with linux in an enterprise environment and looking for any direction as to what to do about this.
I'm fairly new to Linux so I'm going to need a step-by-step guide to get me out of this rut. The install of Linux was fine but when I booted up I got this error. VFS: Cannot open root device "302" or unknown-block (3,2) append a correct "root=" boot option;here are the available partitions;
0800 78150744 sda driver:sd
0801 47428608 sda1 <-- this is my Windows partition
0802 30719552 sda2 <-- this is my Linux partition
0b00 1048575 sr0 driver:sr
0b01 1048575 sr1 driver:sr
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (3,2) I guessed from reading this error Lilo isn't pointing to the right partition to boot from? How will I fix this? I read another thread about boot problems on these forums and a guy said to do this:
#mkdir /slacktemp
#mount /dev/device /slacktemp
#chroot /slacktemp
#cd /slacktemp/etc <-- for me it told me that doesn't exist
#vi lilo.conf <-- couldn't do nothing and was frozen
#lilo -v -t -b /dev/device
#lilo -v -b /dev/device
The above solution did not work for me. Can anyone shed a light on a Linux rookie?
I'm fairly new to linux, and a few days ago, as I was updating my system, I got the "EBDA is big ; kernel setup stack overlaps LILO second stage" error after reboot. I use a 3- boot, ( Win XP / Debian / Debian) and Windows XP works fine, but I can't launch any of the Debian. I googled the message, and I found this link :
[URL]
The only problem problem is that when I try to chroot, I got another message, "chroot: failed to run command `/bin/bash': No such file or directory" I googled this message too, but found no relevant answers. I am now using a knoppix usb drive to try to repair the lilo, but I ran out of ideas ...
how could i mount the whole system into the ramdisk?I follow the article "http://www.linuxquestions.org/questions/red-hat-31/building-a-diskless-redhat-enterprise-linux-cluster-765393/",and it works.when i use the "df -h" on the diskless client .I find many system driectory is mountted from image_server.when i stop the connection between img_server and diskless client,the diskless client stop working. my question is how can i mount the whole system into ramdisk.
View 2 Replies View RelatedI'm using some milters on a Sendmail box that recommends using a RAMdisk [tmpfs] to store temporary files, the performance benefits of which are quite noticeable. However, the problem is if a huge number of messages are all delivered at once this partition can be pushed off the physical memory and into swap. When this happens the performance tanks to about 1/20th to 1/30th of normal.Is there anything I can do to keep a tempfs from being swapped to disk?
View 3 Replies View RelatedDoes anyone know is there any size limitation when doing RAMDISK under SUSE Linux?
View 9 Replies View RelatedHave such a question: how to set ramdisk size? Ramdisk: How do you install and set up Ramdisk under Linux (CentOS, RHEL, Fedora)? | Technology: Learn and Share
Here is some article, but somehow GRUB setting takes no effect, size is still limited to 100MB. I need to get ramdisk with size about 700-1500 MB.
Wine is one of the coolest things I've ever seen, but unfortunately it's still not enough to suit my needs as version 1.38 can't install any of the .NET libraries.
I'm trying to boot windows 7 on virtual box, but it seems to demand quite a bit of memory. The "recommended" amount is 512MB, and upon checking my kernel only has 488MB total ram with not much room to spare:
Code:
billy@billy-desktop:~$ free -m
total used free shared buffers cached
Mem: 488 462 25 0 53 193
-/+ buffers/cache: 216 271
Swap: 1939 17 1921
I've tried giving the virtual machine memory sizes in the area of 192-256MB, but that's way too much and the system locks up and aborts from it. Memory sizes in the area of 128MB is just too small and it throws an error that there just isn't enough ram to boot. So the only thing I can do to make this work is to increase the size of the ramdisk for my host OS so I can give more to the virtual machine (not to mention things like flash animations are horribly slow and I'd like to see them get more fluid).
I see that I have 16 ramdisks available to me:
Code:
billy@billy-desktop:~$ ls -l /dev/ram*
brw-rw---- 1 root disk 1, 0 2010-02-17 09:54 /dev/ram0
brw-rw---- 1 root disk 1, 1 2010-02-17 09:54 /dev/ram1
brw-rw---- 1 root disk 1, 10 2010-02-17 09:54 /dev/ram10
[Code]....
I looked at some guides here and there, but apparently my setup isn't quite the same. I don't have a menu.lst file in boot/grub, and I don't have a grub.conf file anywhere. So I don't know what file I'm supposed to edit for this.
Trying to mount a ramdisk on demand when I need one, however gksudo is griping that the command is wrong. So, what's wrong with this command?
gksudo mount -t tmpfs -o size=1024m tmpfs /mnt/ramdisk
I am trying to config the RAM disk on CentOS 5.5
/etc/grub.conf
title CentOS (2.6.18-194.el5)
root (hd0,0)
[code].....
I am trying to boot a ramdisk and am getting the following error:16384 ram0 (driver?)
16384 ram181 (driver?) No filesystem could mount root, tried:ext2 iso9660. Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (1,0)
This is RHEL5 so input the ramdisk_blocksize into isolinux.cfg:
DEFAULT linux
LABEL linux
KERNEL vmlinuz
APPEND initrd=initrd.img root=/dev/ram0 ramdisk_blocksize=1024 ramdisk=2969600 rw init=/etc/rc.d/rc.sysinit
[Code]...
I created a ram disk with this command: sudo mount -t tmpfs -o size=2048M,nr_inodes=500k,mode=777 tmpfs /var/cache/apt-build/build When I run apt-build, I got an error message that the disk is full (unable to copy file or something). But no disk was full when I checked with 'df'.
we know the maximum of files created from the nr_inodes number? Or is there any other option that determines the max number of files created?
How do I set up a 256mb ramdisk on opensuse 11.3 x86_64 ? - The /boot/grub/menu.lst content reads as:
# Modified by YaST2. Last modification on Mon Aug 30 11:33:28 EST 2010
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
gfxmenu (hd0,1)/boot/message
[Code]....
I updated my netbook to the last incarnation of slackware-current yesterday.
My problem is now, that it is no more able to start the ash shell of the initial ramdisk i am using. The ramdisk was created with the latest version of the mkinitrd script.
The error message is:
Code:
And the error happens when the ash from the initial ramdisk is intended to be started. Simply copying the /lib/libc.so.6 stuff (symlink to the real so and the real so) enables to ash to be started but later cryptsetup fails to load.
The initial ramdisk from mid-January i used before did not have such a problem. What i also see is, that the failing ramdisk has a size of only 16k blocks. The one from mid-January was bigger.
I just performed my very first linux install. I used the Debian 6.0.1a iso. I made it all the way through the installation with no problems whatsoever. I was able to select the version from the grub screen, still everything seemed to be going fine...then it froze. I attached an image of the screen where the system froze:
Its basically the loading screen, times 4! At the top left in case its too hard to read, it says: Loading Linux 2.6.32-5-686, then...Loading initial ramdisk... This sounds all fine and dandy to me but it freezes here. I've tried searching the forums and google for an answer and have come up empty...I'm sure someone has had this problem but it seems to be a tough thing to search for. Would appreciate all the help I can get! Oh and btw, here are the system specs:
circa 2001ish Dell Dimension 4300
P4 1.4ghz
256 ram
onboard video etc...
Howto create squeeze self compiled kernel with initial ramdisk?I need some more details, I never done before.
View 14 Replies View RelatedOn Debian Etch I used to understand how to change boot kernel parameters with Grub. You could just edit menu.lst.
With the newer Grub in Squeeze I am without a clue! I want to set up a ramdisk, say 128 Megs in size, and add that to my boot parameters so that it is created every time the machine starts. Do I set something in /etc/default/grub ?
So after deciding to upgrade the existing fedora install on my laptop from 11 to 12, I decided to use the preupgrade method. After grappling with the boot space issue by clearing out an old kernel that was deemed safe to remove by the python script on the preconfig wiki page and then using tune2fs, I left the computer to do it's thing, periodically checking back on it. I come back to my computer, and after an apparent restart I see this message spat out at me:
Code:
ramdisk: incomplete write (3537 ! 5123)
write error
kernel panic - not syncing : VFS : unable to mount root fs on unknown block (0,0)
I need this laptop up and running for tomorrow and I would appreciate any help given. I have a Fedora 11 live CD running on the laptop and there seems to be an extra 210 filesystem present with the folders efi, grub, lost+found in there, as well as some config files, elf-memtest86+-400, what seems to be .img file amongst other things. If necessary, I can provide a screenshot.
I have updated using zypper from 11.1 to 11.2. Does this process update the boot/menu.lst file with an entry for the new kernel? Didn't for me.
Any rate, that's not really the problem. I have created a new entry in menu.lst to load the new kernel but I don't have a ramdisk image - all I have is a broken link initrd -> initrd-2.6.31.5-0.1-default
Where do I get the image from?
After some hours of googling, I've managed to increase the size of the default ramdisks (/dev/ram0-16) to 1 GiB each, I raided them together with mdadm to try it out, then created a filesyste, mounted it etc etc. No problems. The problem comes when I used gparted to move my windows partition over and in the unallocated space (1 GiB), I created an unformatted partition (/dev/sda2)Now when I try to create the raid array I get the following:
Code:
:~$ sudo mdadm --create /dev/md0 -l 1 -n 2 /dev/ram0 /dev/sda2
mdadm: Cannot open /dev/sda2: Device or resource busy
[code]....
I am trying to write to a Ramdisk because I suffer from terrible IO speeds on my VPS. It uses openVZ and I run a Centos 5 distro.
So i created my ramdisk with '/bin/mount -t tmpfs -o size=1G,nr_inodes=10k,mode=0775,noatime,nodiratime tmpfs /tmp'
but whenever I try and copy files to it, it just spams me with 'no space left on device even though there is!
Here is the output of df:
/dev/simfs 157286400 6511452 150774948 5% /
none 16441412 4 16441408 1% /dev
tmpfs 5242880 1296 5241584 1% /disk/test
tmpfs 5242880 1296 5241584 1% /disk/test
[Code]....
I am trying to use the Linux Ramdisk y machine and followed the instructions oninux/Ramdisk/ramdisk.html to create a 4GB ramdisk (total memory is 8GB, linux 2.6.9)The issue is that it is taking me almost exactly the same time to read a 1GB file from ramdisk as it is from disk. I was expecting it to be atleast twice as fast.Has anyone encountered this before?
View 1 Replies View Related