01-04-2010
Please re-create the metadb and mirrors again. That's Step 2
10 More Discussions You Might Find Interesting
1. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
2. Solaris
I had installed solaris 10 on 440 on disk 0. I had done ufsrestore on disk1 from tape and then rebooted
Rebooting with command: boot disk1
Boot device: /pci@1f,700000/scsi@2/disk@1,0 File and args:
SunOS Release 5.10 Version Generic_118833-24 64-bit
Copyright 1983-2006 Sun Microsystems,... (3 Replies)
Discussion started by: vr76413
3 Replies
3. Red Hat
Hello,
I have a test PC running Fedora 10. Friday evening it was working fine, I have some perl scripts which are scheduled to run every morning.
But when I started work this morning, I found I cannot ping the machine. When I switched on the monitor, I saw the GRUB promt :(. I am not sure... (10 Replies)
Discussion started by: SivaramaRaju
10 Replies
4. Ubuntu
I am not able to boot into my ubuntu. Grub gives me this message
How do I boot linux? (6 Replies)
Discussion started by: locoroco
6 Replies
5. Solaris
Hello all;
We have a SunFire V240 with three disks that were part of a metadb. One of those disks, the boot disk, experienced a horrible death Monday night and we're now trying to recover from that.
I know very little about metadb stuff, so please be gentle with me...
I'm assuming... (3 Replies)
Discussion started by: Handon
3 Replies
6. Solaris
Hi,
Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot.
vxplex -g rootdg dis var-02
vxplex -g rootdg dis swapvol-02
vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies
7. Solaris
Update:
The / file system (/dev/rdsk/c1t0d0s0) is being checked
fsck unable to stat
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0).
Root password for system maintenance (control-d to bypass):
I am unable to hit control-d to by pass.
I... (50 Replies)
Discussion started by: br1an
50 Replies
8. Ubuntu
Hi;
I had Windows Server 2003 and performed a fresh Ubuntu Server 15 installation.
After installation, Ubuntu server not booting
I guess there is boot problem conflicting with my old Windows Server.
This is my pastebin:
http://paste.ubuntu.com/13851828/
Any help to start my new... (1 Reply)
Discussion started by: gc_sw
1 Replies
9. Red Hat
Hi,
I just P2V an old machine running Redhat 5.5 on a physical server. After P2V was completed, when boot up it got an error. Please refer to the attachment for the error. Please assist. Thanks. (2 Replies)
Discussion started by: freshmeat
2 Replies
10. Solaris
how to recovery metadb?
Thanks! (1 Reply)
Discussion started by: dzung
1 Replies
PCIC(4) BSD Kernel Interfaces Manual PCIC(4)
NAME
pcic -- PC Card bridge driver
SYNOPSIS
device pcic
device pccard
DESCRIPTION
The pcic driver provides support for older ISA and non-Yenta PCI PC Card bridges. The pcic driver supports most ExCA devices attached to the
ISA bus or PCI devices that do not conform to the Yenta specification.
The following ISA devices, or true clones, are supported in the current code.
Intel i82365SL Step A
Intel i82365SL Step B
Intel i82365SL Step C Intel's original 16-bit PC Card controller.
Intel i82365SL-DF Intel's last version of this device. 3.3V support was added.
VLSI 82C146 An older VLSI part with some issues on some machines.
Cirrus Logic PD-6710
Cirrus Logic PD-6720
Cirrus Logic PD-6722 Cirrus Logic's pcic controller. Compatible with the i82365SL Step C with the addition of a different 3.3V control.
Ricoh RF5C296
Ricoh RF5C396 Ricoh's PC Card bridge chips. These are compatible with the i82365SL Step C, but with yet another different 3.3V con-
trol.
Vadem 365
Vadem 465 Compatible with i82365SL Step C.
Vadem 468
Vadem 469 Like the earlier Vadem models, but with Vadem's own, incompatible, 3.3V control system.
IBM PCIC IBM clone of the original i82365SL part, with its own ID register value. Has no 3.3V ability.
Many other vendors made parts in this arena, but most of them were compatible with one of the above chipsets.
The following PCI pcmcia bridges are supported:
Cirrus Logic PD6729
Cirrus Logic PD6730
O2micro OZ6729
O2micro OZ6730
BUGS
This does not work at all at the moment.
BSD
July 9, 2002 BSD