similar to: Kernel panic: I have no root and I want to scream

Hi, Is anyone using GlusterFS on Ubuntu in production? Specifically, I'm looking at using the NFS portion of it over a bonded interface. I believe I'll get better speed than user the gluster client across a single interface. Setup: 3 servers running KVM (about 24 VM's) 2 NAS boxes running Ubuntu (13.04 and 13.10) Since Gluster NFS does server side replication, I'll put

Hi, I wonder if someone could give me a little help bringing the sieve-extdata plugin up to date to be usable with latest Dovecot/pigeonhole Trying to use both together at present I get an error: ? managesieve: Fatal: Couldn't load required plugin /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: dlopen() failed: /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: undefined symbol:

hi ya syslinuxerz - i've been slowly working on a making a custom bootable standalone usb-stick with X11 and kde - it's basically builds itself off of a slackware-10.1 server - create a custom initrd.gz ( /dev/ram0 ) http://linux-boot.net/Bootable/InitRD/ - create a custom rootfs.gz ( /dev/loop0 ) http://linux-boot.net/Bootable/RootFS/ - create X11 and kde loopfiles

Sorry, hit send instead of attach again. Rest of patches included. -- Anthony Liguori Samba, Linux/Windows Interoperability Linux Technology Center (LTC) - IBM Austin E-mail: aliguori@us.ibm.com Phone: (512) 838-1208 Tie Line: 678-1208

Hi, In case of tl;dr: I fixed a bug in TLS support for LMTP which caused chained certificates not to work, and another one which caused certificate read errors to be ignored; the patches are attached to this email. While testing LMTP with TLS and certificate verification by Postfix I discovered that certificate chains are not exchanged properly when using LMTP, even though everything works fine

Hi I am trying to have a built in initramfs along with the traditional initrd. So I mount the initrd from the initramfs, but am facing problems in trying to run the 'linuxrc'. Following are the issues: 1. I mount the initrd from the initramfs and exceve 'linuxrc'. It starts executing linuxrc, but gives the following errors and panics: Red hat nash version 3.4.42 starting

I am using the following simple menu and have noticed that items at the bottom are dropping off. I seem to be limited to 12 items. Is there a limit to how many items can be on the simple menu? default pxelinux.cfg/menu.c32 prompt 0 MENU TITLE UWSP PXE Boot Menu # TIMEOUT 200 LABEL bartpe MENU LABEL Build 12 KERNEL /STARTROM.0 APPEND keeppxe LABEL 11dnet MENU LABEL Build 11DNET beta

Hello, I am using with success SYSLINUX-1.48 to boot a CD-Rom in order to realize an automatic installation of Linux. Actually all messages during the boot step are displayed on VGA screen. In the operational version, we have only a VT on COM1. I have tested to modified my syslinux.cfg like the following listing but boot messages are always displayed on VGA screen ! Can you help me, please ? (I

Hi, I am trying to figure out a poor mans install ... I want to be able to boot CD iso thats on my hard disc .. There is an option to install via hard drive .. but I keep getting VFAT16 files system errors .. I know where copied iso image is ... I can boot kernel but linuxrc will not start LiveCD ... Maybe I could rewrite linuxrc to allow this but as it works from ram I am finding hard to

I converted my lvm root initrd to an initramfs by putting glibc, lvm, pivot_root, my linuxrc, etc. in my initramfs source file. I use ash compiled against klibc to run my linuxrc Unfortunately - pivot_root . initrd - complains - pivot_root: Invalid argument I suspect this may be because you can't pivot_root using a cpio initramfs root? If so, what should I do instead? Should I

I?ve got a 512M machine and a 330M ( uncompressed ) initrd image. How can I mount the ramdisk? Normal booting seems to want to copy the entire initrd image into a Ramdisk, thus requiring 2X the memory. So what happens is the kernel boots correctly and I get, RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 330000 blocks [ 1 disk ] into ram disk And then I never see the light of day after

yup runned it. probably something wrong with my initrd filesystem. can you send me a directory listing of your initrd? and probably a sample linuxrc. if worse comes to worse, i'll probably load my usb and scsi modules in the initrd. i'm probably doing it all wrong. i'm trying to imitate the slackware10usb way of booting up. every driver built in the kernel, patch on the mounting root

Hello, Im a Gentoo kernel maintainer thats trying to fix some bugs on are upcoming 1.4 livecd release that uses IsoLinux. Our isolinux.cfg is pretty standard : ######################################### default gentoo append initrd=initrd acpi=off root=/dev/ram0 init=/linuxrc timeout 300 prompt 1 display boot.msg F1 boot.msg F2 help.msg label livecd kernel gentoo append

Hi, I can get into basic shell (from linuxrc) but now I want to boot main system ... ie chroot into untar system & run from there ... but when I run /sbin/init 3 I get kernel panic wondered if /dev was set up .. if not how do I get it working ... sorry to so vague but its diffcult to describe what I want to do...... so to sum up I want to go from initrd (linuxrc) to log into console of

hi, i am wondering about how submission of append parameters can be done. i have the following isolinux.cfg: --------------------------------------------------------------------- DEFAULT linux PROMPT 1 TIMEOUT 100 LABEL linux KERNEL vmlinuz APPEND initrd=initrd.gz nomce quiet ---------------------------------------------------------------------- what i want to do is to tell at

> /diskless/pxelinux.cfg/default > --- > DEFAULT /gentoo-x86_64/boot/kernel-3.14.14-gentoo > APPEND ip=dhcp ro rootfstype=nfs root=/dev/nfs > nfsroot=10.0.0.11:/diskless/gentoo-x86_64 > init=/linuxrc That pxelinux.cfg/default seems "tolerable" for older versions, but not for Syslinux 5+. Is this an inadequate copy of the actual content? Or is it really a

I have a Debian system from a Knoppix distribution. I started out with ext2 but decided to change to ext3. tune2fs -j OK. However the system boots with a warning ....ext3 mounted as ext2. proc/mounts confirms this and no journal is running. So I have to make an initrd. Did so using instructions in the Debian Reference and this did not change anything. Any attempt to use the img produced was a

I have tried to use isolinux 2.05, and I am running into a problem where it will not boot. I have previously used version 1.66, and the older version works just fine. Changing nothing except dropping the new version in does not work. Below is all of the relevant info, I believe. This occurs on multiple machines with different BIOS. I am currently in process of doing a binary search to find the

I'm replacing the master node in a cluster and having issues PXE booting the diskless nodes. The current master works fine, but the new node to replace the current node which has the same setup is having the issues. The hardware is: Dell r920 (new master node, UEFI) Dell r620's (diskless, BIOS) Dell 1950's (diskless, BIOS) When trying to boot, the 1950 node displays (though both

I have tried to get this working SO many times, everywhere I look on the web tells me i have this correct. I have the following stanza in my /tftboot/lts/pxelinux.cfg/default label Ghost kernel memdisk append initrd=netboot.img For some reason, it doesn't work - I get the error messages Missing parameter in config file Could not find kernel image: linux boot: The netboot.img is in the