vinum problem
Hi all, I'm makara from Cambodia. I'm freebsd newbie. I try to configure vinum I always get this messages every time when I start vinum vinum: Inappropriate ioctl for device and a few minute later my pc is restart. I hope you can solv the problem. Thanks sorry for my english. - Start your day with Yahoo! - make it your home page ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vinum Problem
On Sun, 2005-03-27 at 16:59, Ean Kingston wrote: On March 27, 2005 10:35 am, Robert Slade wrote: Hi, I have managed to setup a vinum volume using 2 striped disks, the volume is created and I can do newfs on it and mount it. However, when I set start_vinum=YES in rc.conf, vinum loads then I get panic, followed by hanging vnode. I'm using 5.3. Any pointers please. In 5.3, you need to use gvinum instead of vinum. To do this set start_vinum=NO in /etc/rc.conf and set geom_vinum_load=YES in /boot/loader.conf. gvinum will read your vinum configuration just fine so you only need to make the changes I suggested to get it to work. Althought this is documented, it is not what I would call 'well documented' yet. Ean, Thank you, that got me further, I appears to have created a new /dev/gvinum/test, which seems to the right size, but when I mount it as /test, I get not a directory when I try and ls it. The mount point needs to exist prior to mounting a filesystem so, try something like this (as root): mkdir /test mount /dev/gvinum/test /test mount | grep test That last one should produce the following output, /dev/gvinum/test on /test (ufs, local, soft-updates) which indicates that you have a mounted filesystem on /test. I have tried to find documentation on geom, but that seems to be related to mirroring. Ya, documentation is still being worked on. For basic stuff (like creating concatinated volumes) you can use the vinum documentation and replace 'vinum' with 'gvinum' when you try things. Using your 'test' filesystem is a very good idea. Some aspects of vinum still aren't fully implemented in gvinum. Remember, if you just created your /test volume. It should be empty. You did run 'newfs /dev/gvinum/test' after creating it and before mouting it, right? -- Ean Kingston E-Mail: ean_AT_hedron_DOT_org PGP KeyID: 1024D/CBC5D6BB URL: http://www.hedron.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Vinum Problem
Hi, I have managed to setup a vinum volume using 2 striped disks, the volume is created and I can do newfs on it and mount it. However, when I set start_vinum=YES in rc.conf, vinum loads then I get panic, followed by hanging vnode. I'm using 5.3. Any pointers please. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vinum Problem
On March 27, 2005 10:35 am, Robert Slade wrote: Hi, I have managed to setup a vinum volume using 2 striped disks, the volume is created and I can do newfs on it and mount it. However, when I set start_vinum=YES in rc.conf, vinum loads then I get panic, followed by hanging vnode. I'm using 5.3. Any pointers please. In 5.3, you need to use gvinum instead of vinum. To do this set start_vinum=NO in /etc/rc.conf and set geom_vinum_load=YES in /boot/loader.conf. gvinum will read your vinum configuration just fine so you only need to make the changes I suggested to get it to work. Althought this is documented, it is not what I would call 'well documented' yet. -- Ean Kingston E-Mail: ean AT hedron DOT org URL: http://www.hedron.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vinum Problem
On Sun, 2005-03-27 at 16:59, Ean Kingston wrote: On March 27, 2005 10:35 am, Robert Slade wrote: Hi, I have managed to setup a vinum volume using 2 striped disks, the volume is created and I can do newfs on it and mount it. However, when I set start_vinum=YES in rc.conf, vinum loads then I get panic, followed by hanging vnode. I'm using 5.3. Any pointers please. In 5.3, you need to use gvinum instead of vinum. To do this set start_vinum=NO in /etc/rc.conf and set geom_vinum_load=YES in /boot/loader.conf. gvinum will read your vinum configuration just fine so you only need to make the changes I suggested to get it to work. Althought this is documented, it is not what I would call 'well documented' yet. Ean, Thank you, that got me further, I appears to have created a new /dev/gvinum/test, which seems to the right size, but when I mount it as /test, I get not a directory when I try and ls it. I have tried to find documentation on geom, but that seems to be related to mirroring. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Vinum Problem(?)
Hello, I have a really weird problem, I don't know if it is software or hardware related. When I am in the process of extracting a multivolume archive (rar) it goes on for a while, then stops, then continues and then all of the sudden the computer reboots. The volume which I try to extract files on is a Vinum volume containing 2 Western Digital 36gb SATA raptor disks (striped) connected via a Tekram TR822 SATA-controller. Upon reboot it complains about / not being properly unmounted, and fsck says something about SUPERBLK, or similar. - ws01-omi# vinum list 2 drives: D vinumdrive1 State: up /dev/ad6s1d A: 0/35299 MB (0%) D vinumdrive0 State: up /dev/ad4s1d A: 0/35299 MB (0%) 1 volumes: V hmState: up Plexes: 1 Size: 68 GB 1 plexes: P hm.p0 S State: up Subdisks: 2 Size: 68 GB 2 subdisks: S hm.p0.s0 State: up D: vinumdrive0 Size: 34 GB S hm.p0.s1 State: up D: vinumdrive1 Size: 34 GB -- Can this just be a h/w problem due to overheating? Even though the disks don't feel very varm on touch. I'm not completely sure what details might be needed, but heres my dmesg: -- Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2.1-RELEASE-p8 #7: Wed May 26 22:11:10 CEST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/omi Preloaded elf kernel /boot/kernel/kernel at 0xc084f000. Preloaded elf module /boot/kernel/snd_cmi.ko at 0xc084f26c. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc084f318. Preloaded elf module /boot/kernel/acpi.ko at 0xc084f3c4. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2558.53-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Stepping = 4 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 1073659904 (1023 MB) avail memory = 1033490432 (985 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P4B533 on motherboard pcibios: BIOS version 2.10 Using $PIR table, 10 entries at 0xc00f2400 acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 29 INTA is routed to irq 11 pcib0: slot 29 INTB is routed to irq 5 pcib0: slot 29 INTC is routed to irq 10 pcib0: slot 31 INTA is routed to irq 10 agp0: Intel 82845 host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib1: slot 0 INTA is routed to irq 11 pci1: display, VGA at device 0.0 (no driver attached) uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xd800-0xd81f irq 11 at device 29.0 on pci0 usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: Logitech product 0x08b4, rev 1.10/0.03, addr 2 uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0xd400-0xd41f irq 5 at device 29.1 on pci0 usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uscanner0: EPSON EPSON Scanner, rev 1.10/1.00, addr 2 uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0xd000-0xd01f irq 10 at device 29.2 on pci0 usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 29.7 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib2: slot 10 INTA is routed to irq 9 pcib2: slot 11 INTA is routed to irq 9 pcm0: CMedia CMI8738 port 0xb800-0xb8ff at device 3.0 on pci2 pcib2: slot 3 INTA is routed to irq 5 atapci0: SiI 3112 SATA150 controller port 0xa000-0xa00f,0xa400-0xa403,0xa800-0xa807,0xb000-0xb003,0xb400-0xb407 mem 0xed00-0xed0001ff irq 9 at device 10.0 on pci2 atapci0: [MPSAFE] ata2: at 0xed00 on atapci0 ata2: [MPSAFE] ata3: at 0xed00 on atapci0 ata3: [MPSAFE] xl0: 3Com 3c905C-TX Fast Etherlink XL port 0x9800-0x987f mem 0xec80-0xec80007f irq 9 at device 11.0 on pci2 xl0: Ethernet address: 00:04:75:c8:18:d8 miibus0: MII bus on xl0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci2: network at device
Re: Vinum Problem(?)
On Wednesday, 2 June 2004 at 11:55:37 +0200, Erik Mossberg wrote: Hello, I have a really weird problem, I don't know if it is software or hardware related. When I am in the process of extracting a multivolume archive (rar) it goes on for a while, then stops, then continues and then all of the sudden the computer reboots. The volume which I try to extract files on is a Vinum volume containing 2 Western Digital 36gb SATA raptor disks (striped) connected via a Tekram TR822 SATA-controller. Upon reboot it complains about / not being properly unmounted, and fsck says something about SUPERBLK, or similar. fsck is trying to tell you something. If you don't pay attention, it doesn't help much. Can this just be a h/w problem due to overheating? No idea. Do you get a panic, or just a spontaneous reboot? In any case, please read http://www.vinumvm.org/vinum/how-to-debug.html before submitting new information. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html Note: I discard all HTML mail unseen. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgpHm0zVdKMHx.pgp Description: PGP signature
Re: Grave vinum problem (at least for me)
On Thursday, 5 February 2004 at 6:48:18 +0100, Ole Voss wrote: Last night I reinstalled freebsd and obviously somewhere along the way my 400GB concat vinum volume wasn't unmounted (at least that's what freebsd told me). Now, when I run 'fsck -t ufs /dev/vinum/abyss' I get this: titan# fsck -t ufs /dev/vinum/abyss ** /dev/vinum/abyss CANNOT READ BLK: 843781344 CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 843781344, 843781345, 843781346, 843781347, /dev/vinum/abyss: CANNOT FIGURE OUT FILE SYSTEM PARTITION It mounted fine last night and everything looked perfect. Then I did a reboot and ... well, this is it now. Can anybody help me out? We need more information than this. This message alone could mean that one of your disks is defective, or that some component of the Vinum array is down. Take a look at http://www.vinumvm.org/vinum/how-to-debug.html and supply the info I ask for there. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
Grave vinum problem (at least for me)
Last night I reinstalled freebsd and obviously somewhere along the way my 400GB concat vinum volume wasn't unmounted (at least that's what freebsd told me). Now, when I run 'fsck -t ufs /dev/vinum/abyss' I get this: titan# fsck -t ufs /dev/vinum/abyss ** /dev/vinum/abyss CANNOT READ BLK: 843781344 CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 843781344, 843781345, 843781346, 843781347, /dev/vinum/abyss: CANNOT FIGURE OUT FILE SYSTEM PARTITION It mounted fine last night and everything looked perfect. Then I did a reboot and ... well, this is it now. Can anybody help me out? Regards, Ole. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Vinum problem: Incompatible sector sizes
I have mailed about this problem a few times now, and I have got responses from Greg very quick where he asks for more information, but I never get any replies on my replies. This makes me worried that I'm doing something wrong or that I appear to be rude, something I certainly don't want to be, instead I'm very very grateful for all the work he and all other volnteers do for this great community. Well, here is all answers on the standard vinum-error report form: (I'm forced to do my mails through a web-interface so the formatting is a bit out of my control. This mail can also be found here: http://sherlock.space2u.com/sweclockers/vinumproblem.txt) What problems are you having? One of my drives was flagged down. I replaced it and can't get the plex to synk. It says: vinum: incompatible sector sizes. raid.p0.s2 has 0 bytes, raid.p0 has 512 bytes. Ignored. As I wrote in an earlier message I have some non-backed-up pictures from my sons first year on this RAID, so I'm very very interested to get it up running. Which version of FreeBSD are you running?: FreeBSD 5.1 Have you made any changes to the system sources, including Vinum?: Nope Supply the output of the vinum list command. 3 drives: D c State: up /dev/ad5s1e A: 36/117796 MB (0%) D b State: up /dev/ad4s1e A: 36/117796 MB (0%) D a State: up /dev/ad1s1e A: 36/117796 MB (0%) 1 volumes: V raid State: up Plexes: 1 Size:230 GB 1 plexes: P raid.p0R5 State: corrupt Subdisks: 3 Size: 230 GB 3 subdisks: S raid.p0.s0State: R 0% D: aSize:115 GB *** Start raid.p0.s0 with 'start' command *** S raid.p0.s1State: up D: bSize:115 GB S raid.p0.s2State: R 0% D: cSize:115 GB *** Start raid.p0.s2 with 'start' command *** Supply an extract of the Vinum history file: 16 Dec 2003 01:25:27.318128 *** vinum started *** 16 Dec 2003 01:25:27.319795 start 16 Dec 2003 18:46:56.235010 *** vinum started *** 16 Dec 2003 18:46:56.247488 list 16 Dec 2003 20:56:19.558646 *** vinum started *** 16 Dec 2003 20:56:19.559826 list 16 Dec 2003 21:01:20.895937 *** vinum started *** 16 Dec 2003 21:01:20.897137 list 16 Dec 2003 21:09:40.557217 *** vinum started *** 16 Dec 2003 21:09:40.558411 list 16 Dec 2003 21:14:18.618942 *** vinum started *** 16 Dec 2003 21:14:18.620141 create configfile drive data3 device /dev/ad5e 16 Dec 2003 21:15:29.979837 *** vinum started *** 16 Dec 2003 21:15:29.981017 list 16 Dec 2003 21:15:34.865735 *** vinum started *** 16 Dec 2003 21:15:34.866870 create configfile drive c device /dev/ad5s1e 16 Dec 2003 21:15:40.182047 *** vinum started *** 16 Dec 2003 21:15:43.993956 list 16 Dec 2003 21:15:57.808870 start raid.p0.s0 16 Dec 2003 21:16:10.026204 start raid.p0.s1 16 Dec 2003 21:16:19.150372 list 16 Dec 2003 21:17:58.211696 start raid.p0.s0 16 Dec 2003 21:27:29.356654 quit 16 Dec 2003 22:56:19.832035 *** vinum started *** 16 Dec 2003 22:56:21.813969 list 16 Dec 2003 22:56:44.429803 quit 16 Dec 2003 22:59:22.807721 *** vinum started *** 16 Dec 2003 22:59:22.808967 create configfile drive c device /dev/ad5e 16 Dec 2003 22:59:40.678243 *** vinum started *** 16 Dec 2003 22:59:40.679445 create configfile drive c device /dev/ad5s1e 16 Dec 2003 23:00:02.110682 *** vinum started *** 16 Dec 2003 23:00:02.111828 start raid.p0.s0 16 Dec 2003 23:00:11.598073 *** vinum started *** 16 Dec 2003 23:00:13.247234 list 16 Dec 2003 23:00:33.071709 start raid.p0.s1 16 Dec 2003 23:00:41.104770 list 16 Dec 2003 23:00:51.455482 start raid.p0.s2 16 Dec 2003 23:00:51.455482 start raid.p0.s2 16 Dec 2003 23:00:56.101483 list 16 Dec 2003 23:01:45.663403 help 16 Dec 2003 23:01:52.767021 help start 16 Dec 2003 23:02:00.394404 list 16 Dec 2003 23:02:08.250819 start -w raid.p0 16 Dec 2003 23:07:31.922053 checkparity raid.p0 16 Dec 2003 23:07:52.140702 dumpconfig a 16 Dec 2003 23:07:59.678513 dumpconfig b 16 Dec 2003 23:08:00.959856 dumpconfig c 16 Dec 2003 23:08:08.539420 dumpconfig 16 Dec 2003 23:10:55.536584 start raid.p0.s1 16 Dec 2003 23:10:58.373358 list 16 Dec 2003 23:11:16.284570 start raid.p0 16 Dec 2003 23:14:50.126646 l -r raid 16 Dec 2003 23:25:15.116456 list 16 Dec 2003 23:25:41.387834 list 16 Dec 2003 23:30:27.673287 help 16 Dec 2003 23:30:58.891550 checkparity raid.p0 16 Dec 2003 23:31:00.930865 checkparity raid 16 Dec 2003 23:31:05.092380 checkparity raid.p0.s1 16 Dec 2003 23:31:06.934016 checkparity raid.p0 16 Dec 2003 23:34:05.938272 rebuildparity raid.p0 16 Dec 2003 23:39:31.680231 list 16 Dec 2003 23:41:07.975224 quit 18 Dec 2003 02:34:34.697591 *** vinum started *** 18 Dec 2003 02:34:34.728151 list Supply an extract of the file /var/log/messages /var/log/messages: Dec 13 09:00:00 big
Vinum problem. Full error report attached.
This is an old thread, that I have cleaned up to maybe get an answer. * What problems are you having? One of my drives are flagged down. Vinum reports that drive as referenced. The other two drives in the RAID-5 is up. According to vinum list my subdisks are: s0 State: R 0% s1 State: crashed s2 State: stale * * Which version of FreeBSD are you running? FreeBSD 5.1 Have you made any changes to the system sources, including Vinum? Nope Supply the output of the vinum list command. 2 drives: D b State: up /dev/ad4s1e A: 36/117796 MB (0%) D a State: up /dev/ad1s1e A: 36/117796 MB (0%) D c State: referenced unknown A: 0/0 MB 1 volumes: V raid State: down Plexes: 1 Size: 230GB 1 plexes: P raid.p0 R5 State: faulty Subdisks: 3 Size: 230 GB 3 subdisks: S raid.p0.s0 State: R 0% D: a Size: 115GB *** Start raid.p0.s0 with 'start' command *** S raid.p0.s1 State: crashed D: b Size: 115GB S raid.p0.s2 State: stale D: c Size: 115GB * * Supply an extract of the Vinum history file Can't do that, can't run an editor now. (TMP drive read-only) * * Supply an extract of the file /var/log/messages /var/log/messages: Dec 13 09:00:00 big newsyslog[786]: logfile turned over due to size100K Dec 13 12:46:05 big kernel: ad4: soft error (ECC corrected) cmd=read fsbn 237565992 of 237565992-237566023 Dec 13 12:46:05 big kernel: ad4: hard error cmd=read fsbn 237565992 of 237565992-237566023 status=7f error=7f Dec 13 12:46:05 big kernel: vinum: raid.p0.s1 is crashed by force Dec 13 12:46:05 big kernel: vinum: raid.p0 is corrupt Dec 13 12:46:05 big kernel: fatal:raid.p0.s1 read error, block 237565929 for 16384 bytes Dec 13 12:46:05 big kernel: raid.p0.s1: user buffer block 475130592 for 16384 bytes Dec 13 12:46:05 big kernel: ad4: soft error (ECC corrected) cmd=read fsbn 238506216 of 238506216-238506247 Dec 13 12:46:05 big kernel: ad4: hard error cmd=read fsbn 238506216 of 238506216-238506247 status=7f error=7f Dec 13 12:46:05 big kernel: fatal:raid.p0.s1 read error, block 238506153 for 16384 bytes Dec 13 12:46:05 big kernel: raid.p0.s1: user buffer block 477011872 for 16384 bytes Dec 13 12:46:05 big kernel: ad4: soft error (ECC corrected) cmd=write fsbn 71 Dec 13 12:46:05 big kernel: ad4: hard error cmd=write fsbn 71 status=7f error=7f Dec 13 12:46:05 big kernel: vinum: Can't write config to /dev/ad4s1e, error 5 Dec 13 12:46:05 big kernel: vinum: drive b is down Dec 13 12:46:05 big kernel: ad4: soft error (ECC corrected) cmd=write fsbn 237565992 of 237565992-237566023 Dec 13 12:46:05 big kernel: ad4: hard error cmd=write fsbn 237565992 of 237565992-237566023 status=7f error=7f Dec 13 12:46:05 big kernel: vinum: raid.p0.s1 is stale by force Dec 13 12:46:05 big kernel: fatal :raid.p0.s1 write error, block 237565929 for 16384 bytes Dec 13 12:46:05 big kernel: raid.p0.s1: user buffer block 475130592 for 16384 bytes Dec 13 12:46:05 big kernel: ad4: soft error (ECC corrected) cmd=write fsbn 238506216 of 238506216-238506247 Dec 13 12:46:05 big kernel: ad4: hard error cmd=write fsbn 238506216 of 238506216-238506247 status=7f error=7f Dec 13 12:46:05 big kernel: fatal :raid.p0.s1 write error, block 238506153 for 16384 bytes Dec 13 12:46:05 big kernel: raid.p0.s1: user buffer block 477011872 for 16384 bytes Dec 13 12:46:05 big kernel: ad4: soft error (ECC corrected) cmd=read fsbn 238506280 of 238506280-238506311 Dec 13 12:46:05 big kernel: ad4: hard error cmd=read fsbn 238506280 of 238506280-238506311 status=7f error=7f Dec 13 12:46:05 big kernel: vinum: raid.p0.s1 is crashed by force Dec 13 12:46:05 big kernel: fatal:raid.p0.s1 read error, block 238506217 for 16384 bytes Dec 13 12:46:05 big kernel: raid.p0.s1: user buffer block 477011936 for 16384 bytes Dec 13 12:46:05 big kernel: ad4: soft error (ECC corrected) cmd=write fsbn 238506280 of 238506280-238506311 Dec 13 12:46:05 big kernel: ad4: hard error cmd=write fsbn 238506280 of 238506280-238506311 status=7f error=7f Dec 13 12:46:05 big kernel: vinum: raid.p0.s1 is stale by force Dec 13 12:46:05 big kernel: fatal :raid.p0.s1 write error, block 238506217 for 16384 bytes Dec 13 12:46:05 big kernel: raid.p0.s1: user buffer block 477011936 for 16384 bytes Dec 13 12:46:05 big kernel: ad4: soft error (ECC corrected) cmd=read fsbn 1 Dec 13 12:46:05 big kernel: ad4: hard error cmd=read fsbn 1 status=7f error=7f Dec 13 12:46:05 big kernel: ad4: soft error (ECC corrected) cmd=read fsbn 0 Dec 13 12:46:05 big kernel: ad4: hard error cmd=read fsbn 0 status=7f error=7f Dec 13 12:46:05 big kernel: ad4: soft error (ECC corrected) cmd=read fsbn 64 Dec 13 12:46:05 big kernel: ad4:
big vinum problem
After a power loss last night i restarted my server with a 425 gig or so RAID-5 array and expected to go through a length fsck after which the system would come up. However, one of the vinum subdisks was down. So, i rebooted into single user mode, i restarted the home.p0.s3 subdisk and then i ran a manual fsck. What followed was a series of hard errors that said: ad7s1e: hard error reading fsbn 86482817 of 43241337-43241448 (ad7s1 bn 86482817; cn 5383 tn 78 sn 8) status=59 error=40 vinum: home.p0.s3 is crashed by force vinum: home.p0 is degraded fatal: home.p0.s3 read error, block 43241337 for 57344 bytes home.p0.s3 user buffer block 30268632 for 57344 bytes ** Phase 2 - Check Pathnames ad11s1e hard error etc then home.p0.s7 becomes corrupt and crashes by force and then i find myself staring at a screen that says: CANNOT READ: BLK 297103054 CONTINUE [yn] I have done this twice now and every time vinum successfully initializes the subdisk and the plex comes up and is in the up state but once i run fsck it crashes again. What exactly can i do to remedy this. If it's a bad disk i'll replace it but can't vinum work around bad blocks? My system is FreeBSD 4.9 RC from RELEASE branch with all the latest patches, i'm fully up to date. I have 8 subdisks in vinum home.p0.s0-s7 with a 55 GB partition on each drive used by vinum. All the drives are identical and all they contain is the vinum partitions. Please CC me in any emails you send as I am not on the list. Thanks for your help! octavian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: big vinum problem
On Monday, 13 October 2003 at 23:46:12 -0700, Octavian Hornoiu wrote: After a power loss last night i restarted my server with a 425 gig or so RAID-5 array and expected to go through a length fsck after which the system would come up. However, one of the vinum subdisks was down. So, i rebooted into single user mode, i restarted the home.p0.s3 subdisk and then i ran a manual fsck. What followed was a series of hard errors that said: ad7s1e: hard error reading fsbn 86482817 of 43241337-43241448 (ad7s1 bn 86482817; cn 5383 tn 78 sn 8) status=59 error=40 vinum: home.p0.s3 is crashed by force vinum: home.p0 is degraded fatal: home.p0.s3 read error, block 43241337 for 57344 bytes home.p0.s3 user buffer block 30268632 for 57344 bytes ** Phase 2 - Check Pathnames ad11s1e hard error etc then home.p0.s7 becomes corrupt and crashes by force and then i find myself staring at a screen that says: CANNOT READ: BLK 297103054 CONTINUE [yn] I have done this twice now and every time vinum successfully initializes the subdisk and the plex comes up and is in the up state but once i run fsck it crashes again. What exactly can i do to remedy this. If it's a bad disk i'll replace it but can't vinum work around bad blocks? That depends on your configuration, which you haven't described. Take a look at http://www.vinumvm.org/vinum/how-to-debug.html. My system is FreeBSD 4.9 RC from RELEASE branch with all the latest patches, i'm fully up to date. I have 8 subdisks in vinum home.p0.s0-s7 with a 55 GB partition on each drive used by vinum. All the drives are identical and all they contain is the vinum partitions. It looks as if you have only one plex, then. Vinum doesn't normally recover from these problems. It follows a slightly different policy from UFS: if there are bad sectors on a subdisk, it doesn't trust the entire subdisk. There are ways around this, but they haven't been committed. Send me the information asked for on the web page and I'll send you instructions on how to fix the problem. This still means that you'll probably have to change the disk. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
