Sponsored Content
Full Discussion: Solved: Disk Unable to Boot
Operating Systems Solaris Solved: Disk Unable to Boot Post 302870143 by br1an on Friday 1st of November 2013 09:02:18 AM
Old 11-01-2013
Not a problem hicksd8,

I inherited this server so I have no idea whats going on. Other than the fact is now it's not booting up and I have to bring it back up... somehow..
 

9 More Discussions You Might Find Interesting

1. Solaris

unable to boot from disk1

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

2. Solaris

vxvm root disk booting problem - solved with boot -a. How?

Hi All, We had a Sun Netra T1 go down the other day, the root disk was mirrored using vxvm. Upon boot from either disk, we had the following error appear: WARNING: Error writing ufs log state WARNING: ufs log for / changed state to Error WARNING: Please umount(1M) / and run... (4 Replies)
Discussion started by: badoshi
4 Replies

3. Red Hat

Unable to boot Fedora 10

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. Hardware

[Solved] Boot Lockup After Drive Swap

Hey All, Im using Fedora 2.6 (which is cannot be changed for compatibility reasons). I cloned a drive from a different server and when i added this drive to a new box, during startup it hangs on "Configuring Kernel Parameters:" Is there any way to bypass this process and still boot... (0 Replies)
Discussion started by: robfwauk
0 Replies

5. Fedora

[Solved] Unable to start Matlab program

hello everyone, I have Matlab installed on Fedora 16. I tried running it by simply typing on terminal: $ matlabBut it returned the follwoing error: --- can anyone suggest a solution? cheers, peter ---------- Post updated at 10:57 PM ---------- Previous update was at 10:54 PM ----------... (1 Reply)
Discussion started by: peter_071
1 Replies

6. Solaris

Unable to boot from mirror disk on x86 server configured under VxVM

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

How to specify local boot up disk in CD boot Grub?

Hi Solaris 10 Experts, I am wondering what is the correct syntax to edit in Grub when trying to specify the local ZFS boot disk while booting up from a Solaris 10 x86 64bits DVD installation disk. In other word, I try to boot up from local disk without removing the Solaris installation disk... (0 Replies)
Discussion started by: gjackson123
0 Replies

8. Solaris

Use 'dd' to copy boot disk to larger target disk

Hi, I'm looking to copy a boot disk on an old Solaris 8 system using dd. I'll bring the system down to single user mode and begin from there. I'm copying my source disk to a larger target disk. Do I need to do anything other than the 'dd' command below because the target disk is bigger? ... (2 Replies)
Discussion started by: sparcman
2 Replies

9. Red Hat

Unable to boot up after P2V

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
PCN(4)							   BSD Kernel Interfaces Manual 						    PCN(4)

NAME
pcn -- AMD PCnet/PCI Fast Ethernet device driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device miibus device pcn Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_pcn_load="YES" DESCRIPTION
The pcn driver provides support for PCI Ethernet adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO and PCnet/Home Ethernet controller chips. Supported NIC's include the Allied Telesyn AT-2700 family. The PCnet/PCI chips include a 100Mbps Ethernet MAC and support both a serial and MII-compliant transceiver interface. They use a bus master DMA and a scatter/gather descriptor scheme. The AMD chips provide a mechanism for zero-copy receive, providing good performance in server environments. Receive address filtering is provided using a single perfect filter entry for the station address and a 64-bit multicast hash table. The pcn driver supports the following media types: autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to rc.conf(5). 10baseT/UTP Set 10Mbps operation. The ifconfig(8) mediaopt option can also be used to select either 'full-duplex' or 'half-duplex' modes. 100baseTX Set 100Mbps (Fast Ethernet) operation. The ifconfig(8) mediaopt option can also be used to select either 'full-duplex' or 'half-duplex' modes. The pcn driver supports the following media options: full-duplex Force full duplex operation. half-duplex Force half duplex operation. For more information on configuring this device, see ifconfig(8). HARDWARE
The pcn driver supports adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips: o AMD Am79C971 PCnet-FAST o AMD Am79C972 PCnet-FAST+ o AMD Am79C973/Am79C975 PCnet-FAST III o AMD Am79C976 PCnet-PRO o AMD Am79C978 PCnet-Home o Allied-Telesis LA-PCI DIAGNOSTICS
pcn%d: couldn't map ports/memory A fatal initialization error has occurred. pcn%d: couldn't map interrupt A fatal initialization error has occurred. pcn%d: watchdog timeout The device has stopped responding to the network, or there is a problem with the network connection (e.g. a cable fault). pcn%d: no memory for rx list The driver failed to allocate an mbuf for the receiver ring. pcn%d: no memory for tx list The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. pcn%d: chip is in D3 power state -- setting to D0 This message applies only to adapters which support power management. Some operating sys- tems place the controller in low power mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configur- ing it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. If you see this message at boot time and the driver fails to attach the device as a network interface, you will have to perform a warm boot to have the device properly configured. Note that this condition only occurs when warm booting from another operating system. If you power down your system prior to booting FreeBSD, the card should be configured correctly. SEE ALSO
arp(4), miibus(4), netintro(4), ng_ether(4), ifconfig(8) AMD PCnet/FAST, PCnet/FAST+ and PCnet/Home datasheets, http://www.amd.com. HISTORY
The pcn device driver first appeared in FreeBSD 4.3. AUTHORS
The pcn driver was written by Bill Paul <wpaul@osd.bsdi.com>. BSD
January 31, 2006 BSD
All times are GMT -4. The time now is 08:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy