"Sandra Escandor" writes:
> So, to get more specific with my question: If the raid10 module has
> disabled sdc, why is there a kernel log message after recovery that
> still involves sdc - no one should be talking to sdc, correct? I've
> attached a kernel log snippet. I can post more if needed.
rking with 3 out of 4 devices.
3. md driver starts a recovery of the RAID (all four disks are still
physically in, but one has been disabled by the raid10 module).
4. After md driver says that the recovery is done, a kernel log message
shows that there is an unhandled error code from sdc (but sd
Lance Hoffmeyer <[EMAIL PROTECTED]> [2003-01-09 18:29:42 -0600]:
> During boot I keep getting:
>
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: could not lock [dev 08:01], zero-size? Marking faulty.
>
> What is this? If I determine I don't need i
On Thu, Jan 09, 2003 at 06:29:42PM -0600, Lance Hoffmeyer wrote:
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: could not lock [dev 08:01], zero-size? Marking faulty.
>
> What is this? If I determine I don't need it how do I
> remove it in the kernel?
Multipl
On Thu, Jan 09, 2003 at 06:29:42PM -0600, Lance Hoffmeyer wrote:
> During boot I keep getting:
>
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: could not lock [dev 08:01], zero-size? Marking faulty.
>
>
> What is this? If I determine I don't need it h
During boot I keep getting:
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: could not lock [dev 08:01], zero-size? Marking faulty.
What is this? If I determine I don't need it how do I
remove it in the kernel?
Lance
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
On Sun, 2002-06-16 at 14:49, csj wrote:
> On Sat, 15 Jun 2002 18:50:12 -0400
> lketter <[EMAIL PROTECTED]> wrote:
>
> > Have a K7S5A that is locking on the CDROM boot of disk 1. It
> > locks after the floppy detect when it starts to load the md driver
> >
On Sat, 15 Jun 2002 18:50:12 -0400
lketter <[EMAIL PROTECTED]> wrote:
> Have a K7S5A that is locking on the CDROM boot of disk 1. It
> locks after the floppy detect when it starts to load the md driver
> (version 0.36.6 ). The DDR chip is the CE POWMEM 512MB 266MHZ, 18
To whoever gets this;
Thanks for taking the time to read it.
Have a K7S5A that is locking on the CDROM boot of disk 1. It locks
after the floppy detect when it starts to load the md driver (version
0.36.6 ). The DDR chip is the CE POWMEM 512MB 266MHZ, 184 pin It
keeps locking
On Wed, 28 Oct 1998, Peter Iannarelli wrote:
: Hay all:
:
: I think md is for the ramdisk.
No, md is "Multiple Device Driver". Usually it's the NEXT driver that's
hanging, and that's almost always a SCSI driver.
--
Nathan Norman
MidcoNet 410 South Phillips Avenue Sioux Falls, SD
mailto:[E
>
> Hi, Peter,
>
> It doesn't seen to be a floppy problem but the md-driver seems to hang.
>
> Ciao
> Andreas Loosen
>
I think it's not an md problem but rather the next driver to be loaded
in the
kernel that used to be WD-7000 SCSI car
Hi
Some time back I had a problem with a mother board running linux.
Specifically, the kernel was not seeing the PS/2 mouse. The manufacturer
(tyan) had a new firmware version for that motherboard on their site.
I applied it an low and behold, the PS/2 mouse started working.
The BIOS/CMOS setting
>The Multiple-Device-Driver for HD-Mirroring and Striping
So, what does this mean? What should I change in the BIOS or wherever?
The Multiple-Device-Driver for HD-Mirroring and Striping
Ciao
Andreas Loosen
> -Original Message-
> From: Rodrigo Moya [mailto:Moya_Rodrigo/[EMAIL PROTECTED]
> Sent: Wednesday, October 28, 1998 11:45 AM
> To: [EMAIL PROTECTED]; debian-user@lists.debian.org
> Subject
Rodrigo
You certainly have lots of RAM.
Disconnect the two HDs on the 2nd IDE chain and try again.
Check the manufacturers WEB site for firmware updates.
Peter
Rodrigo Moya wrote:
> >I think md is for the ramdisk.
> >how much memory is available ?
> I've got 64MB of memory
>
> Thanks
begin:v
>I think md is for the ramdisk.
>how much memory is available ?
I've got 64MB of memory
Thanks
>It doesn't seen to be a floppy problem but the md-driver seems to hang.
Sorry for me being stupid, but what exactly is the MD-driver?
Thanks very much
>Try booting a DOS floppy if you can to see what happens.
I've been using all this time Windows on this computer, and the floppy works
perfectly well. Usually, I start the installation process by booting with a
DOS disk, and then executing boot.bat from the cd.
>Try resetting the CMOS to the manuf
Hay all:
I think md is for the ramdisk.
how much memory is available ?
Peter
Andreas Loosen wrote:
> Hi, Peter,
>
> It doesn't seen to be a floppy problem but the md-driver seems to hang.
>
> Ciao
> Andreas Loosen
>
> > -Original Message-
> >
Hi, Peter,
It doesn't seen to be a floppy problem but the md-driver seems to hang.
Ciao
Andreas Loosen
> -Original Message-
> From: Peter Iannarelli [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 28, 1998 11:28 AM
> To: Rodrigo Moya
> Cc: Debian User Li
> hdd: MATSHITA CR-585, ATAPI CDROM drive
> ide0 at 0x1f0-0x1ft,0x3f6 on irq14
> ide1 at 0x170-0x177, 0x376 on irq 15
> no cont in shutdown
> floppy0: FDC access conflict
> Floppy drive(s): fd0 is 1.44M
> trying to lock fdc while usage count = 0
>
irq14
ide1 at 0x170-0x177, 0x376 on irq 15
no cont in shutdown
floppy0: FDC access conflict
Floppy drive(s): fd0 is 1.44M
trying to lock fdc while usage count = 0
floppy0: no floppy controllers found
md driver 0.35 MAX_MD_DEV=4, MAX_REAL=8
Of course I've got a f
Hi!
If anybody sent replies to my reply about the re:, please send
them again. I accidentally deleted them.
Thanks.
Salutacions, Pere __o mailto:[EMAIL PROTECTED]
2:343/108.91 - _`\<;_ http://casal.upc.es/~pere/
PGP key available --- (_
>
> Have you ran badblocks on /dev/hda4 ?
Thats what was reporting the error
>
> Salutacions, Pere __o mailto:[EMAIL PROTECTED]
> 2:343/108.91 - _`\<;_ http://casal.upc.es/~pere/
> PGP key available --- (_)/ (_)"Lo importante es el conce
> 3 months ago I put this machine together and it worked then.
A reason for the md driver to be able to handle 13.3 GB
Have you ran badblocks on /dev/hda4 ?
Salutacions, Pere __o mailto:[EMAIL PROTECTED]
2:343/108.91 - _`\<;_ http://
I am having a problem with the md driver
/dev/hda1 is the boot partition 300M
/dev/hda2 is a 127M swap partition
/dev/hda3 is a 127M swap partition
/dev/hda4 is a 3.3G linux partition \
|
/dev/sda1 is a 4.0G (whole drive
26 matches
Mail list logo
