Re: md driver - dropped disk still being used?
Sandra Escandor sescan...@evertz.com 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. The logs don't say that sdc is disabled. Apparently the array doesn't degrade and a rebuild is tried that fails when the kernel panics. Have you tried with a more recent kernel? -- html messages are obsolete -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/877h7etws9@yun.yagibdah.de
md driver - dropped disk still being used?
Question:
I would like to confirm if I am interpreting the kernel log correctly.
The situation is that there was I/O going on to the RAID and then one of
the disks drop out - then the whole system completely hangs after
recovery finishes. I expected that the RAID would still be usable with 3
out of 4 disks (since it's in RAID10 configuration). Also, is this a
known issue?
My interpretation is the following:
1. There was a RAID member disk communication error with device sdc
(starts from ata layer).
2. The raid10 module handles this and disables sdc, then says that it
will continue working 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 sdc was
supposed to have been removed by the raid10 module, right?).
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.
System info:
Kernel 2.6.32-5-amd64
mdadm 3.1.4
four member disk raid10 - using imsm metadata container
Kernel Log snippet:
Jul 8 14:48:06 ecs-1u kernel: [ 8200.901003] ata3.00: exception Emask
0x0 SAct 0x1ffc0 SErr 0x0 action 0x6 frozen
Jul 8 14:48:06 ecs-1u kernel: [ 8200.901052] ata3.00: failed command:
WRITE FPDMA QUEUED
Jul 8 14:48:06 ecs-1u kernel: [ 8200.901082] ata3.00: cmd
61/00:30:80:37:3f/04:00:44:00:00/40 tag 6 ncq 524288 out
Jul 8 14:48:06 ecs-1u kernel: [ 8200.901083] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 8 14:48:06 ecs-1u kernel: [ 8200.901163] ata3.00: status: { DRDY }
Jul 8 14:48:06 ecs-1u kernel: [ 8200.901183] ata3.00: failed command:
WRITE FPDMA QUEUED
Jul 8 14:48:06 ecs-1u kernel: [ 8200.901207] ata3.00: cmd
61/00:38:80:3b:3f/04:00:44:00:00/40 tag 7 ncq 524288 out
Jul 8 14:48:06 ecs-1u kernel: [ 8200.901208] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 8 14:48:06 ecs-1u kernel: [ 8200.901282] ata3.00: status: { DRDY }
repeats...
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699104] sd 2:0:0:0: [sdc]
Unhandled error code
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699107] sd 2:0:0:0: [sdc] Result:
hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699110] sd 2:0:0:0: [sdc] CDB:
Write(10): 2a 00 3e cf 18 00 00 04 00 00
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699117] end_request: I/O error,
dev sdc, sector 1053759488
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699144] raid10: Disk failure on
sdc, disabling device.
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699144] raid10: Operation
continuing on 3 devices.
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699301] sd 2:0:0:0: [sdc]
Unhandled error code
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699303] sd 2:0:0:0: [sdc] Result:
hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699306] sd 2:0:0:0: [sdc] CDB:
Write(10): 2a 00 3e cf 1c 00 00 04 00 00
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699311] end_request: I/O error,
dev sdc, sector 1053760512
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699430] sd 2:0:0:0: [sdc]
Unhandled error code
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699431] sd 2:0:0:0: [sdc] Result:
hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699434] sd 2:0:0:0: [sdc] CDB:
Write(10): 2a 00 3e cf 20 00 00 04 00 00
Jul 8 14:57:19 ecs-1u kernel: [ 8753.699439] end_request: I/O error,
dev sdc, sector 1053761536
repeats...
Jul 8 14:57:23 ecs-1u kernel: [ 8758.163655] md: recovery of RAID array
md126
Jul 8 14:57:23 ecs-1u kernel: [ 8758.163660] md: minimum _guaranteed_
speed: 1000 KB/sec/disk.
Jul 8 14:57:23 ecs-1u kernel: [ 8758.163662] md: using maximum
available idle IO bandwidth (but not more than 20 KB/sec) for
recovery.
Jul 8 14:57:23 ecs-1u kernel: [ 8758.163672] md: using 128k window,
over a total of 732572288 blocks.
Jul 8 14:57:23 ecs-1u kernel: [ 8758.163675] md: resuming recovery of
md126 from checkpoint.
Jul 8 14:57:23 ecs-1u kernel: [ 8758.163677] md: md126: recovery done.
Jul 8 14:57:23 ecs-1u kernel: [ 8758.296414] RAID10 conf printout:
Jul 8 14:57:23 ecs-1u kernel: [ 8758.296416] --- wd:3 rd:4
Jul 8 14:57:23 ecs-1u kernel: [ 8758.296417] disk 0, wo:0, o:1,
dev:sdb
Jul 8 14:57:23 ecs-1u kernel: [ 8758.296419] disk 1, wo:1, o:0,
dev:sdc
Jul 8 14:57:23 ecs-1u kernel: [ 8758.296420] disk 2, wo:0, o:1,
dev:sdd
Jul 8 14:57:23 ecs-1u kernel: [ 8758.296421] disk 3, wo:0, o:1,
dev:sde
Jul 8 14:57:23 ecs-1u kernel: [ 8758.296673] md: recovery of RAID array
md126
Jul 8 14:57:23 ecs-1u kernel: [ 8758.296676] md: minimum _guaranteed_
speed: 1000 KB/sec/disk.
Jul 8 14:57:23 ecs-1u kernel: [ 8758.296679] md: using maximum
available idle IO bandwidth (but not more than 20 KB/sec) for
recovery.
Jul
Re: md driver?
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 it how do I remove it in the kernel? As noted by others that is the software raid (multiple device) driver. Which makes me think you are using a bootstrapping kernel which has everything built in. In which case you might consider updating to a tuned kernel for your hardware. The tuned kernels implement most device drivers as modules. apt-cache search kernel-image Updating from the bootstrapping kernel to a tuned kernel is slightly more complex than the typical package install. If seeing the md driver noise at boot is your only complaint then I would not upgrade. Bob msg23476/pgp0.pgp Description: PGP signature
md driver?
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 subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: md driver?
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 how do I remove it in the kernel? According to the kernel docs, its software RAID. If you don't need it and its a module, rmmod it, else change kernel. -- Seneca [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: md driver?
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? Multiple-disk device driver. I know it handles the kernel's software RAID implementation, and I suspect that LVM is based off of it also. It's one of those things where if you don't know what it is, you almost certainly don't need it... -- The freedoms that we enjoy presently are the most important victories of the White Hats over the past several millennia, and it is vitally important that we don't give them up now, only because we are frightened. - Eolake Stobblehouse (http://stobblehouse.com/text/battle.html) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: K7S5a md driver, Debian 2.2R6 problems
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, 184 pin It keeps locking constistantly at this point Do you have any suggestions? Since you asked for a suggestion and not a(n outright) solution, here goes. Is this an ECS board? Get a kernel with SIS chipset support enabled. You probably can't do this with the installer you now have. You might need to build a custom one using your other computer. I have been using Debian since the MAY 25,2000 Beta have never seen a problem quite like this before FUD Yes, the SIS-based boards are quite amazing. /FUD -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: K7S5a md driver, Debian 2.2R6 problems
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 (version 0.36.6 ). The DDR chip is the CE POWMEM 512MB 266MHZ, 184 pin It keeps locking constistantly at this point Do you have any suggestions? Since you asked for a suggestion and not a(n outright) solution, here goes. Is this an ECS board? Get a kernel with SIS chipset support enabled. You probably can't do this with the installer you now have. You might need to build a custom one using your other computer. I have been using Debian since the MAY 25,2000 Beta have never seen a problem quite like this before FUD Yes, the SIS-based boards are quite amazing. /FUD My wife's PC has been using the same model board (don't know what rev), but with a 512MB SDRAM chip for 4 months with no problems. Used the idepci kernel to install with, and now run a custom 2.4.17 kernel. -- +-+ | Ron Johnson, Jr.Home: [EMAIL PROTECTED] | | Jefferson, LA USA http://ronandheather.dhs.org:81 | | | | Object-oriented programming is an exceptionally bad idea | | which could only have originated in California. | | --Edsger Dijkstra | +-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
K7S5a md driver, Debian 2.2R6 problems
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 constistantly at this point Do you have any suggestions? I was not able to find any messages with problems other than with the onboard soud card networking card MAX_MD_DEV=4, MAX_REAL=8 is the last line before it locks hard must be rebooted. I have been using Debian since the MAY 25,2000 Beta have never seen a problem quite like this before Thanks, Lester -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
md driver problem
Hi all! I've been trying to install Linux (Suse, Debian, RedHat...) in a Pentium MMX 200 with 3 hard disks and a cdrom, but with either distribution, the boot-up process hangs up in the same place (never mind whether started from DOS boot disk, Linux boot disk, cdrom...). This is the output I get: hda: Maxtor 90432D3, 4121MB w/256 cache, CHS=8374/16/63 hdb: SAMSUNG WINNER-3 WN32543A(2.5GB), 2423MB w/109kB cache, CHS=4924/16/63 hdc: ST3290A, 249MB w/64kB cache, CHS=1001/15/34 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 floppy0: no floppy controllers found md driver 0.35 MAX_MD_DEV=4, MAX_REAL=8 Of course I've got a floppy disk controller. I've tried disabling it but the results are the same. I would appreciate any help because now I've been trying to install linux in this computer for almost six months and in the meanwhile I have to use linux on a 386. Please help me Regards
Re: md driver problem
hello Rodrigo: I've never seen problems with a floppy before. Thats a good one. Try booting a DOS floppy if you can to see what happens. Try resetting the CMOS to the manufacturers defaults. You may also try removing the two hard drives on your second IDE chain for the install. You can reconnect and initialize them once your up and running. First - check your physical connections. You never know, something may have shaken loose. Assuming the FD controller is on the motherboard, you may want to go to the manufacturer web site as see if there is a firmware update Peter. Rodrigo Moya wrote: Hi all! I've been trying to install Linux (Suse, Debian, RedHat...) in a Pentium MMX 200 with 3 hard disks and a cdrom, but with either distribution, the boot-up process hangs up in the same place (never mind whether started from DOS boot disk, Linux boot disk, cdrom...). This is the output I get: hda: Maxtor 90432D3, 4121MB w/256 cache, CHS=8374/16/63 hdb: SAMSUNG WINNER-3 WN32543A(2.5GB), 2423MB w/109kB cache, CHS=4924/16/63 hdc: ST3290A, 249MB w/64kB cache, CHS=1001/15/34 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 floppy0: no floppy controllers found md driver 0.35 MAX_MD_DEV=4, MAX_REAL=8 Of course I've got a floppy disk controller. I've tried disabling it but the results are the same. I would appreciate any help because now I've been trying to install linux in this computer for almost six months and in the meanwhile I have to use linux on a 386. Please help me Regards -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null begin:vcard n:Iannarelli;Peter tel;fax:1+416-929-1056 tel;work:1+416-929-1885 x-mozilla-html:FALSE url:http://www.genxl.com org:GenX Internte Labs;Operations adr:;;20 Madison Ave.;Toronto;ON;M5R 2S1;CA version:2.1 email;internet:Peter.Iannarelli title:Engineer x-mozilla-cpt:;0 fn:Peter Iannarelli end:vcard
FW: md driver problem
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 List Subject: Re: md driver problem hello Rodrigo: I've never seen problems with a floppy before. Thats a good one. Try booting a DOS floppy if you can to see what happens. Try resetting the CMOS to the manufacturers defaults. You may also try removing the two hard drives on your second IDE chain for the install. You can reconnect and initialize them once your up and running. First - check your physical connections. You never know, something may have shaken loose. Assuming the FD controller is on the motherboard, you may want to go to the manufacturer web site as see if there is a firmware update Peter. Rodrigo Moya wrote: Hi all! I've been trying to install Linux (Suse, Debian, RedHat...) in a Pentium MMX 200 with 3 hard disks and a cdrom, but with either distribution, the boot-up process hangs up in the same place (never mind whether started from DOS boot disk, Linux boot disk, cdrom...). This is the output I get: hda: Maxtor 90432D3, 4121MB w/256 cache, CHS=8374/16/63 hdb: SAMSUNG WINNER-3 WN32543A(2.5GB), 2423MB w/109kB cache, CHS=4924/16/63 hdc: ST3290A, 249MB w/64kB cache, CHS=1001/15/34 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 floppy0: no floppy controllers found md driver 0.35 MAX_MD_DEV=4, MAX_REAL=8 Of course I've got a floppy disk controller. I've tried disabling it but the results are the same. I would appreciate any help because now I've been trying to install linux in this computer for almost six months and in the meanwhile I have to use linux on a 386. Please help me Regards -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null begin:vcard n:Iannarelli;Peter tel;fax:1+416-929-1056 tel;work:1+416-929-1885 x-mozilla-html:FALSE url:http://www.genxl.com org:GenX Internte Labs;Operations adr:;;20 Madison Ave.;Toronto;ON;M5R 2S1;CA version:2.1 email;internet:Peter.Iannarelli title:Engineer x-mozilla-cpt:;0 fn:Peter Iannarelli end:vcard
Re: FW: md driver problem
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- From: Peter Iannarelli [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 28, 1998 11:28 AM To: Rodrigo Moya Cc: Debian User List Subject: Re: md driver problem hello Rodrigo: I've never seen problems with a floppy before. Thats a good one. Try booting a DOS floppy if you can to see what happens. Try resetting the CMOS to the manufacturers defaults. You may also try removing the two hard drives on your second IDE chain for the install. You can reconnect and initialize them once your up and running. First - check your physical connections. You never know, something may have shaken loose. Assuming the FD controller is on the motherboard, you may want to go to the manufacturer web site as see if there is a firmware update Peter. Rodrigo Moya wrote: Hi all! I've been trying to install Linux (Suse, Debian, RedHat...) in a Pentium MMX 200 with 3 hard disks and a cdrom, but with either distribution, the boot-up process hangs up in the same place (never mind whether started from DOS boot disk, Linux boot disk, cdrom...). This is the output I get: hda: Maxtor 90432D3, 4121MB w/256 cache, CHS=8374/16/63 hdb: SAMSUNG WINNER-3 WN32543A(2.5GB), 2423MB w/109kB cache, CHS=4924/16/63 hdc: ST3290A, 249MB w/64kB cache, CHS=1001/15/34 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 floppy0: no floppy controllers found md driver 0.35 MAX_MD_DEV=4, MAX_REAL=8 Of course I've got a floppy disk controller. I've tried disabling it but the results are the same. I would appreciate any help because now I've been trying to install linux in this computer for almost six months and in the meanwhile I have to use linux on a 386. Please help me Regards -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null begin:vcard n:Iannarelli;Peter tel;fax:1+416-929-1056 tel;work:1+416-929-1885 x-mozilla-html:FALSE url:http://www.genxl.com org:GenX Internte Labs;Operations adr:;;20 Madison Ave.;Toronto;ON;M5R 2S1;CA version:2.1 email;internet:Peter.Iannarelli title:Engineer x-mozilla-cpt:;0 fn:Peter Iannarelli end:vcard
Re: md driver problem
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 manufacturers defaults. You may also try removing the two hard drives on your second IDE chain for the install. You can reconnect and initialize them once your up and running. Well, now I've got four disks, but before I had only one and the CD and the results were worst, since the installation process used to stop after detecting the disks. Assuming the FD controller is on the motherboard, you may want to go to the manufacturer web site as see if there is a firmware update What do you mean by firmware update? Thanks very much
Re: md driver problem
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
Re: FW: md driver problem
I think md is for the ramdisk. how much memory is available ? I've got 64MB of memory Thanks
Re: FW: md driver problem
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:vcard n:Iannarelli;Peter tel;fax:1+416-929-1056 tel;work:1+416-929-1885 x-mozilla-html:FALSE url:http://www.genxl.com org:GenX Internte Labs;Operations adr:;;20 Madison Ave.;Toronto;ON;M5R 2S1;CA version:2.1 email;internet:Peter.Iannarelli title:Engineer x-mozilla-cpt:;0 fn:Peter Iannarelli end:vcard
Re: md driver problem
The Multiple-Device-Driver for HD-Mirroring and Striping So, what does this mean? What should I change in the BIOS or wherever?
Re: FW: md driver problem
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:[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)
Re: md driver
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 concepto -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
re: md driver
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 --- (_)/ (_)Lo importante es el concepto -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
md driver
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) | | /dev/md0 /dev/sdb1 is a 4.0G (whole drive) | | /dev/sdc1 is a 2.0G (whole drive)/ then i do the following /sbin/mdadd /dev/md0 /dev/hda4 /dev/sda1 /dev/sdb1 /dev/sdc1 /sbin/mdrun -pl -c4k /dev/md0 /sbin/mkfs.ext2 -c /dev/md0 When it finishes it says that block 49 is bad and that 1 - 55 must be good to make a filesystem. All drives will format by them selves. 3 months ago I put this machine together and it worked then. anyone have any ideas ? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: md driver
/dev/hda4 is a 3.3G linux partition \ /dev/sda1 is a 4.0G (whole drive) | /dev/sdb1 is a 4.0G (whole drive) | /dev/sdc1 is a 2.0G (whole drive)/ I don't have the documents right here, but are you sure that the md drive can handle 13.3 GB partition? 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://casal.upc.es/~pere/ PGP key available --- (_)/ (_)Lo importante es el concepto -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
