similar to: Autodetecing RAID members upon boot... need to update initrd?

I have a system with 4 disk drives, two 512 Gb and two 1 Tb. It look like this: CentOS release 5.9 (Final) Disk /dev/sda: 500.1 GB, 500107862016 bytes Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes Disk /dev/sdc: 500.1 GB, 500107862016 bytes Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes ================================================================= Disk /dev/sda: 500.1 GB, 500107862016 bytes

Hi all, After rebooting my CentOS 5.5 server, i have the following message: ================================== Red Hat nash version 5.1.19.6 starting EXT3-fs: unable to read superblock mount: error mounting /dev/root on /sysroot as ext3: invalid argument setuproot: moving /root failed: No such file or directory setuproot: error mounting /proc: No such file or directory setuproot: error mounting

Yes, I tried to dd the mbr.bin and use both --install and --stupid parameters. The FAT32 partition is bootable. Here is what I did: $ sudo fdisk /dev/sda -l Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal):

<!-- @page { size: 8.5in 11in; margin: 0.79in } P { margin-bottom: 0.08in } --> I'm having a problem mounting my new CDRW DVD in my new machine I just built. The motherboard is an Intel DP35DP, and I connected the CDRW DVD via ribbon cable into the motherboard IDE slot. Centos 5.1 is installed and functioning fine so far (other than this problem). I can't mount the

Problem has been solved: "sudo mount -t iso9660 /dev/cdrom /mnt/cdrom -o" mounted the drive after adding "mount /mnt/cdrom" to /etc/festab. ----- Original Message ---- From: Pam Astor <pamastor at yahoo.com> To: centos at centos.org Sent: Monday, March 17, 2008 1:45:16 PM Subject: [CentOS] CDRW-DVD Mount Problem, Centos 5.1, Intel board... <!-- _filtered

> Yes, I tried to dd the mbr.bin and use both --install and --stupid parameters. > > The FAT32 partition is bootable. > > > Here is what I did: > > $ sudo fdisk /dev/sda -l > > Disk /dev/sda: 500.1 GB, 500107862016 bytes > 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size

My previous question: "can syslinux on a USBstik also boot installations on other USB devices ?" got no proper reply, so I'm now including more background detail. The new problem is that my 32bit partition of ETHOberon, only gives a proper font-size under Debian7:DVDinstaller:rescueMode, since I'm forced to use a laptop, after my previous systems were stolen. Neither gnome nor

Hi all I have a remote server (i.e SSH access only) which was incorrectly partitioned and I urgently need to get it up and running. It's got a 500GB HDD, but the PV is only 10GB big, so I can't add more LV's to to. P.S. This is on LVM, btw. [root at nd11176 ~]# fdisk -l /dev/sda Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders

it seems like I keep running into a wall. The present raid array...well let me do an fdisk -l: ---------------------------------------- Disk /dev/hda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux

Hi Folks, I've inherited an old RH7 system that I'd like to upgrade to CentOS6.1 by means of wiping it clean and doing a fresh install. However, the system has a software raid setup that I wish to keep untouched as it has data on that I must keep. Or at the very least, TRY to keep. If all else fails, then so be it and I'll just recreate the thing. I do plan on backing up

Hi, I have a custom linux system that runs off a FAT32 usb flash disk. I use syslinux to make it bootable and load the kernel. I'm trying to boot now from a SSD SATA disk (500GB) but it's not working and I can't figure out why. BIOS show that no bootable disk were found. What I already tried (linux fdisk): 1- Creating a new DOS partition table on the SSD, a FAT32 (type b), and

Somewhere, mdadm is cacheing information. Here is my /etc/mdadm.conf file: more /etc/mdadm.conf # mdadm.conf written out by anaconda DEVICE partitions MAILADDR root ARRAY /dev/md0 level=raid1 num-devices=4 metadata=0.90 UUID=55ff58b2:0abb5bad:42911890:5950dfce ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=315eaf5c:776c85bd:5fa8189c:68a99382 ARRAY /dev/md2 level=raid1 num-devices=2

We're getting the below errors about once a day on a system we're trying to set up with RedHat 7.3. This has happened to multiple filesystems on multiple physical and logical disks (basically we've got 4 drives as 2 sets of RAID 1 arrays, details below). Until a week ago, this box was a high-volume IMAP server running RedHat 6.2 with uptimes in the 200-day range, so I don't

(Resend: message didn't show, was my original message too big? Posted one of the output files to a website to see) The point of RAID1 is to allow for continued uptime in a failure scenario. When I assemble servers with RAID1, I set up two HDDs to mirror each other, and test by booting from each drive individually to verify that it works. For the OS partitions, I use simple partitions and

I am trying to install CentOS 4.6 to a pair of 750GB hard drives. I can successfully install to either of the drives as a single drive, but when I try to use both drives and mirror the partitions, I start having problems. Anaconda crashes as it is trying to format the drives. This is what I'm trying to create: /dev/md0: 200MB, /boot /dev/md1: 2GB, swap /dev/md2: rest of the

Hi there, I have a system with the following: # fdisk -l Disk /dev/sda: 80.0 GB, 80000000000 bytes 255 heads, 63 sectors/track, 9726 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104391 83 Linux /dev/sda2 14 9471 75971385 83 Linux /dev/sda3

On 1/29/2015 7:21 PM, Jatin Davey wrote: > [root at localhost ~]# lspci | grep RAID > 05:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS-3 > 3108 [Invader] (rev 02) to get info out of those, you need to install MegaCli64 from LSI Logic, which has the ugliest command lines and output you've ever seen. I use the python script below, which I put in

On 2/16/2016 3:23 PM, Zube wrote: > Does anyone know what program can be used to query the RAID status > from the OS for an on-board LSI SAS 2308-4i? the 2308 isn't actually a megaraid, its a simple SAS HBA that has an optional raid mode IF its flashed with IR firmware... this only supports raid 0/1/10. I always(!) flash these with the IT firmware that turns them back into a

On 1/30/2015 9:44 AM, John R Pierce wrote: > On 1/29/2015 7:21 PM, Jatin Davey wrote: >> [root at localhost ~]# lspci | grep RAID >> 05:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS-3 >> 3108 [Invader] (rev 02) > > to get info out of those, you need to install MegaCli64 from LSI > Logic, which has the ugliest command lines and output you've

How can I mount an old LVM drive into a new system so I can view the old files? I want to mount it as /mnt/backup fdisk -l Disk /dev/sda: 160.0 GB, 160000000000 bytes 255 heads, 63 sectors/track, 19452 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104391 83 Linux /dev/sda2