Error No /sbin/init Found On Rootdev Or Not Mounted
mos98 Member Registered: 2010-02-07 Posts: 24 [solved] copy to new hard drive: no /sbin/init found I got myself a new hard drive so I copied my old system to the new drive.The partition layout of the new drive looks similar to the old one (only this time /boot is somewhat smaller than it used to be)WINDOWS /dev/sdb1 SWAP /dev/sdb2 BOOT (/boot) /dev/sdb3 EXTENDED /dev/sdb4 ROOT (/) /dev/sdb5 HOME (/home) /dev/sdb6To copy /, /boot and /home to the new drive I used the following command mount /dev/sdb3 /mnt/sdb3; cd /boot; find . -xdev -print0 | cpio -pdvum0 --sparse /mnt/sdb3I did the same thing for the other two partitions /dev/sdb5 and /dev/sdb6 (where /dev/sdb stands for the new drive)After that I re-installed Grub via the live cd. Everything went like a charm until I tried to boot fromthe new drive. This is the error message I see:Error: Root device mounted successfully, but /sbin/init does not exists. Bailing out, you are on your own. Good LuckI checked /sbin/init and it's definitely thereI thought maybe one should better use dd instead of cpio to copy the ROOT Partition from /dev/sda5 to /dev/sdb5So next thing I did was using dd instead of cpio like that dd if=/dev/sda5 of=/dev/sdb5 bs=32768 conv=noerror,syncwith unmounted hardrives in live cd mode.But the error still remains. I guess the error must be caused somewhere else. But how?Is there a better way to copy an existing installation to a new hard drive?Does anyone have some insight? Last edited by mos98 (2010-04-03 11:56:22) Offline #2 2010-03-31 13:25:11 stryder Member Registered: 2009-02-28 Posts: 498 Re: [solved] copy to new hard drive: no /sbin/init found Did you try to boot using the fallback option? Offline #3 2010-03-31 13:38:22 flamelab Member From: Athens, Hellas (Greece) Registered: 2007-12-26 Posts: 2,160 Re: [solved] copy
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 https://bbs.archlinux.org/viewtopic.php?id=94208 my Slackware partition to try and fix things. View 14 Replies Similar Messages: Slackware :: Software RAID 1 Versus LILO / Kernel-generic - ERROR: No /sbin/init Found On Rootdev Ubuntu :: Computer Will Not Load /sbin/init Error Ubuntu :: Error - No Init Found - Try Passing Init=bootarg Ubuntu :: Target Filesystem Doesn't Have /sbin/init.tes? Ubuntu :: Target Filesystem Doesn't Have /sbin/init Ubuntu :: Target Filesystem Doesn't Have /sbin/init. And http://linux.bigresource.com/Slackware-ERROR-No-sbin-init-found-on-rootdev-or-not-mounted--9QXCy0y8W.html More? General :: Target Filesystem Doesnt Have /sbin/init? General :: Ubuntu Booting :Can't Find /sbin/init? Ubuntu :: Target Filesystem Cant Find Sbin/init? Ubuntu Servers :: Target Filesystem Doesn't Have /sbin/init? Ubuntu :: Targe File System Doesn't Have /sbin/init? Ubuntu Installation :: Can't Find /sbin/init, Drops To Busybox Ubuntu :: 10.04 Cant Boot - Target Filesystem Doesnt Have /sbin/init Ubuntu :: Target Filesystem Doesn't Have /sbin/init (Can't Boot)? Ubuntu Installation :: Target Filesystem Doesn't Have /sbin/init? Ubuntu :: 10.10 - Target Filesystem Doesn't Have Requested /sbin/init Ubuntu :: Computer Seemed To Be Frozen - Reboot - No Init Found. Try Passing Init - Bootarg" Ubuntu Installation :: 10.04 And 10.10 Recurringly Crash (target System Does Not Have Requested /sbin/init )? Debian Installation :: Live Crashes With Error - 0x8DF6 Init Table Command Not Found Ubuntu :: Wont Boot - "no Init Found. Try Passing Init=bootarg" General :: Kernel Panic - Not Syncing - No Init Found - Try Passing Init - Option To Kernel Ubuntu :: Unable To Boot - Get "target System Doesn't Have /sbin/init" Server :: Redhat ES ( 2.4.21-50.Elsmp) Not Booting - Error "no Init Found" Ubuntu :: Can't Access Disk After "no Init Found" Error Debian :: INIT: Cannot Execute "/sbin/mingetty" General :
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings http://unix.stackexchange.com/questions/139802/error-root-device-mounted-successfully-but-sbin-init-does-not-exist and policies of this site About Us Learn more about Stack Overflow the http://askubuntu.com/questions/733251/cannot-boot-as-sbin-init-is-reported-missing company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes error no a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top ERROR: Root device mounted successfully, but /sbin/init does not exist up vote 6 down vote favorite 1 I've installed Linux Mint and Manjaro Linux on my computer. I installed only the Linux mint on the MBR. error no /sbin/init For Manjaro, I created a /boot/efi partition, but I have not checked to install to MBR. So, I am controlling grub from mint. Now, when I try to boot Manjaro, it shows : ERROR: resume: no device specified for hibernation: performing fsck on dev/sda11 /dev/sda11: clean 1727/915712 files, .... blocks WARNING: The root device is not configured to be mounted read-write!It may be fsck'd again later :mounting /dev/sda11 on real boot running cleanup hook [udev] ERROR: Root device mounted successfully, but /sbin/init does not exist. sh:can't access tty; job control turned off [rootfs /]# After the shell prompt, I can't write anything. It hangs, or sometimes it shows me messages continuously like : usb 3-3: device not accepting address 2, error -62 and so on... I tried to add init=/usr/lib/systemd/systemd to grub, as I saw in google, but still the same. I must note that for the Manjaro installation I am using a separate partition for / and for /usr and for /var. This maybe have an influence? As I saw here . But the problem is that I can't write anything, it hangs. I
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Cannot boot as /sbin/init is reported missing up vote 0 down vote favorite I use Ubuntu 14.04. A few days ago, I logged off, then my computer was unresponsive as I tried to log back on. I do not recall installing any software or changing any setting that could have caused this. Since then, whenever I have tried to boot, I receive the following error messages: mount: mounting /dev/mapper/ubuntu--vg-root on /root failed: invalid argument mount: mounting /dev on /root/dev failed: No such file or directory mount: mounting /sys on /root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have requested /sbin/init No init found. Try passing init= bootarg. BusyBox v1.21.1 (Ubuntu 1:1.21.0-1ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Something similar seems to have happened to other users before: This post recommends Ubuntu Boot-Repair. I tried it, selected "recommended repair", and received a message that it was successful. However, after a restart, the error message appeared as before. The log of Boot-Repair can be found here. Here, I found the suggestion of booting from a live disk and using fsck -f. The command came back without an error code, but the booting problem persisted as before. Likewise when I tried e2fsck, as suggested here. Here, someone suggests editing the Grub configuration. I tried it, again to no effect. If anyone could come up with something else I can try, I would much appreciate it. EDIT: After posting this, I stumbled upon the recommendation that I use Rescatux to post a log of the boot info script. Here it is: paste.ubuntu.com/15049548/ boot share|improve this question edited Feb 14 at 1:38 asked Feb 13 at 18:02 jphaller 13 add a comment| 1 Answer 1 activ