similar to: CentOS 5 Beta Dual Boot Problem

To test CentOS 5, I loaded from DVD adding it to a system at home running Fedora Core 7 T2. Partition Layout is: /dev/hda1 - / for the RH7T2 system /dev/hda2 - /home /dev/hda3 - swap /dev/hda4 - extended /dev/hda5 - / for CentOS 5 The system loaded cleanly and gave me the opportunity to tell grub about the other system. CentOS boots fine. Grub Stage 2 will show me both systems.

I am new to CentOS. I mostly use Fedora Core. I installed the CentOS 5 Beta on a test machine from the DVD. I configured it with both KDE and Gnome. I am using the default YUM configurtion which loaded with the DVD. Unlike FC7T2, CentOS 5 Beta does not seem to pick up Yum updates. Is this by design or do I need to add repos to my /etc/yum.repos.d? Thanks for any suggestions Bob Styma

>That should work, *IF*: > >a) hda5 is a FAT12/16 filesystem; >b) hda5 is <= cyl 1024. > > -hpa I got thinking booting off a logical partition might not be allowed, so I changed the LEAF/Bering logical partition to a primary, hda4. Then I ran "syslinux d:" from a Win98SE DOS-box to (try to) initialize the partition's boot record. And added this from a

Hi to all. I''m installed XEN3.1 correctly but I''m some problem to start it. XEN start but I received this message: VFS: Cannot open root device "hda5" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) This is strange because my grub is configured like this:

I installed C 6.0 in an empty partition. It functioned. Despite using the usually successful methods of booting into another operating system from C 5.7, I can't get into C 6.0 Tried:- title C6-0 (2.6.32-71.el6.x86_64) rootnoverify (hd0,6) chainloader +1 and root (hd0,6) kernel /boot/vmlinuz-2.6.32-71.el6.x86_64 ro root=UUID=67c62872-0c69-451c-8412-3c218c0d2cb0 rd_NO_LUKS rd_NO_LVM

Stephen McManus <step77 at f2s.com> wrote: > Finally got my install working, Centos didn't recognise my m/board NIC > so I had to install another NIC. Now, I've lost the windows install. I > need it for my Walkman and Palm. Never, ever got any distro to see the > Tunsgsten E. I can see the Win in Grub but it says there's a file > missing, insert system disk.

Hi, "Mircea Popescu" <nufarul.alb at go.ro> schrieb am 29.01.02: > I have this problem: > I've partitioned my hard drive with PQMagic 7 in the following way: > hda1 - fat32 > hda2 - ext2 > hda3 - fat16 > hda4 - extended > hda5 - Linux Swap > hda6 - fat32 > hda7 - ext2 > hda8 - fat32 > > I've put syslinux on

Hello, Sorry for the off-topic, but I've just installed CentOS 5 on my home box and I want to put the journal on another drive. I created a software RAID-1 device, /dev/md1, and formatted an ext3 file system on it. Now I want to move the journal to /dev/hda5. I've googled for this and the process appears to be: mkfs.ext3 -b 4096 -O journal_dev /dev/hda5 mkfs.ext3 -b 4096 -J

Hi, I'm trying to copy my CentOS install to a new drive. - old drive is /dev/hda and had hda1 : /boot hda2 : swap hda3 lvm hda5 : lvm hda4 : /usr/local - new drive is /dev/hdb hdb1 : /boot hdb2 : swap hdb3 : / I decided to get rid of lvm which is useless to me. I've created and formated the new partitions and copied anything from the old drive to the new one

I installed a 4.1 x86_64 with kernel 2.6.9-11.ELsmp (rpm) initially. My box is tyan 5350 and a SATA harddisk The install was successful and the harddisk was detected as /dev/sdaX But strangely, when I first reboot my machine. The harddisk change to /dev/hdaX What is the problem ? Below are some of dmesg output hda: WDC WD1200JD-00HBB0, ATA DISK drive Probing IDE interface ide1... Probing IDE

Hello, I'm new in ext3. I installed RH7.2 with ext3. For a short time it worked properly, but when I compiled the linux kernel (2.4.9-13) from RH package, the old kernel didn't boot again (I didn't change anything with the old binary). I downloaded kernel 2.4.14 and ext3 patch for this version. After the compilation and installation I rebooted the system. I got answer something

Good morning, I try to use the last release of ext3 patch with a 2.4.10 linux kernel. I have two troubles : - when the kernel is booting, I receive : NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 208k freed Adding Swap: 128480k swap-space (priority -1) Adding Swap: 128480k swap-space (priority -2) Why my root

I''ve seen this happen before, not sure why. I changed ''phy:'' to ''file:'' and it worked. I later rebooted and ''phy:'' worked again. So you might try ''file:'' rather than ''phy:''. -- Ray -----Original Message----- From: xen-users-bounces@lists.xensource.com

On Wed, Dec 9, 2015 at 1:07 PM, Emilio Lazo Zaia via Syslinux <syslinux at zytor.com> wrote: > I thought I've found three bugs on syslinux 6.03: Just to be clear, is this only affecting vesamenu.c32? > (1) With sample config file as is, i.e. leaving commented MENU VSHIFT and > MENU COLOR UNSEL but uncommented MENU COLOR SEL: > > A black "border" is displayed

Hi, I''ve installed xen-2.0.5 from source on gentoo, but the xen dom0 kernel doesn''t find the root device: ############################# snip ###################################### Kernel panic: VFS: Unable to mount root fs on unknown-block (3,3) ############################# snap ###################################### grub.conf: ############################# snip

I have been using the LEAF Bering firewall for a year or so. It boots with Syslinux 1.75. But Bering is too large for a 1440KB floppy, so it formats the diskette as 1680KB. Recently I found a small Compaq 2266 box to replace a larger Compaq 7170 to run the firewall. But when I try to boot the Bering diskette on the 2266 I get the following message: Loading Linux ............ Boot failed:

greetings, since i have a test server in front of me and i have never tried it i request your assistance please. ive always been a fdisk and lilo person i have a fresh CentOS 4 "test" install on a WD120 sata /dev/sda /dev/sda1 / /dev/sda2 /boot /dev/sda3 swap and it just so happens i have a old test 17Gig Maxtor PATA with a fresh Win98 on it from helping my father migrate to a newer

> [6] ctivating swap partitions: swapon: /dev/hda7: No such device or address > [6] [FAILED] > [6] ioctl 80041272 not supported by xl_block > [6] Finding module dependencies: depmod: Can''t open /lib/modules/2.4.24-xeno/modules.dep for writing > [6] [FAILED] > [6] Checking filesystems > [6] Couldn''t find matching filesystem: LABEL=/policy Edit your

I thought I've found three bugs on syslinux 6.03: (1) With sample config file as is, i.e. leaving commented MENU VSHIFT and MENU COLOR UNSEL but uncommented MENU COLOR SEL: A black "border" is displayed below the selected line and on its right edge. (2) Uncommenting MENU COLOR UNSEL: This effect appears also on separators and on right edge on every unselected lines. (3)

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R