Slackware :: Software RAID 1 Versus LILO / Kernel-generic - ERROR: No /sbin/init Found On Rootdev
Jul 1, 2011
I'm currently trying to setup Slackware 13.7 on a server, using software RAID 1. I'm using the README_RAID.TXT document at the root of the Slackware disc as a reference. Anyway, here's what I have so far.
/dev/md1 -> /boot partition
/dev/md2 -> swap partition
/dev/md3 -> / partition
Code:
[root@raymonde:~] # fdisk -l /dev/sd{a,b}
Disk /dev/sda: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders, total 80293248 sectors
Units = sectors of 1 * 512 = 512 bytes
[code]....
I created an initrd image using mkinitrd -F, added an according stanza to /etc/lilo.conf and ran 'lilo' after that. Now I can boot on the vanilla huge kernel all right. But I can't seem to boot on the generic kernel. Whenever I try to do this, the boot process stops short on the following error message:
Code:
mount: mounting /dev/md3 on /mnt failed: Device or resource busy
ERROR: no /sbin/init found on rootdev
View 5 Replies
ADVERTISEMENT
Apr 21, 2010
I'm running Slacware current. Ran the updates this morning, including kernel 2.6.33.2. I always get nervous about that since something often goes wrong. Sure enough -
trying to boot I get No kewrnel modules found for Linux 2.6.33.2-smp mount: mounting /dev/sda9 on /mnt failed: No such device ERROR: No /sbin/init found on rootdev ( or not mounted ) and failure to proceed with booting. I got an original warning about the initial ram disk being too big to fit and switched to using generic kernel, and yes I did run lilo afterwards and did add the initrd.gz line. I run Ubuntu on the same laptop and have to boot into that and work as chroot in my Slackware partition to try and fix things.
View 14 Replies
View Related
Apr 19, 2011
Im am building a Linux distro. It will be very tiny and fast.
I only have a minimal linuxkernel (bzImage) who is 1,2 mb big. And then I have Busybox who is 174,6 kb big.
The commands in busybox is: cd, ls, mkdir, rmdir, wget, httpd, clear, rm, poweroff, halt, reboot, fdisk, mount, umount, free, and cp.
When I compiled the kernel i use initramfs/initrd function and point it to a folder where initrd/initramfs source is.
The kernel works OK with others initramfs/initrd files. But not with my own.
Quote:
Here is how the end of the kernelcomplie look like.
Quote:
Here is my init file who is the initrd/initramfs source.
Quote:
The initramfs folder contains "bin" (folder) and "init" a file. No more.
The problem is that the kernel cannot find/read init file.
View 4 Replies
View Related
Jan 4, 2011
I am trying to figure out how to load the generic kernel in Grub2.
I have run the /usr/hare/mkinitrd/mkinitrd_command_generator.sh and ran the output:
Code:
Why this will not load.
View 10 Replies
View Related
Nov 27, 2010
After normal use the computer was turned on and would not load (10.04) and the error message on the screen was :
Quote:
/sbin/init: error while loading shared libraries: libnih.so.1: cannot open shared object file: Input/output error
[ 26.369130] Kernel panic - not syncing: Attempted to kill init!
Anyways, I put the hard drive in an external unit, and I ran fsck. Many errors came up and they were all fixed. I was able to mount the drive on my other computer and back up files in the home directory.
If I try to select recovery mode and the same error appears.
What can I do in this case? Can I somehow get into a recovery-like mode off of the livecd to maybe fix the packages that might be "messed up"?
View 1 Replies
View Related
Jan 20, 2010
Ubuntu 9.10 will not boot! System froze this morning, I restarted and it is now failing to boot. Starts loading grub and I get this message:
mount: mounting /dev/disk/by-uuid/04aa3697-7bc0-45b5-b86a-77a1e6534bd5 on /root failed: invalid argument
mount: mounting /sys on /root/sys failed: no such file or directory
mount: mounting /dev on /root/sys failed: no such file or directory
[code]....
I booted with 9.04 LiveCD discovered the drive could not be mounted-ran fsck -ln and it told me the drive has no valid partition table. I have had intermittent problems mounting flash drives before this, so I'm kind of worried it might be a hardware issue.Also have files on that drive I would rather not lose, so reinstalling is hopefully a last resort.
View 9 Replies
View Related
Mar 14, 2010
I look after some small office where computers run ubuntu. Sometimes they phone me for help. For that reason, I decided to install ubuntu alongside with my slack.I seem to have problems with lilo configuration. Ubuntu is installed on software raid :
/boot = md0 (raid 1 of sda1+sdb1)
/ = md1 (raid 0 of sda2+sdb2)
That's lilo.conf:
Code:
append=" vt.default_uft8=0"
boot = /dev/sda
bitmap = /boot/slack.bmp
[code]....
Code:
Fatal: open /vmlinuz-2.6.31-9-rt: No such file or directory
I can mount md0 without problems and the file name seems to be correct.
View 3 Replies
View Related
Oct 16, 2010
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 ...
View 4 Replies
View Related
Mar 9, 2011
Basic Problem: I have been trying to install 13.1 (64-bit) and have not been able to get lilo to install.
Procedure:
1) partitioned drive /dev/sdc 1GB (Linux RAID) and 499GB (Linux Raid)
2) copied partitioning scheme to /dev/sdd
3) set up RAID-1 arrays md0 (sdc1-sdd1) and md1 (sdc2-sdd2)
4) write random data to partitions
5) set up LUKS on md1 (swluks)
6) set up LVM on swluks (80GB /, 375GB /home, 20GB swap)
7) ran setup, chose partitions, installed software
8) setup lilo (mbr, selected /)
9) TRIED to install lilo
[Code]..
View 4 Replies
View Related
Apr 4, 2011
I have the current disk setup :
disk1 :
Code:
sda:
(primary) sda1 ntfs
(primary) sda2 ext3 (mounted as / )[code]....
Before i set up the raid, but with this exact partitioning, the system booted perfectly. When i installed mdadm and created the raid1 mirroring on sda6 and sdb1, the init got screwed up, and all i get is a shell on initramfs, from where i can inspect that sda is binded on md, and cat /proc/mdstat tells me that i have an inactive sda[4].I can't mount the root partition (sda2), because it's busy (i suspect dmraid to lock it), which is, i guess, why init cannot be found.
I wonder if my error is to setup a raid array using a logical partition contained in an extended partition (but i hardly see why it would not work - but the sda bind and the sda[4] in mdstat seems to tell me that it does not), or it's just the initrd that is improperly configured. The other things that bothers me, is that changing the partition type of the raid partitions (fd to 0 - Empty), to disable raid autodetection, resulted in the same behavior on boot. Which might lead me again to think about configuration file problem instead of improper setup.The live cd doesn't not seem to recognize raid, so i can't inspect problems any further, but i could inspect system configuration, but i don't really know where to start.
View 2 Replies
View Related
Jul 4, 2010
I recently updated the kernel to the newest version(2.6.32-23-generic) using the update manager and now I am unable to boot in to my Lucid installation.
My setup is LVM on top of a RAID 0 array. My computer had been running in this configuration since Lucid was released.
The Error Code I get on Boot is to the effect of: /dev/mapper/ubuntu-os is not available.. and then I get kicked in to Busy Box.
Once in Busy Box if I try to use mdadm to mount the RAID array I get this error:
If I boot in to the live CD I can mount all of the partitions and LVM volumes, so it does not appear to be a failed drive or volume.
I have looked in the mdadm.conf, lvm config and grub config files and searched the "Google" for an answer with no-avail...
Ultimately I would like to find a solution which doesn't involve a re-installation.
View 6 Replies
View Related
Jun 15, 2011
One thing I always do is switch to the vmlinuz-generic(-smp) kernel in /etc/lilo.conf and build an initrd (see /boot/README.initrd for details). The "huge" kernel used by default is only meant for installing and not recommended for everyday use. It has a lot of drivers you don't need built-in and uses more RAM than the "generic" kernels.
still trying to find my feet and get to know Slackware. In one of my previous threads, 'things to do after installing' i was told the above message. When i installed, it used the huge kernel, but i'm unsure if that was the one that got installed. when i start slackware up, above the login screen it say, �wecome to Linux 2.6.37.6-smp (tty1)� I was wondering how to swich to the generic smp kernel, do I just change the vmlinuz to the desired, in lilo?
View 9 Replies
View Related
Feb 6, 2011
I just added an 80GB Maxtor 6Y080P0 HDD to my computer and when I'm booting into linux (Slackware 13.1) I get:
~
NTFS volume version 3.1.
VFS: Mounted root (NTFS filesystem) read-only on device 8:1.
devtmpfs: error mounting -2
Freeing unused kernel memory: 636k freed
Write protecting the kernel text: 9564k
Write protecting the read only data: 2448k
Warning: unable to open initial console.
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
pid: 1, comm: swapper Not tainted 2.6.33.4-smp #2
Call trace:
~
The HDD I'm booting from is a 20GB Maxtor and is the 3rd slave. The new 80GB one is the 3rd master.
View 1 Replies
View Related
Feb 28, 2011
having updated my Debian box, it ceases to boot kernel 2.6.32 with above error. Booting an older kernel (2.6.26) seems to run init without problems.
View 2 Replies
View Related
Apr 8, 2010
I've changed for huge kernel to a generic+initrd setup per the instructions in the README.initrd file however my machine fails to boot using that method. I get the following errors:
/boot/initrd.gz: Loading kernel modules from initrd image:
mount: mouting /dev/sda2 on /mnt failed: No such device
ERROR: No /sbin/init found on rootdev (or not mounted)
1. I've created the initrd using the results from /usr/share/mkinitrd/mkinitrd_command_generator.sh
mkinitrd -c -k 2.6.33.1 -f ext4 -r /dev/sda2 -m usbhid:ehci-hcd:ext4 -o /boot/initrd.gz
2. my root fs is ext4 on /dev/sda2
3. I've changed all necessary links in /boot
4. I've changed my /etc/lilo to:
image = /boot/vmlinuz
initrd = /boot/initrd.gz
root = /dev/sda2
label = Linux-Generic
read-only
View 12 Replies
View Related
Sep 19, 2010
I am going to change my hardware soon, just a new motherboard and cpu, same sound card,gfx card and other stuff. Will it boot and run ok ( like a live cd/dvd) until I have time to do a reinstall or does it have specific ports the hardware is installed on now?
View 6 Replies
View Related
Mar 20, 2011
I was interested in the idea of the btrfs subvolumes, so I made a virtual machine and installed Slackware as per the instructions here: [URL] It all went very well, but when I tried to switch from the huge kernel to the generic kernel and use the initrd.gz generated from step 29 (except that I used 2.6.37.4-smp instead of whatever's there) in lilo.conf, it failed to boot. I also noticed that in the instructions themselves, the poster doesn't actually add the initrd.gz to lilo.conf, so I'm guess the huge kernel has everything it needs to boot properly.
View 13 Replies
View Related
May 3, 2011
I've installed Slackware64 on a Toshiba Qosmio laptop (booting with ext4, SAMSUNG HM500JI HDD, 3 GB Ram, Intel Core 2 Duo Processor, Intel chipset and graphics).The system boots the huge kernel just fine. But after booting with the generic kernel AND after having prepared a mkinitrd with the mkinitrd generator, the boot process crashes at ~4sec with a panic.
View 14 Replies
View Related
Feb 16, 2011
My Slackware boots using the huge kernel. I am not using LILO; I am using GRUB from the extras directory on the DVD. I followed the tutorial @ [URL] up to the point where it discusses modifying LILO. My /boot/grub/menu.lst reads, in part:
# Linux bootable partition config begins
title Slackware Linux on (/dev/sda7)
root (hd0,6)
kernel /boot/vmlinuz root=/dev/sda7 ro vga=normal
# Linux bootable partition config ends
This boots the huge kernel. What changes must I make to the above menu.lst entry to boot using the generic kernel?
View 3 Replies
View Related
Mar 15, 2011
i'm attempting to configure the vmware server on the above mentioned system,without luck.i can't get the vmmon to compile. I have tried this out-dated guide [URL] but no luck. I have setup made the necessary links as explained in this guide [URL] I haven't managed to try out the any-any patch since no link to the patch is alive anymore.Since slack 13.37 is using 2.6.37.3 kernel I wonder if anyone has found a way to compile the vmware modules on these recent kernels.
View 12 Replies
View Related
Mar 20, 2011
I just imaged my RHEL 4 system that was running on a Dell Poweredge 2950 server using Acronis software and I restored the image to a VmWare virtual machine.
Dell Poweredge 2950 - RAID 5
VmWare - using ESX 4.0
OS - Red Hat Enterprise Linux 4 ES Update 5 x64
kernel - 2.6.9-55.0.9.ELsmp
I'm getting the following when I try to boot on the new virtual machine. I'm thinking it has to do with the fact that it's new hardware and it's having trouble either finding the right drivers or pointing to the correct place.
"No Volume Groups found
Volume Group "Volgroup00" not found
ERROR: /bin/lvm exited abnormally! (pid505)
mount: error 6 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!"
I was able to boot into Linux rescue mode using the boot CD. Then I typed:
#chroot /mnt/sysimage
Here's all the info from the commands I typed:
#ldd /bin/bash
libtermcap.so.2 => /lib64/libtermcap.so.2
libdl.so.2 => /lib64/libdl.so.2
libc.so.6 => /lib64/tls/libc.so.6
/lib64/ld-linux-x86-64.so.2
#uname -a
Linux localhost.localdomain 2.6.9-89.EL x86_64
#df -h ....
I've tried the following:
1. mkinitrd -v -f /boot/initrd-2.6.9-55.0.9.EL.img 2.6.9-55.0.9.EL
2. modified the device.map to point to /dev/sda3
3. changed the SCSI controller in Vmware to use BusLogic instead of LSI Logic. (didn't work because I'm running 64 bit.. gave me an error message)
4. grub-install --recheck /dev/sda
5. tried booting to differerent OS versions (i.e. 2.6.9-55.0.6, etc.). I tried all of the versions listed in the boot menu.
None of these worked.
View 2 Replies
View Related
Jul 4, 2011
I just did a full install of Slackware64 on my netbook. Everything was sweet until I tried switching to the generic kernel. Even before this, I noticed when I ran the mount command it listed not sda3, which really is the root partition, but /dev/root as the root partition. This also appears in mtab, but not fstab. So yeah, here are the errors when I try booting into the generic kernel:
Code: mounting /dev/sda3 on /mnt failed: No such device No /sbin/init found on rootdev (or not mounted) bin/sh: cant access tty: job control turned off
I've tried rebuilding the mkinitrd_command_generator.sh script several times, as well as lilo.conf. But no success I've looked at some similar old threadss here but most of them are related to slackware 12 and older, so I don't know if these issues are related or not.
View 8 Replies
View Related
Jul 22, 2010
I am trying to setup Slacware 13.1 x86_64 to a encrypted partition. I used the README_CRYPT.TXT howto : [URL] At the step when I create an initrd.gz I get this error: Quote: ERROR: No /lib/modules/2.6.33.4-smp kernel modules tree found for kernel "2.6.33.4-smp"
I tried to look into the directory and there was only modules under 2.6.44.3. So I tried to change the command into: Quote: mkinitrd -c -k 2.6.33.4 -m ext3 -f ext3 -r cryptroot -C /dev/sda2
This command was successful, but I don't know if this is alright. I made the changes in lilo.conf, add initrd = initrd.gz. This is all on unencrypted /boot partition. The boot=/dev/sda1 I also set for the unencrypted boot partition. When I boot the system I get a kernel panic:
[Code]....
View 5 Replies
View Related
Feb 27, 2011
I'm on Ubuntu 10.10 - fresh install 2 days ago, I marked all packages for upgrade in Synaptic, everything upgraded except 'linux-image-2.6.35-22-generic' kernel image. Now everytime I use apt-get or synaptic it takes ages as it tries to update the kernel image every time. The error I am receiving is as follows:
[Code]....
View 3 Replies
View Related
Mar 4, 2010
Having trouble booting into Kubuntu originally installed with Wubi.The system returns this error:
Code:
mount: mounting /dev/loop0 on /root failed: Device or resource busy
mount: mounting /sys on /root/sys failed: No such file or directory
[code]....
View 1 Replies
View Related
Oct 11, 2010
I've recently installed 10.10 onto my laptop, a Toshiba Equium A-100. It's been working perfectly for the last few weeks, but today I woke up, booted and got this;
Code:
mount: mounting dev/disk/by-uuid/9f8e1fd1-ca75-4eeb-8afc-a6b7bd756180 on /root
failed: Invalid argument
mount: mounting /dev on /root/dev failed: No such file or directory
[code]....
I'm a bit of a linux newbie, and while I can use the system fine, once we get into a shell I'm out of my depth. My laptop is useless now, and, unluckily, my 2000 word end-of-semester submission is on it. No, I didn't back it up because I wrote it last night. Arrgh.
View 6 Replies
View Related
Nov 15, 2010
I hope that you will be able to help me. I know that my topic may seem the same as some other threads, but there is a twist and it seems that I can't sort things out. I installed Ubuntu on the family's 4 year old Dell about a year ago when Windows stopped working (too many bluescreens!). It seed to be good, until one day when I tried to boot and it listed some codes on a black screen. I then reinstalled ubuntu from one of my disks, and it worked fine... until the entire thing occurred again a week later. This happened once or twice more, until today's problem:
It won't boot into ubuntu and also has white writing on the black background (read this below). I tried to reinstall from a ubuntu install disk, burned additional install disks, made an install usb, and also tried opensuse. They all say the below message when I try to boot into the disk:
Killed
mount: mounting on /dev on root/dev failed: No such file or directory
mount: mounting on /sys on root/sys failed: No such file or directory
mount: mounting on /proc on root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init.
[Code]...
View 3 Replies
View Related
Oct 1, 2010
I have installed Ubuntu 10.04 .. normally and I installed also some programs; I had problems with the monitor and many times I shutted dow the CPU when I changed the monitor and turned on angain and appears a black screen:after
mount: mounting /dev on root/dev failed: no such such file or dir
mount: mounting /sys on root/sys failed: no such such file or dir
mount: mounting /proc on root/proc failed: no such such file or dir
[code]...
View 3 Replies
View Related
Apr 17, 2011
I have an Acer netbook with the netbook version of Ubuntu and Windows 7. When I try to boot on Ubuntu I get a terminal that says "Target filesystem doesn't have /sbin/init. No init found. Try passing init= bootarg." I've found questions about this, but I get lost at "after booting from livecd." I put ubuntu-10.10-netbook-i386 on a flash card, but I don't know how to boot from it; I think that's my main problem.
View 4 Replies
View Related
Sep 15, 2010
when I start my laptop (Ubuntu 10), it even doesnt offer log in and writes this:mount: mounting/ proc on / root/ proc failed: No such file on directory Target filesystem doesntt have sbin/init. No init found. Try passing init=bootarg.device scan complete, Attached scsi generic sg2 type 0I tried to restart it several times, but it shows the same. The evening before I used it to show some files on projector and after I disconnected my laptop from it, it was a bit slower, but working. And the next morning I get that message. As I just started with Linux,
View 3 Replies
View Related
