similar to: 'vinum list' wierd output

Dear colleagues, [I'm under 4-STABLE] What is the correct sequence to delete existing vinum module (for example, raid10) and do *not* use -f flags for vinum? in my case t is raid10 vovume: vinum -> l -r t V t State: up Plexes: 2 Size: 8191 MB P t.p0 S State: up Subdisks: 2 Size: 8191 MB P t.p1 S State:

I am trying to setup vinum on a box using 4.8 RELENG_4 (as of about a week ago snapshot). This box was running 4.6 /w vinum on same hard drives for the last 4 months wonderfully... but since it is my current 'scratch/backup' box, I just reinstalled with -STABLE. # uname -a FreeBSD polya.axista.com 4.8-STABLE FreeBSD 4.8-STABLE #22: Tue Jun 24 17:01:07 EDT 2003

I made an array out of 3 IBM 20 gigs and 3 Maxtor 20 gigs I used striping to make one big drive A couple of days ago I was copying a movie onto to it and the computer decided to reboot when it came back up I was greeted with this message Can someone please tell me if I can recover some how? or should I just rebuild the array? or is one of my disks physically bad? Detects all 7 drives (1 10gig

Hi all, I have some problems with my gvinum setup after the system panic'ed. Afterwards the system fails finding the plexes to the subdisks (or at least that is what I can understand after having searched the gvinum source code for the error string in the DMESG log..) The machine is an IBM Netfinity 5000 and the internal HW self tests does not find any errors in the hw. Luckily my root is

Hi All, I'm about to clean and re-initialize a Maxtor 160GB disk that shows a weird problem but I think I've found a bug in RELENG_4_7 somewhere so if preserving my disk can help conquer one more bug I'm happy to wait a couple of days and help solve that bug. Here's the story: While upgrading from 4.3-STABLE to 4.7p4 and at the same time reorganizing my vinum volumes I copied

I've just had a 4.9p1 system partially deadlock for about 30 minutes and then spontaneously(?) recover. The "ps" results point at vinum. I've never seen this before and don't recall anything like this being mentioned here before. At the time, I had two find's running in a large NFS mounted filesystem and was doing a "cvs -d /usr/ncvs -R checkout -P ports" from

Dear colleagues, experimenting with vinum stripes and mirrors, I'd stuck myself with the following: panic: throw_rude_remark: called without config lock (from vinumconfig.c:throw_rude_remark:103) The system before this panic has two 160G drives with two vinum partitions on each (one for mirrored root and one for the rest with swap between); these were ad0 and ad2. For the experiments,

Hi, I had a power failure, and the on-disk configuration for vinum went bizarre. The logs read from disks are at http://biaix.org/pk/debug/ (log.$DEVICE files). The logs in da0 (barracuda) are the ones obviously wrong, I'm pretty sure the others are ok. Is this a 'virtually' dead drive? Can I force vinum to use the other's drive configuration? What's the less traumatic

Well, colleagues, I'm stuck a bit. I tried many different ways to setup system with vinum root (the only reference I found yet besides old "bootstrapping vinum" article is Joerg's commit message: http://freebsd.rambler.ru/bsdmail/cvs-all_2003/msg01225.html I failed. I have 4-stable system set up at ad0, and tried to set up pair of drives for new system at ad2 and ad3 (actually,

hi i got TOS and retranssmission error on receiving SIP call chan_sip.c:2794 retrans_pkt: Maximum retries exceeded on transmission 10CAED68-0F1D-DF82-DA1E-A76C1CB3D8A3 at 172.18.100.72 for seqno 43156 (Critical Response) -- See doc/sip-retransmit.txt. [May 22 13:42:44] WARNING[18021]: chan_sip.c:2821 retrans_pkt: Hanging up call 10CAED68-0F1D-DF82-DA1E-A76C1CB3D8A3 at 172.18.100.72 - no reply to

Hello. I'm having a 4.7Rp9 server which is since months quite unstable, so I've compiled a debug kernel and got a crash dump. I'm a programmer and I know a little how to use gdb, I'm not so expert about FreeBSD kernel insides however, so I can't get much from it. Any kind of help is appreciated. This is the crash message: IdlePTD at phsyical address 0x0032f000 initial pcb

Before reading below: I am considering a new install rather than an upgrade of our servers. However, now I just want to beat this problem. :) At 02:19 PM 7/8/2003 +0000, Phil Pennock wrote: >On 2003-07-08 at 14:09 +0000, Phil Pennock wrote: > > There was a fairly major update to the IDE disk device handlers which > > required new device nodes. Bringing in the new MAKEDEV script

Hi all! According to www.freebsd.org/releases/5.1R/hardware-i386.html#AEN63 FreeBSD doesnt seem to support the PDC20378 chipset. Anyway, output of dmesg, atapci0: <Promise PDC20378 SATA150 controller> port 0xdc00-0xdc7f,0xdfa0-0xdfaf,0xdf00-0xdf3f mem 0xfeac0000-0xfeadffff,0xfeafe000-0xfeafefff irq 11 at device 4.0 on pci2 more dmesg output: ar0: ERROR - array broken

I upgraded from 6.2 to 6.3 p5 last night. Upon rebooting, the second disk in the mirror is missing. # atacontrol status ar0 ar0: ATA RAID1 status: DEGRADED subdisks: 0 ad0 ONLINE 1 ---- MISSING # grep ata /var/run/dmesg.boot ad0: 238475MB <WDC WD2500AVJB-63UDA0 00.02C01> at ata0-master UDMA100 ad1: 238475MB <WDC WD2500AVJB-63UDA0 00.02C01> at ata0-slave UDMA100 ar0: disk0

I sent this to freebsd-questions earlier via the newsgroup, but I just found out today that the list-to-news gateway has been down for half a month now. Any idea when it's going back up? Who was hosting that service anyway? And now for the question.. I have a test server that is being used to test a 4.4-REL to 4.8-STABLE upgrade, and I've found the system will no longer boot unless I

Hi all, I got a machine with 8GB of RAM and plenty of disk space. I need gvinum to manage big number of file systems but PAE enabled kernel does not compile modules. I couldn't figure out how to get vinum statically compiled in the kernel if that is the way to go. I am running 6-STABLE. Please advise on how to get PAE kernel and gvinum working together! TIA, Stoyan

Hi! Just before we start, this is not the "USB hang on boot" problem. OK? This post got rather long, so I'll summaries it all in a sentence here: With FreeBSD 4.9-rc on an ASUS A7N8X with a cheapo memory stick, simply plugging it in and taking it out a couple of times is a guaranteed panic. I use only one USB device, a cheapo USB memory stick, which I recently bought on a

FreeBSD 4.1.1-RELEASE #1: Tue Oct 10 18:09:51 CDT 2000 root@test-drive.tamu.edu:/usr/src/sys/compile/TEST-DRIVE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM

Hi everybody. I've just upgraded a box from FreeBSD 9 to 9.1 via freebsd-update. At the first reboot, the machine stopped with messages about GRAID : GEOM_RAID: Promise: Subdisk kjihgfedcba`_^]\[ZYXWVUTSRQPONM:0-ada0 state changed from NONE to ACTIVE The trick is that I've never setup any kind of RAID on that old box... Is there a way to completely disable GEOM_RAID loading on boot ?

Hi there, I am newbie and recently started using btrfs. Now facing a weird problem. FWIW, I am on archlinux, kenel v3.8.0, having Btrfs v0.20-rc1. After an abnormal reboot, getting these errors while boot: systemd.fsck[289]: checking extents systemd.fsck[289]: checking fs roots systemd.fsck[289]: checking root refs systemd.fsck[289]: found 23728128 bytes used err is 0 systemd.fsck[289]: total