Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Troubles with raidhotadd



Hello:

I am the last step away from having RAID-1, but the command:
'raidhotadd /dev/md0/ /dev/hda6' fails because hda6 has inodes busy
from booting using grub.  grub has a command line interface, so if in
the one place I see /dev/hda6 I replace that with /dev/md0, it doesn't
boot (kernel panic), saying it is unable to create dev/console.  I
tried to substitute /dev/hdc6, but that messes up the array itself, so
much so /proc no longer appears.

Here is a bit of data about my current attempts to configure the
system and its current status:

# df            
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/md0               6016568   3492336   2218600  62% /
/dev/hda1                15522      9560      5161  65% /boot
/dev/hda3               980340     16436    914104   2% /tmp
/dev/hda5               980308    627124    303388  68% /var
# mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90.00
  Creation Time : Sat Sep  6 15:04:56 2003
     Raid Level : raid1
     Array Size : 6109888 (5.83 GiB 6.26 GB)
    Device Size : 6109888 (5.83 GiB 6.26 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Sun Sep  7 18:33:10 2003
          State : dirty, no-errors
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0


    Number   Major   Minor   RaidDevice State
       0      22        6        0      active sync   /dev/hdc6
       1       0        0        1      faulty
           UUID : d77ccd49:017683f5:1fa1cf98:f9bb5bac
         Events : 0.43
# cat /etc/raidtab
raiddev /dev/md0
   raid-level       1
   nr-raid-disks    2
   nr-spare-disks   0
   persistent-superblock 1
   chunk-size        16
   device   /dev/hdc6
   raid-disk 0
   device   /dev/hda6
   raid-disk 1
# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system>	<mount point>	<type>	<options>		<dump>	<pass>
/dev/md0	/		fd	errors=remount-ro	0	1
/dev/hda2	none		swap	sw			0	0
proc		/proc		proc	defaults		0	0
/dev/fd0	/floppy		auto	user,noauto		0	0
/dev/cdrom	/cdrom		iso9660	ro,user,noauto		0	0
/dev/hda1	/boot	ext3	defaults			0	2
/dev/hda3	/tmp	ext3	defaults,rw,nosuid	0	2
/dev/hda5	/var	ext3	defaults

Permutations of grub tried, and failures to raidhotadd
root		(hd0,0)
kernel		/vmlinuz-2.4.20 root=/dev/hda6 ro
initrd		/initrd.img-2.4.20
savedefault
boot
failure: inodes busy, otherwise system is fine.

root		(hd0,0)
kernel		/vmlinuz-2.4.20 root=/dev/md0 ro
initrd		/initrd.img-2.4.20
savedefault
boot
failure: kernel panic

root		(hd0,0)
kernel		/vmlinuz-2.4.20 root=/dev/hdc6 ro
initrd		/initrd.img-2.4.20
savedefault
boot
failure: doesn't make /proc files, system gets to shell but is broken.


I tried to boot off of tomsrtbt-2.0.103, but that failed for my
system.  My system is old enough that bootable CDs have yet to work
for me (not sure why that is, or how to get around it).

Any ideas?  It is frustrating to be one command away from having
raid-1 working.

doug




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org