similar to: Cannot open root device "LABEL=/" on 00:00

Hi, I've just moved over to an Opteron 246 dedicated server and have used up2date to install the latest kernel (2.4.21-27.0.4.Elsmp). However, when the machine reboots it never comes back up and according to the datacentre technicians, this is what's happening: VFS: Cannot open root device"806" or 08:06 Please append a correct "root=" boot option Kernel

Hi! Please see bellow. Note that web1.dasilva.network is the address of the local machine where one of the bricks is installed and that ties to mount. [2017-08-20 20:30:40.359236] I [MSGID: 100030] [glusterfsd.c:2476:main] 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 3.11.2 (args: /usr/sbin/glusterd -p /var/run/glusterd.pid) [2017-08-20 20:30:40.973249] I [MSGID: 106478]

On Mon, Aug 21, 2017 at 2:49 AM, Cesar da Silva <thunderlight1 at gmail.com> wrote: > Hi! > I am having same issue but I am running Ubuntu v16.04. > It does not mount during boot, but works if I mount it manually. I am > running the Gluster-server on the same machines (3 machines) > Here is the /tc/fstab file > > /dev/sdb1 /data/gluster ext4 defaults 0 0 > >

Hi! I am having same issue but I am running Ubuntu v16.04. It does not mount during boot, but works if I mount it manually. I am running the Gluster-server on the same machines (3 machines) Here is the /tc/fstab file /dev/sdb1 /data/gluster ext4 defaults 0 0 web1.dasilva.network:/www /mnt/glusterfs/www glusterfs defaults,_netdev,log-level=debug,log-file=/var/log/gluster.log 0 0

Hi, I am trying to create a scatterplot, coding each point to one of 5 populations. I was successful when I did this for one set of data, yet when I try plotting other data a blank plot appears (although the axes are labelled and I can fit the regression lines from each population). I have tried a variety of things to fix this but nothing seems to work. I can plot the points if I do not

https://rhn.redhat.com/errata/RHSA-2005-043.html refers updated files :- updates/i386/RPMS/kernel-2.4.21-27.0.2.EL.athlon.rpm updates/i386/RPMS/kernel-2.4.21-27.0.2.EL.i586.rpm updates/i386/RPMS/kernel-2.4.21-27.0.2.EL.i686.rpm updates/i386/RPMS/kernel-2.4.21-27.0.2.EL.src.rpm updates/i386/RPMS/kernel-BOOT-2.4.21-27.0.2.EL.i386.rpm updates/i386/RPMS/kernel-doc-2.4.21-27.0.2.EL.i386.rpm

Hi, I have updated the kernel to 2.4.21-27.0.2 on Centos 3.4 (was 3.3 when I did the kernel update) and have modified grub.conf to use the single CPU kernel: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. #

I'm attempting to upgrade to kernel-smp-2.4.21-27.0.4.EL (x86_64) on a Dell 1850. The new kernel is panicing on reboot. When comparing against the current working kernel, I just noticed that we're currently running the "UP" kernel: [root at polaris root]# uname -srvp Linux 2.4.21-27.0.2.EL #1 SMP Wed Jan 19 11:49:43 CST 2005 x86_64 First question... why is the kernel

Hi, There seems to be a problem with the timer resolution on x86_64. This is clear in ping results - I don't know if it's just a ping problem or if it manifests elsewhere as well. It does also affect mtr and traceroute times. I guess it's more a kernel issue than a CentOS problem, but is anyone else seeing the same? Ping results have a resolution of 10ms - so a ping <10ms

Good evening all, I''ve all but finished installing Xen 2.0.5, XenLinux 2.6.10 and Debian GNU/Linux 3.0r4 into /boot on a colo box currently (and temporarily) running CentOS. I''ve chrooted into the debian install (chroot /boot /bin/bash) and was able to set everything up, install requisite packages, install xen, etc. Now I''m at the last step and I''ve run into

After updating a very old x86_64 3.x install to 3.8 it still has kernel-2.4.21-27.0.2.EL. Then if I repeat the yum update command, it offers to install kernel 2.4.21-47.EL.ia32e. Neither of these situations seems quite right. -- Les Mikesell lesmikesell at gmail.com

New kernel packages are available for CentOS-3 x86_64. Refer to https://rhn.redhat.com/errata/RHSA-2004-689.html. RPMS/kernel-2.4.21-27.0.1.EL.ia32e.rpm RPMS/kernel-2.4.21-27.0.1.EL.x86_64.rpm RPMS/kernel-doc-2.4.21-27.0.1.EL.x86_64.rpm RPMS/kernel-smp-2.4.21-27.0.1.EL.x86_64.rpm RPMS/kernel-smp-unsupported-2.4.21-27.0.1.EL.x86_64.rpm RPMS/kernel-source-2.4.21-27.0.1.EL.x86_64.rpm

Hi, I know btrfs complicates filesystem lists due to the use of subvolumes. However, I just noticed that the root partition itself ends up being listed twice with list-filesystems, inspect-os, inspect-get-roots, etc... I'm seeing this in version 1.26, but haven't found anything directly resolving this in newer versions. These commands all show the partition listed twice as in the

Hi, I want tested Xen with my OS based on a kernel 2.4 (it''s a CentOS 3.4). I downloaded the unstable sources of xen (xen-unstable-src.tgz). I read the user guide and I verified the "Prerequisites", I''ve : - the "iproute 2" package - the "linux bridge utils" - an installation of Twisted - gcc, binutils & make -

Hi Everyone, Long time reader, first time poster. FINALLY got my First AVM Fritz Card up and running under Centos 3.4 Installed the second....modified the drivers etc as per the instructions found at the wiki System boots Modprobe capi all good modprobe fcpci all good modprobe f2pci the kernel then goes into Panic If Modprobe f2pci before fcpci the kernel still goes into panic.

Dear all Can I get the kernel source for the centos 3.4 Release final kernel version is 2.4.21-27.0.2.EL Thanks Prasad

Is it possible to specify the root device in extlinux.conf by an ext2 label or uuid? How difficult is it to add this support if it is not there? I am in a situation where this is needed and my fstab is configured appropriately, but extlinux.conf still needs to be manually updated when the root drive changes to a different scsi device (due to the number of drives on the bus and the order of the

Finally, I was able to find a solution for this. I'm posting the result here, just in case that it's useful for someone else in the future ... The problem was not in initramfs (dracut), but on the fact that /dev/sda2 partition(PV), after I resized it, somehow got 2 partition table signatures. One was set as a "dos" partition with an offset "0x1fe" and second set as

We are running 2-node RAC on RedHat Linux-86 (32-bit) the following was done on (4/10/2005) 1. upgrade OS to update 4 (kernel-smp-2.4.21-27.0.2.EL) 2. upgrade OCFS 1.0.12 to ocfs-2.4.21-EL-smp-1.0.14-1 3. upgrade from 9.2.0.5 to 9.2.0.6 (IN 2-Node RAC) 4. change defualt temporary tablespace to regular one (Rac bug fix) 5. Enable aysnc mode by applying patch 3208258_9206 ** Patch 4153303 applied on

If i try to connect as root (dovecto 1.0) with wrong password doveco exit with an auth error robyt:~# telnet dns pop3 Trying x.x.x.x Connected to dns. Escape character is '^]'. +OK Dovecot ready. user root +OK pass [wrong] -ERR Authentication failed. but if the password is correct dovecot exit but with another error: user root +OK pass [correct] -ERR [IN-USE] Internal login failure.