search for: rdsosreport

I just tried to create a CentOS 7 VM on a CentOS 6 host, but it crashes to the dracut prompt. I am using the PXEBoot installer. I *think* it is unhappy with the (virtual) graphics controller, but I am not sure. The rdsosreport.txt file is available here: https://www.deepsoft.com/wp-content/uploads/2018/09/rdsosreport.txt -- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller at deepsoft.com -- Webhosting...

...] VM boot failed sometimes if using vhost-user-blk with spdk I enable debug of systemd-udevd by changing guest's /etc/udev/udev.conf to this: udev_log="debug" and regenerate initramfs. Then, we can get more message about this issue. I select some useful messages from /run/initramfs/rdsosreport.txt: systemd-udevd[199] probe /dev/vdb raid offset=8 systemd-udevd[199] no db file to read /run/udev/data/+virtio:virtio1: No such systemd-udevd[199] handling device node '/dev/vdb', devnum=b253:16, mode=0660, systemd-udevd[199] set permissions /dev/vdb, 060660, uid=0, gid=6 syst...

...ling list <centos at centos.org> wrote: > > I just tried to create a CentOS 7 VM on a CentOS 6 host, but it crashes to the > dracut prompt. I am using the PXEBoot installer. I *think* it is unhappy > with the (virtual) graphics controller, but I am not sure. > > The rdsosreport.txt file is available here: > https://www.deepsoft.com/wp-content/uploads/2018/09/rdsosreport.txt > -- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller at deepsoft.com --...

...ue[256]: Warning: /dev/mapper/centos_webman11-root does not exist Starting Dracut Emergency Shell... Warning: /dev/centos_webman03/root does not exist Warning: /dev/centos_webman03/swap does not exist Warning: /dev/mapper/centos_webman11-root does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. dracut:/# After some monkeying around wi...

...0, with dual Tesla cards, one R420, with a fibre card for a RAID device, it never switches root. All these systems have Xeons, not AMD CPUs. We've had this with every one of the 327 kernels. In addition, it seems to happen also with the 229.20.1; the 229.14.1 has no such problem. >From the rdsosreport: starting at line 126: /dev/disk/by-label: total 0 lrwxrwxrwx 1 root 0 10 Jan 27 19:03 SWAP -> ../../sda2 lrwxrwxrwx 1 root 0 10 Jan 27 19:03 \x2f -> ../../sda3 lrwxrwxrwx 1 root 0 10 Jan 27 19:03 \x2fboot -> ../../sda1 Then, starting at line 1283: [ 3.317027] <servername> system...

...er, with CentOS 7, boot crashes out with.... [  OK  ] Reached target Basic System. dracut-initqueue[555]: Warning: Could not boot. dracut-initqueue[555]: Warning: /dev/root does not exist          Starting Dracut Emergency Shell... Warning: /dev/root does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. dracut:/# Some googling suggests this i...

...### output of cat /prod/mdstat Personalities : md126 : inactive sda5[0](S) 15727616 blocks super 1.2 md127 : inactive sda2[0](S) 104856576 blocks super 1.2 unused devices: <none> ### content of rdosreport.txt It's big; see http://chico.benjamindsmith.com/rdsosreport.txt

...hat I'm doing wrong in here ? As I previously said, this is a new installation, so I could simply reinstall the whole thing, but I would rather try to find out some answer to why is this happening ... :-) [curiosity] Some additional details: ================== I've attached /run/initramfs/rdsosreport.txt file [generated while in inird] here: https://privatebin.net/?fdc4052c0c402884#gdB/QYR3IeR55SxUbjfrkZPQfJ7jMxiUxq5DWhTVbWc= o/s ver=CentOS Linux release 7.5.1804 (Core) [root at localhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 13G 0 disk ??...

...: Warning: Could not boot. [ 194.557324] dracut-initqueue[227]: Warning: /dev/disk/by-uuid/bbafa3a5-0a24-40d2-a362-03cb33d5d76b does not exist Starting Dracut Emergency Shell... Warning: /dev/disk/by-uuid/bbafa3a5-0a24-40d2-a362-03cb33d5d76b does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. dracut:/# Server OS is CentOS 7.3 using Xen...

...this has happened more then once and had to reinstall. Any way I can prevent this when I shutdown or restart? This happens when I reboot the machine. Sorry, but you've given us absolutely no information at all. There's more than 8001 possibilities. So the least you can do is extract the rdsosreport.txt if you're dropped to a shell. Or boot from install media, with the rescue boot parameter option, and try mounting the volume, and if that fails, also xfs_repair and give that result. And then collect dmesg which will have mount failure info for sure, and maybe it will also have extra messag...

