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

Re: / on raid1



On Fri, 17 May 2002, Alvin Oga wrote:

> hi ya karoly...

hi & thx for the help,

> did you try "raidsetfaulty" ?
> 	raidsetfaulty /dev/md0 /dev/hda1
> 	raidhotremove /dev/md0 /dev/hda1

~ # raidsetfaulty /dev/md1 /dev/hda1
~ # raidhotremove /dev/md1 /dev/hda1
/dev/md1: can not hot-remove disk: disk not in array!
~ #

> what does your lilo.conf look like ??

at the moment i have boot=/dev/hda, that i can boot at least from the
harddrive, but when i booted from floppy (as i wrote from in my other
mail) even then i couldn't raidhotadd /dev/hda1, 'cause it had active
inodes, according to log. how could it have active inodes, when it was set
to failed dik in the raidtab, and i booted from floppy?



~ # cat /etc/lilo.conf
disk    = /dev/hda
  bios  = 0x80
disk    = /dev/hdb
  bios  = 0x81
disk    = /dev/sda
  bios  = 0x82
boot    = /dev/hda
change-rules
reset
read-only
menu-scheme = Wg:kw:Wg:Wg
lba32
prompt
timeout = 80
message = /boot/message
default=withoutMTRR

  image  = /boot/memtest.bin
  label  = memtest86

 image=/boot/2418-charlie
        label=withoutMTRR
~ #

the lilo.conf.raid what i would like to use, looks like:

~ # cat /etc/lilo.conf.raid
# lilo.conf.hda - primary ide master
        disk=/dev/md1
        bios=0x80
        sectors=63
        heads=255
        cylinders=2491
        partition=/dev/md3
        start=63
        map=/boot/map
        install=/boot/boot.b
        image=/boot/2418-charlie
        root=/dev/hda1
        boot=/dev/hda
        read-only
        label=LinuxRaid
~ # lilo -C /etc/lilo.conf.raid
Warning: LBA32 addressing assumed
Device 0x0301: Partition type 0xFD does not seem suitable for a LILO boot
sector
~ #

> 	- does it have initrd.gz in it ??
> 	- which kernel is in initrd.gz ??

i do not have initrd.

this is getting somewhat weird:

~ # cat /proc/mounts
/dev/root / ext2 rw 0 0
proc /proc proc rw 0 0
devpts /dev/pts devpts rw 0 0
/dev/sda3 /oradata ext2 rw 0 0
/dev/sda2 /orapps ext2 rw 0 0
/dev/md4 /opt ext2 rw 0 0
/dev/md3 /var ext2 rw 0 0
/dev/md2 /usr ext2 rw 0 0
/dev/md1 /mnt ext2 rw 0 0

~ # mount /dev/md1 /
~ # cat /proc/mounts
/dev/root / ext2 rw 0 0
proc /proc proc rw 0 0
devpts /dev/pts devpts rw 0 0
/dev/sda3 /oradata ext2 rw 0 0
/dev/sda2 /orapps ext2 rw 0 0
/dev/md4 /opt ext2 rw 0 0
/dev/md3 /var ext2 rw 0 0
/dev/md2 /usr ext2 rw 0 0
/dev/md1 /mnt ext2 rw 0 0
/dev/md1 / ext2 rw 0 0
~ # mount /dev/hda1 /
~ # mount /dev/hda2 /

and so on...

~ # mount
/dev/md1 on / type ext2 (rw)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw)
/dev/sda3 on /oradata type ext2 (rw)
/dev/sda2 on /orapps type ext2 (rw)
/dev/md4 on /opt type ext2 (rw)
/dev/md3 on /var type ext2 (rw)
/dev/md2 on /usr type ext2 (rw)
/dev/md1 on /mnt type ext2 (rw)
/dev/md1 on / type ext2 (rw)
/dev/hda1 on / type ext2 (rw)
/dev/hda2 on / type ext2 (rw)

?!?

something like this i haven't seen yet, and just can hope that im not
going to see anymore...

charlie

--
Vegh Karoly


-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: