I have been playing with Vinum and my first serious experiment resulted in a serious failure. I am not sure if my hard drive just chose this moment to fail or if it is a configuration problem but I can't seem to do anything with the drive anymore:
I have a 40 G IBM drive that I have not really ever used. I configured it with Vinum to be a single volume with a single plex and a single drive (can't get much simpler than that.) After newfs'ing it I proceded to copy about 35G of data to it. While doing other things my system suddenly froze. I could not switch to a virtual terminal. The machine was no longer funtioning as a gateway but I could still ping it. I had no other option than to reboot. On reboot fsck successful cleaned up various inconsistoncies on various partitions (not the vinum volume.) The last message in /etc/messages was: Feb 24 07:23:47 hoho /kernel: pid 756 (kdeinit), uid 1000 on /: file system full Although none of my file systems are full after reboot. The drive ad7 still shows up in my boot messages. When I started vinum I got this in /var/messages: Feb 24 21:36:47 hoho /kernel: vinum: loaded Feb 24 21:37:17 hoho /kernel: vinum: drive a is up Feb 24 21:37:17 hoho /kernel: vinum: simplevinum.p0.s0 is up Feb 24 21:37:17 hoho /kernel: vinum: simplevinum.p0 is up Feb 24 21:37:17 hoho /kernel: vinum: simplevinum is up Feb 24 21:37:17 hoho /kernel: ad7s1e: hard error writing fsbn 8 (ad7s1 bn 8; cn 0 tn 0 sn 8)ad7s1e: hard error writing fsbn 8 (ad7s1 bn 8; cn 0 tn 0 sn 8) status=51 error=04 Feb 24 21:37:17 hoho /kernel: ad7: DMA problem fallback to PIO mode Feb 24 21:37:17 hoho /kernel: vinum: Can't write config to /dev/ad7s1e, error 5 Feb 24 21:37:17 hoho /kernel: vinum: drive a is down Feb 24 21:37:17 hoho /kernel: vinum: simplevinum.p0.s0 is crashed Feb 24 21:37:17 hoho /kernel: vinum: simplevinum.p0 is faulty Feb 24 21:37:17 hoho /kernel: vinum: simplevinum is down I then tried to reconfigure the drive: su-2.05# dd if=/dev/zero of=/dev/ad7 bs=1k count=1 dd: /dev/ad7: Input/output error 1+0 records in 0+0 records out 0 bytes transferred in 0.014675 secs (0 bytes/sec) with the /var/log/messages output of: Feb 25 00:16:50 hoho /kernel: ad7: hard error writing fsbn 0 of 0-1 (ad7 bn 0; cn 0 tn 0 sn 0) status=51 error=04 Note, I have an identical drive on the same IDE controller and it is still working fine, so I don't think it is a controller problem. Is my drive toast? -- David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
