Converting Software to Hardware RAID
 

I have a server running RedHat9. Currently It Has Software RAID Partitions and I need to move them onto a Hardware Raid System. The Issue is that the existing install and information must remain intact and the server needs as little downtime as possible. I am a Windows Technician so I gave it a shot as it would be done in windows, 1) install RAID adapter drivers into current setup 2) Duplicate origional Disk to New Array using ghost and the "image all" switch 3) Remove origional disks and boot from array. But when attempted the Kernel panics
( Kernel panic: vfs: Unable to mount foot fs on 09:02 ) :Pengy:
Any Suggestions?
LuCiD

I have never done this myself, but do you know what your drive would be? (i.e. /dev/hda ) , I am guessing that you will need to change your /etc/lilo.conf file to reflect which drive is the boot drive. after you edit the lilo.conf file you have to type in "lilo" to apply the changes, I am not sure how to edit grub if that is what you are using but I would imagine it would be pretty much the same.

You could find out what device your new raid is by typing in "dmesg" and seeing what it listed it as when you booted up.

I am using Grub as my bootloader
The Source Disk(s) Is Attached to The Integrated Ide Controller (hda/hdb). The Destination Disk Is Attached to A Promise Fast Track s150tx4 Controller (sda)
I change the line in the bootloader from "hda" to "sda" with no results
Any Suggestions?
Thank You For Your Help
LuCiD

Here is a Readout from "dmesg":

