on 5/17/00 11:14 AM, Mr. James W. Laferriere at [EMAIL PROTECTED]
wrote:
> Hello Harry, I noticed that on the higher IDE controller(s) are
> alternating 'PIO' drives .
Actually, the way it turns out, the PIO slots are the ones without drives.
It switches to DMA when it detects if a drive is the
Hello Harry, I noticed that on the higher IDE controller(s) are
alternating 'PIO' drives . A suggestion , try placing these
drives on just one controller OR not using them entirely .
then try rebuilding using just the DMA capable ones .
Just a possibilit
[Harry Zink]
> While I appreciate the patch/diff provided by James Manning, I am extremely
> weary of applying anything to a system that I don't fully understand -
> particularly if it is suffixed by "Who knows..." (shiver).
I hadn't had a chance to test it... this one (attached) works (I had
for
On Wed, 17 May 2000, Harry Zink wrote:
> on 5/17/00 9:24 AM, Tommy at [EMAIL PROTECTED] wrote:
>
> > I mentioned in the email I sent last week that your problem was the dev,
> > and requested a ls -l of /dev/ to show you..
>
> ...and I appreciate the help you provided with that, but when I rece
> -Original Message-
> From: Harry Zink [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 17, 2000 9:10 AM
> To: m. allan noah; James Manning
> Cc: [EMAIL PROTECTED]
> Subject: Re: md0 won't let go... (dmesg dump...)
>
> on 5/17/00 8:30 AM, m. allan no
on 5/17/00 9:24 AM, Tommy at [EMAIL PROTECTED] wrote:
> I mentioned in the email I sent last week that your problem was the dev,
> and requested a ls -l of /dev/ to show you..
...and I appreciate the help you provided with that, but when I received
your mail, I had already taken the system down
On Wed, 17 May 2000, Harry Zink wrote:
> Thanks, and thanks to James Manning as well for finally tracking down what
> the core of this problem is.
>
> Is there some utility that will quickly and easily create /dev/ files and
> provides qualified questions to assist in properly creating /dev/ fil
on 5/17/00 8:30 AM, m. allan noah at [EMAIL PROTECTED] wrote:
> you obviously dont understand how device files work.
You are correct, that is one particular part of the opsys that is still
pretty much mystery to me.
Even reading through /usr/src/linux/Documentation/devices.txt makes it
pretty o
[Harry Zink]
> Not sure what this will help, except confirm again that these volumes aren't
> accessible, which was my question to start with.
question is "why?", answer is "no appropriate /dev entries"
> [root@gate src]# ls -l /dev/hdj1
> ls: /dev/hdj1: No such file or directory
> [root@gate sr
Harry Zink <[EMAIL PROTECTED]> said:
> on 5/17/00 7:21 AM, James Manning at [EMAIL PROTECTED] wrote:
>
> > ls -l /dev/hd[gk]* ... you make need a later MAKEDEV (or edit yours)
> > to create all the necessary files
>
> Not sure what this will help, except confirm again that these volumes aren't
on 5/17/00 7:21 AM, James Manning at [EMAIL PROTECTED] wrote:
> ls -l /dev/hd[gk]* ... you make need a later MAKEDEV (or edit yours)
> to create all the necessary files
Not sure what this will help, except confirm again that these volumes aren't
accessible, which was my question to start with.
[Harry Zink]
>Doing fdisk /dev/hdf works just fine.
>Doing fdisk /dev/hdg or /dev/hdk results in the old 'unable to open
>hdj/hdk'
ls -l /dev/hd[gk]* ... you make need a later MAKEDEV (or edit yours)
to create all the necessary files
>Alright, try turning off the RAID again ... r
ednesday, May 17, 2000 2:37 PM
> To: James Manning; Tommy; Harry Zink
> Cc: [EMAIL PROTECTED]
> Subject: Re: md0 won't let go... (dmesg dump...)
>
> I have scrapped the earlier configuration, and have rebuilt a kernel and
> tried this whole RAID ringmarole again.
>
Title: Re: md0 won't let go... (dmesg dump...)
I have scrapped the earlier configuration, and have rebuilt a kernel and tried this whole RAID ringmarole again. I am including mdstat, dmesg, and raidtab at the end.
Kernel 2.2.15
ide.2.2.15.2509.patch
raid-2.2.15-A0 (Mingo)
Com
on 5/11/00 1:11 PM, James Manning at [EMAIL PROTECTED] wrote:
> I'd think that, but he's still not put out the /proc/mdstat I asked for
> multiple times
---
on 5/10/00 2:13 PM in response to Theo Van Dinter at [EMAIL PROTECTED]:
> what does "cat /proc/mdstat" say? do the drives appear in th
[Tommy]
> When reading through this, my first impulse is to say that /dev/hdl isn't
> correct. When I recently built a raid5 using 3 promise cards, I found
> that in spite of the kernel detecting hdk hdm and hdo, these devices were
> NOT built in /dev. In fact, I had to dig into the ide header f
On Thu, 11 May 2000, Harry Zink wrote:
> on 5/11/00 10:11 AM, James Manning at [EMAIL PROTECTED] wrote:
>
> > fdisk to /dev/hdl would seem to be failing because there is no hdl device
>
> There *IS* an hdl device (as well as hdk and hdi), and they are properly
> recognized when the kernel recog
on 5/11/00 10:11 AM, James Manning at [EMAIL PROTECTED] wrote:
> fdisk to /dev/hdl would seem to be failing because there is no hdl device
There *IS* an hdl device (as well as hdk and hdi), and they are properly
recognized when the kernel recognizes the IDE cards.
Doens't matter anymore, I'm do
[Harry Zink]
> autorun ...
> considering hdh1 ...
> adding hdh1 ...
> adding hdg1 ...
> created md0
so hdh and hdg certainly both have partitions and bothare set to type fd
fdisk to /dev/hdl would seem to be failing because there is no hdl device
if you're trying to "free" hdg and/or hdh, f
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
20 matches
Mail list logo