...a two-disk RAID1 mirror.? I pulled one drive, waited for the kernel to acknowledge the missing drive, and then rebooted.? The system started up normally with just one disk (which was originally sdb). > ### content of rdosreport.txt > It's big; see > http://chico.benjamindsmith.com/rdsosreport.txt > > [??? 0.000000] localhost kernel: Command line: > BOOT_IMAGE=/boot/vmlinuz-0-rescue-4456807582104f8ab12eb6411a80b31a > root=UUID=1b0d6168-50f1-4ceb-b6ac-85e55206e2d4 ro crashkernel=auto > rd.md.uuid=ea5fede7:dc339c3b:81817fc4:aba0bd89 > rd.md.uuid=7a90faed:4e5a2b50:9baa...

...R420, with a fibre card for a RAID > device, it never switches root. All these systems have Xeons, not AMD > CPUs. > > We've had this with every one of the 327 kernels. In addition, it seems to > happen also with the 229.20.1; the 229.14.1 has no such problem. > > From the rdsosreport: > starting at line 126: > /dev/disk/by-label: > total 0 > lrwxrwxrwx 1 root 0 10 Jan 27 19:03 SWAP -> ../../sda2 > lrwxrwxrwx 1 root 0 10 Jan 27 19:03 \x2f -> ../../sda3 > lrwxrwxrwx 1 root 0 10 Jan 27 19:03 \x2fboot -> ../../sda1 > > Then, starting at line 1283: &...

...ot;dos" partition, hence refused to activate centos/root and centos/swap LVs which were required to boot the machine to the O/S. What's interesting is that neither fdisk or parted were showing this second signature, however there was a trace of it in the dracut report file (/run/initramfs/rdsosreport.txt), specifically the one below.. + blkid /dev/sr0: UUID="2016-10-28-12-18-36-00" LABEL="CentOS 7 x86_64" TYPE="iso9660" PTTYPE="dos" /dev/sda1: UUID="a620a180-3a8c-4b5f-ad30-804f131a7261" TYPE="xfs" /dev/sda2: PTTYPE="dos" +...

...ing fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt ------------------------------------------------ [...] [ 14.780428] localhost kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready [ 19.977052] localhost kernel: tg3 0000:0b:00.0 eno1: Link is up at 1000 Mbps, full duplex [ 19.977118] localhost kernel: tg3 0000:0b:00.0 eno1: Flow...

Hello! On my server PC i have Centos 7 installed. CentOS Linux release 7.6.1810. There are four arrays RAID1 (software RAID) md124 - /boot/efi md125 - /boot md126 - /bd md127 - / I have configured booting from both drives, everything works fine if both drives are connected. But if I disable any drive from which RAID1 is built the system crashes, there is a partial boot and as a result the

...> As I previously said, this is a new installation, so I could simply > reinstall the whole thing, but I would rather try to find out some answer > to why is this happening ... :-) [curiosity] > > Some additional details: > ================== > I've attached /run/initramfs/rdsosreport.txt file [generated while in > inird] here: > https://privatebin.net/?fdc4052c0c402884#gdB/QYR3IeR55SxUbjfrkZPQfJ7jMxiUxq5DWhTVbWc= > > o/s ver=CentOS Linux release 7.5.1804 (Core) > > [root at localhost ~]# lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda...

> Yannis Milios wrote: >>> But, what happens if you let the kernel post install scripts do the >>> work or setting up the initrd things? >> >> Initially, I just rebooted from LiveCD and left Grub,kernel and dracut >> do >> their job with the defaults, but unfortunately, boot process stops at >> initrd (dracut) stage with the following error:

...a RAID >> device, it never switches root. All these systems have Xeons, not AMD >> CPUs. >> >> We've had this with every one of the 327 kernels. In addition, it seems >> to happen also with the 229.20.1; the 229.14.1 has no such problem. >> >> From the rdsosreport: >> starting at line 126: >> /dev/disk/by-label: >> total 0 >> lrwxrwxrwx 1 root 0 10 Jan 27 19:03 SWAP -> ../../sda2 >> lrwxrwxrwx 1 root 0 10 Jan 27 19:03 \x2f -> ../../sda3 >> lrwxrwxrwx 1 root 0 10 Jan 27 19:03 \x2fboot -> ../../sda1 >> >&gt...

...0's, but I could be wrong, just all do the same thing on boot. ***************** I've just updated a CentOS 7 server to the latest kernel, vmlinuz-3.10.0-327.4.5.el7.x86_64, and the server fails to boot. It has failed on every 327 kernel. Server: Dell R420, 2 Xeons, 124G RAM. >From the rdsosreport.txt, the relevant portion is: [ 3.317974] <servername> systemd[1]: Starting File System Check on /dev/disk// by-label/\x2f... [ 3.320089] <servername> systemd-fsck[590]: Failed to detect device /dev/diskk /by-label// [ 3.320567] <servername> systemd[1]: systemd-fsck-root.service:...

Hi, Everytime I restart Centos 7 I receive a error saying? metadata is corrupt and then I need to go through the process of mount and unmount the disk uuid then run xfs_repair {some uuid} or xfs_repair -L {some uuid} which ultimately corrupts even more. I?m running on a RAID 1 two identical drives this has happened more then once and had to reinstall. Any way I can prevent this when I