Linux version 2.4.20-8 (bhcompile@stripples.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:18:24 EST 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
511MB LOWMEM available.
On node 0 totalpages: 131056
zone(0): 4096 pages.
zone(1): 126960 pages.
zone(2): 0 pages.
Kernel command line: ro root=/dev/md2 hdc=ide-scsi
ide_setup: hdc=ide-scsi
Initializing CPU#0
Detected 1674.498 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 3342.33 BogoMIPS
Memory: 511392k/524224k available (1312k kernel code, 10268k reserved, 996k data, 128k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After generic, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: Common caps: 0383fbff c1c3fbff 00000000 00000000
CPU: AMD Athlon(tm) XP 2000+ stepping 02
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xf9d60, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router default [1106/3189] at 00:00.0
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16)
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
pty: 2048 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS0 at 0x03f8 (irq = 4) is a 16550A
ttyS1 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
NET4: Frame Diverter 0.46
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00beta-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PDC20270: IDE controller at PCI slot 00:0d.0
PDC20270: chipset revision 2
PDC20270: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xb000-0xb007, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0xb008-0xb00f, BIOS settings: hdg:pio, hdh:pio
VP_IDE: IDE controller at PCI slot 00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci00:11.1
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:DMA, hdd:pio
hda: ST380011A, ATA DISK drive
hdb: ST380011A, ATA DISK drive
blk: queue c03be900, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c03bea44, I/O limit 4095Mb (mask 0xffffffff)
hdc: SONY CD-RW CRX195E1, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: host protected area => 1
hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(100)
hdb: host protected area => 1
hdb: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(100)
ide-floppy driver 0.99.newide
Partition check:
hda: hda1 hda2 hda3
hdb: hdb1 hdb2 hdb3
ide-floppy driver 0.99.newide
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
[events: 00000015]
[events: 00000015]
[events: 00000015]
[events: 00000015]
[events: 00000015]
[events: 00000015]
md: autorun ...
md: considering hdb3 ...
md: adding hdb3 ...
md: adding hda3 ...
md: created md2
md: bind<hda3,1>
md: bind<hdb3,2>
md: running: <hdb3><hda3>
md: hdb3's event counter: 00000015
md: hda3's event counter: 00000015
md: md2: raid array is not clean -- starting background reconstruction
md: RAID level 1 does not need chunksize! Continuing anyway.
kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2
md: personality 3 is not loaded!
md :do_md_run() returned -22
md: md2 stopped.
md: unbind<hdb3,1>
md: export_rdev(hdb3)
md: unbind<hda3,0>
md: export_rdev(hda3)
md: considering hdb2 ...
md: adding hdb2 ...
md: adding hda2 ...
md: created md1
md: bind<hda2,1>
md: bind<hdb2,2>
md: running: <hdb2><hda2>
md: hdb2's event counter: 00000015
md: hda2's event counter: 00000015
md: md1: raid array is not clean -- starting background reconstruction
md: RAID level 1 does not need chunksize! Continuing anyway.
kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2
md: personality 3 is not loaded!
md :do_md_run() returned -22
md: md1 stopped.
md: unbind<hdb2,1>
md: export_rdev(hdb2)
md: unbind<hda2,0>
md: export_rdev(hda2)
md: considering hdb1 ...
md: adding hdb1 ...
md: adding hda1 ...
md: created md0
md: bind<hda1,1>
md: bind<hdb1,2>
md: running: <hdb1><hda1>
md: hdb1's event counter: 00000015
md: hda1's event counter: 00000015
md: RAID level 1 does not need chunksize! Continuing anyway.
kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2
md: personality 3 is not loaded!
md :do_md_run() returned -22
md: md0 stopped.
md: unbind<hdb1,1>
md: export_rdev(hdb1)
md: unbind<hda1,0>
md: export_rdev(hda1)
md: ... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 154k freed
VFS: Mounted root (ext2 filesystem).
md: raid1 personality registered as nr 3
Journalled Block Device driver loaded
md: Autodetecting RAID arrays.
[events: 00000015]
[events: 00000015]
[events: 00000015]
[events: 00000015]
[events: 00000015]
[events: 00000015]
md: autorun ...
md: considering hda1 ...
md: adding hda1 ...
md: adding hdb1 ...
md: created md0
md: bind<hdb1,1>
md: bind<hda1,2>
md: running: <hda1><hdb1>
md: hda1's event counter: 00000015
md: hdb1's event counter: 00000015
md: RAID level 1 does not need chunksize! Continuing anyway.
md0: max total readahead window set to 124k
md0: 1 data-disks, max readahead per data-disk: 124k
raid1: device hda1 operational as mirror 0
raid1: device hdb1 operational as mirror 1
raid1: raid set md0 active with 2 out of 2 mirrors
md: updating md0 RAID superblock on device
md: hda1 [events: 00000016]<6>(write) hda1's sb offset: 104320
md: hdb1 [events: 00000016]<6>(write) hdb1's sb offset: 104320
md: considering hda2 ...
md: adding hda2 ...
md: adding hdb2 ...
md: created md1
md: bind<hdb2,1>
md: bind<hda2,2>
md: running: <hda2><hdb2>
md: hda2's event counter: 00000015
md: hdb2's event counter: 00000015
md: md1: raid array is not clean -- starting background reconstruction
md: RAID level 1 does not need chunksize! Continuing anyway.
md1: max total readahead window set to 124k
md1: 1 data-disks, max readahead per data-disk: 124k
raid1: device hda2 operational as mirror 0
raid1: device hdb2 operational as mirror 1
raid1: raid set md1 not clean; reconstructing mirrors
raid1: raid set md1 active with 2 out of 2 mirrors
md: updating md1 RAID superblock on device
md: hda2 [events: 00000016]<6>(write) hda2's sb offset: 1044160
md: syncing RAID array md1
md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.
md: using maximum available idle IO bandwith (but not more than 10000 KB/sec) for reconstruction.
md: using 124k window, over a total of 1044160 blocks.
md: hdb2 [events: 00000016]<6>(write) hdb2's sb offset: 1044160
md: considering hda3 ...
md: adding hda3 ...
md: adding hdb3 ...
md: created md2
md: bind<hdb3,1>
md: bind<hda3,2>
md: running: <hda3><hdb3>
md: hda3's event counter: 00000015
md: hdb3's event counter: 00000015
md: md2: raid array is not clean -- starting background reconstruction
md: RAID level 1 does not need chunksize! Continuing anyway.
md2: max total readahead window set to 124k
md2: 1 data-disks, max readahead per data-disk: 124k
raid1: device hda3 operational as mirror 0
raid1: device hdb3 operational as mirror 1
raid1: raid set md2 not clean; reconstructing mirrors
raid1: raid set md2 active with 2 out of 2 mirrors
md: updating md2 RAID superblock on device
md: hda3 [events: 00000016]<6>(write) hda3's sb offset: 76999424
md: delaying resync of md2 until md1 has finished resync (they share one or more physical units)
md: hdb3 [events: 00000016]<6>(write) hdb3's sb offset: 76999424
md: ... autorun DONE.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 128k freed
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
ehci-hcd 00:10.3: VIA Technologies, Inc. USB 2.0
ehci-hcd 00:10.3: irq 11, pci mem e084d000
usb.c: new USB bus registered, assigned bus number 1
PCI: 00:10.3 PCI cache line size set incorrectly (32 bytes) by BIOS/FW.
PCI: 00:10.3 PCI cache line size corrected to 64.
ehci-hcd 00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2003-Jan-22
hub.c: USB hub found
hub.c: 6 ports detected
usb-uhci.c: $Revision: 1.275 $ time 17:26:20 Mar 13 2003
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0xb400, IRQ 10
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: USB UHCI at I/O 0xb800, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: USB UHCI at I/O 0xbc00, IRQ 10
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 4
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,2), internal journal
Adding Swap: 1044152k swap-space (priority -1)
SCSI subsystem driver Revision: 1.00
PROMISE FastTrak TX4000/376/378/S150 TX Series Linux Driver Version 1.00.0.18
scsi0 : ft3xx
Vendor: Promise Model: 1X2 Mirror/RAID1 Rev: 1.10
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 234375000 512-byte hdwr sectors (120000 MB)
sda: sda1 sda2 sda3
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,0), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
scsi1 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: SONY Model: CD-RW CRX195E1 Rev: ZYS5
Type: CD-ROM ANSI SCSI revision: 02
parport0: PC-style at 0x378 [PCSPP,TRISTATE]
Attached scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
ip_tables: (C) 2000-2002 Netfilter core team
parport0: PC-style at 0x378 [PCSPP,TRISTATE]
lp0: using parport0 (polling).
lp0: console ready
md: md1: sync done.
md: syncing RAID array md2
md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.
md: using maximum available idle IO bandwith (but not more than 10000 KB/sec) for reconstruction.
md: using 124k window, over a total of 76999424 blocks.

