search for: rdshell

...l init! Pid: 1, comm: init Not tainted 2.6.32-358.el6.i686 #1 After removing "quiet" and adding "selinux=disabled", I got more information; the boot stalls after finding devices, and gives: No root device "block:/dev/mapper/live-rw" found dracut suggests adding "rdshell", which I did. This was not helpful (I had no idea what to do in the dracut shell), but did notice that in the dracut shell /dev/ did NOT seem to contain my USB drive at /dev/sdb as I would expect. (One reason it seemeed not helpful) So: 1) I used VFAT rather than ext2/3/4. Do I have to use e...

...ld server die; we had another, same model, sitting around lightly used, so I did what I've done before: swap the RAID card into that, swap the drives, even putting them in the same bays as the dead one, and boot. Nope. 100% of the time, when it hits switching roots, it kernel panics. Adding rdshell to the kernel line does nothing, I get no grub rdshell. Booting from a flash drive into rescue, it finds everything, *perfectly*, and mounts it all, including the RAID data drives. I've rebuilt the initrd, and no joy. Anyone have an idea? mark

...cut: dracut-004-303.el6 udev: starting version 147 udevd (61): /proc/61/oom_adj is deprecated, please use /proc/61/oom_score_adj instead. dracut: Starting plymouth daemon dracut Warning: No root device "block:/dev/hda1" found dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line. dracut Warning: Signal caught! dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line. Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 3.0.0 #1 Call Trace: [<ffffffff814e5d7a...

...ont: xvde1: barriers disabled blkfront: xvdf: barriers disabled xvdf: unknown partition table %Gblkfront: xvdg: barriers disabled xvdg: unknown partition table dracut Warning: No root device "block:/dev/xvda1" found %G%G dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line. dracut Warning: Signal caught! dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line. Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32-220.7.1.el6.x86_64 #1 Call Trace: [...

> -----Original Message----- > From: Wes James [mailto:comptekki at me.com] > Sent: Wednesday, January 27, 2016 7:04 PM > To: CentOS mailing list > Subject: Re: [CentOS] CentOS 7, 327 kernel still crashing > > > > On Jan 27, 2016, at 1:47 PM, m.roth at 5-cent.us wrote: > > > > I've just added the following to the CentOS bugtracker for CentOS-7 > >

I am trying to create a CF card that boots 686 CentOS 6.3 On boot I get a message about /dev/disk/by-label/\x2f where \x2f is "/" cannot be found. Adding rdshell to the boot line and booting up sure enough the /dev/disk directory does not exist. What "creates" that early on in the boot process? My CF card was changed from UUID to LABEL. So I edited grub.conf and make root=LABEL=/ like the OLD 5.X days. Clearly I have missed something else when s...

...Interrupt Remapping [Enabled] Coherency Support [Disabled] ATS Support [Enabled] Pass-through DMA Support [Enabled] Everything works so far, but when I add intel_iommu=on to the kernel line of my grub.conf, Dracut gives my a kernel panic while booting. I added "rdshell" to the command line and extracted the boot messages via dmesg (http://nilscaspar.ch/centos-dmesg.log). I think the main problem is this: dracut Warning: No root device "block:/dev/disk/by-uuid/280234d1-dff5-4e04-b1ef-93d54cdcd825" found But I doesn't make sense to me... As soo...

...level 5 boot. shutdown system, rebooted level 3, boot crashed again. error message; =+=+= ACPI: wmi: Mapper loaded dracut Warning: No root device "block: /dev/disk/by=uuid/dbb9f9c4-8f67- \ 4d79-aaef-4f804f31c800" found dracut Warning: Boot has failed. To debug this issue add "rdshell" to the \ kernel command line. dracut Warning: Signal caught! dracut Warning: Boot has failed. To debug this issue add "rdshell" to the \ kernel command line. kernel Panic - not syncing: Attempted to kill init! Pid: 1, comm: init Tainted: G I-------2.6.32-358.el6.x86_64 #...

Just installed CentOS 6.3 from a minimal install disc. All was well, so I ran a yum update, as well as installed some additional packages (mysql, httpd, libjpeg, libpng, and more that I don't remember off the top of my head). Went to reboot the machine and now it won't book up. As it starts to boot, says: Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not

Hi, I am trying to recover data from my old system which had LVM. The disk had two partitions - /dev/sda1 (boot, Linux) and /dev/sda2 (Linux LVM). I had taken a backup of both partitions using dd. Now I am booting of CentOS live cd for system restore. I recreated partitions like previous system using fdisk and then used dd to dump all the data onto it. I would like to mount sda2 as LVM, but I

...a bunch, 2 SATA 6GBps and 6 SATA 3GBps). When I booted the box after this, I got a kernel panic, the typical "Can't find root device". I read some docs, and first tried to boot from a rescue disc and reinstal GRUB, but that didn't change anything. Further Googling got me the rdshell kernel parameter, and that dropped me to a shell when it failed to find the root device. Reading https://fedoraproject.org/wiki/How_to_debug_Dracut_problems , I did the following: # lvm vgscan # lvm vgchange -ay And then # ln -s /dev/mapper/<volumegroup>-<root_volume> /dev/root #...

...;. [ 3.324998] <servername> systemd[1]: Unit systemd-fsck-root.service entered ff ailed state. [ 3.325430] <servername> systemd[1]: systemd-fsck-root.service failed. [ 3.326752] <servername> systemd[1]: Stopped dracut pre-pivot and cleanup hooo And it stops, and drops me into the rdshell. Not that I can mkdir /mnt, and mount /dev/sda1, and /boot is there, and I can mount /dev/sda3, and root is there just fine. mark

Good day - This is my first post to this list , and I''m new to Xen - any help on this issue would be much appreciated . I downloaded, built and installed xen-4.2.1 (hypervisor and tools) on an x86_64 ArchLinux box updated to latest software as of today. I am trying to bring up a Linux guest from a remote iSCSI disk. The iSCSI-initiator (open-iscsi) logs in to the remote target OK and