Re: vinum crashed
Hi there, On Thu, Feb 26, 2004 at 09:14:06AM +0100, Axel S. Gruner wrote: I setup a disk stripping with two disks and vinum. I was impressed about the quick and easy setup. The configuration is, that i installed FreeBSD 5.2.1-RC2 on /, a little bit of swap, and the gave the rest for vinum. So the two disks have both a bootable / and /usr and /var is on vinum. All went fine and was working. Yes, was... A colleague of mine went to the server, took the first HD out, and tried to boot. Crash. Single user mode. Thats it. (strange guy...). Ok, i put the second HD in, rebooted the server, and still found myself in single user. fsck on vinum does not work (but the filesystem wants to do a fsck). So i looked at vinum ls output an saw that vinum is marked as crashed. After a #vinum vinum -- start the stripping was up again. Happy happy joy joy i thought and i booted into multiuser mode. To test it out, i rebooted the machine, and, no more happy happy und no more joy joy, the system boots in single user mode, wants to fsck vinum, can not do that Yes, i know, it would be fine to post some error messages, but right now i dont have any access to that machine. So, what could be the problem, and how to solve it. I appreciate any hints. Do you include start_vinum=YES in your /etc/rc.conf ? It is likely given information about past working, but maybe it was lost/changed? After a subdisk has crashed the data is still valid so a 'vinum start' should bring the plex back online. This will then give you full access to your filesystems. At that point you should run fsck on the vinum volumes to ensure no errors. Anytime you start in single user mode you will need to begin with a 'vinum start' command at least to get vinum going unless you load vinum in /etc/loader.conf or something. To help any further we would need some specific error details. Regards, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vinum crashed
Hi. I setup a disk stripping with two disks and vinum. I was impressed about the quick and easy setup. The configuration is, that i installed FreeBSD 5.2.1-RC2 on /, a little bit of swap, and the gave the rest for vinum. So the two disks have both a bootable / and /usr and /var is on vinum. All went fine and was working. Yes, was... A colleague of mine went to the server, took the first HD out, and tried to boot. Crash. Single user mode. Thats it. (strange guy...). Ok, i put the second HD in, rebooted the server, and still found myself in single user. fsck on vinum does not work (but the filesystem wants to do a fsck). So i looked at vinum ls output an saw that vinum is marked as crashed. After a #vinum vinum -- start the stripping was up again. Happy happy joy joy i thought and i booted into multiuser mode. To test it out, i rebooted the machine, and, no more happy happy und no more joy joy, the system boots in single user mode, wants to fsck vinum, can not do that Yes, i know, it would be fine to post some error messages, but right now i dont have any access to that machine. So, what could be the problem, and how to solve it. I appreciate any hints. asg ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vinum crashed disk error
Hello, Three IDE drives multiplexed together to make one large partition (for mounting as /usr/local). We were messing with hardware in the box and when we rebooted vinum spat out errors about defective objects and the boot came to a halt. We figured we had left something loose or unplugged on the motherboard, so we shut it down and took a look. Sure enough, the plug in the mobo's secondary IDE channel was loose, so we reseated it and powered the machine up again. We saw that the kernel found all the IDE drives and figured the problem was over. But vinum had the same problem. It said (loose quotation): /dev/ mounted read-only. vinum config not being rebuilt. And then spit out the same errors it had the first time. Unfortunately, the vinum.org domain is having problems of some sort, and the vinum help pages on lemis.com are redirected to the vinum.org site, so I am deprived of a great trouble-shooting resource. System is 4.8-STABLE. Below you will see the output of 'vinum start'. Any suggestions as to fixing this problem would be greatly appreciated, as we do make production use of this box. Thank you in advance for any words you may be able to offer. -John output of 'vinum start': Warning: defective objects V bigdisk State: down Plexes: 1 Size: 23 GB P big_plexC State: faulty Subdisks: 3 Size: 23 GB S drive0State: down PO:0 B Size: 8063 MB S drive2State: crashed PO: 8063 MB Size: 8063 MB S drive3State: crashed PO: 15 GB Size: 8063 MB -- +---+ | John Fox [EMAIL PROTECTED] |System Administrator | InfoStructure | +---+ |Gideon: I thought you said don't hold a grudge.| | Galen: I don't. I have no surviving enemies...at all. | | -- Crusdade, _Racing the Night_ | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vinum crashed disk error -- addendum
Maybe it'll help if I give some more comprehensive information: vinum - l 3 drives: D ide0e State: up Device /dev/ad0s1e Avail: 0/8063 MB (0%) D ide2e State: up Device /dev/ad2s1e Avail: 0/4031 MB (0%) D ide3e State: up Device /dev/ad3s1e Avail: 0/8063 MB (0%) 1 volumes: V bigdisk State: down Plexes: 1 Size: 23 GB 1 plexes: P big_plexC State: faulty Subdisks: 3 Size: 23 GB 3 subdisks: S drive0State: down PO:0 B Size: 8063 MB S drive2State: crashed PO: 8063 MB Size: 8063 MB S drive3State: crashed PO: 15 GB Size: 8063 MB Thanks, John -- +---+ | John Fox [EMAIL PROTECTED] |System Administrator | InfoStructure | +---+ |Gideon: I thought you said don't hold a grudge.| | Galen: I don't. I have no surviving enemies...at all. | | -- Crusdade, _Racing the Night_ | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum crashed disk error -- addendum
On Tuesday, 23 September 2003 at 11:29:44 -0700, John Fox wrote: Maybe it'll help if I give some more comprehensive information: vinum - l 3 drives: D ide0e State: up Device /dev/ad0s1e Avail: 0/8063 MB (0%) D ide2e State: up Device /dev/ad2s1e Avail: 0/4031 MB (0%) D ide3e State: up Device /dev/ad3s1e Avail: 0/8063 MB (0%) 1 volumes: V bigdisk State: down Plexes: 1 Size: 23 GB 1 plexes: P big_plexC State: faulty Subdisks: 3 Size: 23 GB 3 subdisks: S drive0State: down PO:0 B Size: 8063 MB S drive2State: crashed PO: 8063 MB Size: 8063 MB S drive3State: crashed PO: 15 GB Size: 8063 MB By itself, this is meaningless. If you have a problem, look at the man page or the web site for information on how to report it. 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
Re: vinum crashed disk error
On Tuesday, 23 September 2003 at 11:21:49 -0700, John Fox wrote: Hello, Three IDE drives multiplexed together to make one large partition (for mounting as /usr/local). We were messing with hardware in the box and when we rebooted vinum spat out errors about defective objects and the boot came to a halt. We figured we had left something loose or unplugged on the motherboard, so we shut it down and took a look. Sure enough, the plug in the mobo's secondary IDE channel was loose, so we reseated it and powered the machine up again. We saw that the kernel found all the IDE drives and figured the problem was over. But vinum had the same problem. It said (loose quotation): /dev/ mounted read-only. vinum config not being rebuilt. And then spit out the same errors it had the first time. These messages have a purpose. You shouldn't just ignore them. Unfortunately, the vinum.org domain is having problems of some sort, What sort? More error messages? I have no problem accessing it (and no, it's not here, it's at the other end of the world). and the vinum help pages on lemis.com are redirected to the vinum.org site, They're on the same server. so I am deprived of a great trouble-shooting resource. There are still the man pages. output of 'vinum start': Warning: defective objects V bigdisk State: down Plexes: 1 Size: 23 GB P big_plexC State: faulty Subdisks: 3 Size: 23 GB S drive0State: down PO:0 B Size: 8063 MB S drive2State: crashedPO: 8063 MB Size: 8063 MB S drive3State: crashedPO: 15 GB Size: 8063 MB Any suggestions as to fixing this problem would be greatly appreciated, as we do make production use of this box. Do these objects have any relationship to each other? The naming is confusing to say the least. In general, though, if your drives are up again, and the volume only has one plex, you can use the 'vinum setupstate' command to explicitly set the state to up. You'll then need to save the configuration with saveconfig after you've confirmed that the data is OK. 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
