[Harry Zink]
> [root@gate Backup]# raidstop /dev/md0
> /dev/md0: Device or resource busy
>
> (This is normal, the fs is shared by atalk. I disable atalk)
>
> [root@gate Backup]# raidstop /dev/md0
> /dev/md0: Device or resource busy
>
> (Now this is no longer normal. No services or anything else
on 5/10/00 4:25 PM, Gregory Leblanc at [EMAIL PROTECTED] wrote:
>> You mean, reboot and at the lilo prompt type in 'linux single'?
>
> Yep, that's what I mean.
Made no difference.
Here's a dump from my dmesg at startup, though, maybe that can shed some
light. From what I can see, md tries to g
I have been suffering with gaps in email delivery from outside sources due
to continuing after-effects of the infamous "love bug" (gotta love NT mail
servers). I don't know if any responses to this have been posted since last
night (I had to grab this from a web archive just to read and respond t
> -Original Message-
> From: Harry Zink [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 10, 2000 4:20 PM
> To: Gregory Leblanc; [EMAIL PROTECTED]
> Subject: Re: md0 won't let go...
>
>
> on 5/10/00 3:59 PM, Gregory Leblanc at [EMAIL PROTECTED] wrote:
>
> > ok, stupid questions. Try '
Does Ingo, the author of the 0.90 RAID patches that I used read and
participate on this list? My e-mail to him at the last known address has,
not surprisingly, bounced.
Harry <-- Things there ought to be a central e-mail depository for kernel
maintainer e-mails...
on 5/10/00 3:59 PM, Gregory Leblanc at [EMAIL PROTECTED] wrote:
> ok, stupid questions. Try 'umount /dev/md0' then 'raidstop /dev/md0' and
> then 'fdisk /dev/hdX'.
[root@gate /root]# umount /dev/md0
[root@gate /root]# raidstop /dev/md0
[root@gate /root]# fdisk /dev/hdl
Unable to open /dev/hdl
on 5/10/00 4:02 PM, Mr. James W. Laferriere at [EMAIL PROTECTED]
wrote:
> Hello Harry, I probably missed this in the earlier flurry
> but which kermel version are you using & which raid patches ?
kernel 2.2.15
ide patches for 2.2.15
raid patches 0.90
http://people.redhat.com/mingo/raid-patches/r
Hello Harry, I probably missed this in the earlier flurry
but which kermel version are you using & which raid patches ?
Tia, JimL
On Wed, 10 May 2000, Harry Zink wrote:
> on 5/10/00 3:32 PM, James Manning at [EMAIL PROTECTED] wrote:
> > Are you claiming that /pro
on 5/10/00 4:56 PM, Michael at [EMAIL PROTECTED] wrote:
> Take a look in /proc/ide for the devices that the
> kernel found on startup.
drivers hdg hdj ide0 ide4
hda hdh hdl ide1 ide5
hdc hdi hpt366ide3 pdc202xx
The right drives are
> -Original Message-
> From: Harry Zink [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 10, 2000 3:46 PM
> To: James Manning
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: md0 won't let go...
>
> on 5/10/00 3:32 PM, James Manning at [EMAIL PROTECTED] wrote:
>
> > Are you cla
> on 5/10/00 2:08 PM, Gregory Leblanc at [EMAIL PROTECTED]
> wrote:
>
> > That is a correct error message, and has nothing to do with RAID. You can't
> > run fdisk on /dev/hdx1, you have to run fdisk on /dev/hdx
>
> Sorry, my bad in transcribing the error message.
>
> I tried to fdisk /dev/hdx
on 5/10/00 3:32 PM, James Manning at [EMAIL PROTECTED] wrote:
> Are you claiming that /proc/mdstat has the md0 active both before and
> after running raidstop /dev/md0? Just want to clarify.
Thus, to answer this question, yes, since it won't let me stop the RAID, I
keep getting the same /proc i
on 5/10/00 3:32 PM, James Manning at [EMAIL PROTECTED] wrote:
> Are you claiming that /proc/mdstat has the md0 active both before and
> after running raidstop /dev/md0? Just want to clarify.
[root@gate Backup]# raidstart -a
/dev/md0: File exists
[root@gate Backup]# raidstop /dev/md0
/dev/md0:
on 5/10/00 3:29 PM, Gregory Leblanc at [EMAIL PROTECTED] wrote:
> Changing the partition type from fd to something else
> should prevent those disks from getting included in any RAID autostart.
That's just it - these drives do not have an partitions set to fd. I'm
trying to use fdisk precisely s
[Harry Zink]
> on 5/10/00 2:30 PM, [EMAIL PROTECTED] at [EMAIL PROTECTED]
> wrote:
> > You probably need to do a 'raidstop' on md0. Then, maybe you can
> > fdisk it?
>
> Been there, done that.
> Makes no difference. It just very persistently holds on to these drives.
Are you claiming that /proc
On Wed, 10 May 2000, Dave Meythaler wrote:
> I was doing some testing earlier this week on RedHat 6.2 (2.2.14-5
> recompiled w/o raid modules) using /boot RAID-1 (two disks, hda and hdc) and
> saw what sounds like the same problem discussed here.
>
> With hda unplugged, I would get 0x80 errors
> -Original Message-
> From: Harry Zink [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 10, 2000 3:27 PM
> To: Gregory Leblanc; [EMAIL PROTECTED]
> Subject: Re: md0 won't let go...
>
> on 5/10/00 3:00 PM, Gregory Leblanc at [EMAIL PROTECTED] wrote:
>
> > D'oh! Are you sure that you ha
on 5/10/00 3:00 PM, Gregory Leblanc at [EMAIL PROTECTED] wrote:
> D'oh! Are you sure that you have the device entries correct?
Yes, I have checked that multiple times. In fact, just to be sure I also
inspected it using webmin, which has as a nice feature to ONLY show
available drives in its fdi
> -Original Message-
> From: Harry Zink [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 10, 2000 2:56 PM
> To: Gregory Leblanc; [EMAIL PROTECTED]
> Subject: Re: md0 won't let go...
>
>
> on 5/10/00 2:08 PM, Gregory Leblanc at [EMAIL PROTECTED] wrote:
>
> > That is a correct error mess
on 5/10/00 2:30 PM, [EMAIL PROTECTED] at [EMAIL PROTECTED]
wrote:
> You probably need to do a 'raidstop' on md0. Then, maybe you can
> fdisk it?
Been there, done that.
Makes no difference. It just very persistently holds on to these drives.
Harry
on 5/10/00 2:13 PM, Theo Van Dinter at [EMAIL PROTECTED] wrote:
> what does "cat /proc/mdstat" say? do the drives appear in there somewhere?
cat /proc/mdstat
Personalities : [raid0]
read_ahead 1024 sectors
md0 : active raid0 hdh1[1] hdg1[0] 19806976 blocks 16k chunks
unused devices:
on 5/10/00 2:08 PM, Gregory Leblanc at [EMAIL PROTECTED] wrote:
> That is a correct error message, and has nothing to do with RAID. You can't
> run fdisk on /dev/hdx1, you have to run fdisk on /dev/hdx
Sorry, my bad in transcribing the error message.
I tried to fdisk /dev/hdx
And the error I
> -Original Message-
> From: Harry Zink [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 10, 2000 2:00 PM
> To: [EMAIL PROTECTED]
> Subject: md0 won't let go...
>
> Problem: I compiled RAID patches properly into the recent
> 2.2.15 kernel. I
> have TWO IDE controllers (Promise & HPT366)
Problem: I compiled RAID patches properly into the recent 2.2.15 kernel. I
have TWO IDE controllers (Promise & HPT366). 2 drives attached to the HPT366
(10.1 gb IBMs), 3 drives attached to the Promise (3 x IBM 25.1 gb).
I successfully created /dev/md0 with the 2 x 10.1 gb drives.
When ataching
I was doing some testing earlier this week on RedHat 6.2 (2.2.14-5
recompiled w/o raid modules) using /boot RAID-1 (two disks, hda and hdc) and
saw what sounds like the same problem discussed here.
With hda unplugged, I would get 0x80 errors in lilo and was unable to boot
except by floppy.
I f
On Wed, 10 May 2000, Martin Munt wrote:
> Rich/Chance,
>
> I had EXACTLY the same problem. This post prompted me to fix it.
> Thanks a lot.
[ ... ]
I followed Richard Bollinger's advice, reordering the disks in my root
RAID-1 then rerunning lilo. With sda1 now raid-disk 0 and
Rich/Chance,
I had EXACTLY the same problem. This post prompted me to fix it.
Thanks a lot.
My setup is basic Redhat 6.0 but with clean 2.2.14 kernel sources,
mingo's 2.2.14-B1 patch & raidtools-19990824-0_90_tar.gz. After an
unsuccessful attempt t
27 matches
Mail list logo