Can you post your grub.conf file, (I think that is the name) so I can see what it looks like?

I just did a quick google search and came up with this article:

http://www.redhat.com/docs/manuals/l...e/ch-grub.html

I don't know if your using redhat or what but this is a pretty general grub guide, take a look and see if that will help you at all.

Well, try to find out what the new device is called and make sure that the kernel has support for what you're trying to do. Without the correct RAID drivers then it will be impossible.

EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,0), internal journal
EXT3-fs: mounted filesystem with ordered data mode.


If anyone would have paid attention to the posts question and the output of dmesg, youd notice something a little fishy no?

question was, upgraded RAID, why does the kernel panic and how do I fix it,.....

according to dmesg that he posted, the kernel doesnt seem to panick, and his filesystem is mounted on md wharetver, the same as it is, for his specified root device.

I guess I don't see a problem here and if in fact the kernel is panicking please include that part with dmesg output.

Holy snack pies!

"Can you post your grub.conf file, (I think that is the name) so I can see what it looks like?" -- cli_man

Yes, I will do so soon

"according to dmesg that he posted, the kernel doesnt seem to panick, and his filesystem is mounted on md wharetver, the same as it is, for his specified root device." -- AutOPSY

The readout is from the current (functional) software raid setup with the replacement disks and drivers installed. How do I recieve output from dmesg when the system does not complete bootup? :confused:

"Without the correct RAID drivers then it will be impossible." -- Pwnz3r

The drivers are tested and work on other machines with under similar conditions
download url: http://www.promise.com/support/downl...ry=driver&os=3

Thanks for all your help
LuCiD

Readout of grub.conf

# 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.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/md2
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-8)
root (hd0,0)
kernel /vmlinuz-2.4.20-8 ro root=/dev/md2 hdc=ide-scsi
initrd /initrd-2.4.20-8.img

Thank You For Your Time
Pete

#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-8)
root (hd0,0)
kernel /vmlinuz-2.4.20-8 ro root=/dev/md2 hdc=ide-scsi

I would make sure that the boot= portion is supposed to be commented out and that root=/dev/md2 is in fact your root device, for some situations I think you have to preload the drivers for that kernel, I dont know for surre but its called kernel module preloading.

EDIT: preload the drivers for that controller.

I think the magic edit is this, you said you changed the hdc to sda but did you change the /dev/md2? I did not see in dmesg what the device for sda is but you may find it by doing a "mount" command and see where sda is listed. I think once you get both of those it should work.

Got it to work!
 

Setup:
Source Drive = the software raid setup (/dev/hda)
Destination Drive = pre-partioned and formated with redhat minimal installation (/dev/sdb)
Pivot Point = possibly knoppix or minimal install with all drivers for mounting and copying files (/dev/sda)

(Convert Source Partitions)
#fdisk /dev/hda (0ption t)
(Default Setup (md0=/boot md1=swap md2=/)

partition 1 = 83 linux ext3
partition 2 = 82 linux swap
partition 3 = 83 linux ext3

#mkdir /mnt/hda3
#mkdir /mnt/sdb2

#mount -t ext3 /dev/hda3 /mnt/hda3
#mount -t ext3 /dev/sdb2 /mnt/sdb2

(save /mnt/sdb2/etc/fstab for later use)
#mkdir /home/temp
#cp -v /mnt/sdb2/etc/fstab /home/temp

(delete all files under /mnt/sdb2/*)
#rm -rfv /mnt/sdb2/*

#cp -av /mnt/hda3/* /mnt/sdb2

(delete etc/raidtab to erase software raid info)
#rm -v /mnt/sdb2/etc/raidtab

(replace /mnt/sdb2/etc/fstab with one saved in /home/temp)
#rm -v /mnt/sdb2/etc/fstab
#cp -iv /home/temp/* /mnt/sdb2/etc

:cry: