Sponsored Content
Full Discussion: PANIC Error
Top Forums UNIX for Advanced & Expert Users PANIC Error Post 28212 by hachik on Sunday 15th of September 2002 02:31:20 PM
Old 09-15-2002
was it crashed physically ? or just partitioning problems ? i dont get a thing
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Panic

Hi All, When I came officce this morning I saw this error messages on the screen ----- PANIC:srmountfun - Error 6 mounting rootdev hd (1/42) Cannot dump 32639 pages to dumpdev hd (1/41) : space for only 0 pages Dump not completed -------- and machine was reboot mode. Why this problem... (3 Replies)
Discussion started by: alisev
3 Replies

2. SCO

Panic :

Hi Friends , i am getting the following error when iam booting a sco unix system. ------------------ H init PANIC : srmountfun --Error 22 mounting rootdev hd(1/42) cannot dump 40863 pages to dempdev hd(1/41) : space for only 0 pages. Dump not completed. Safe to power off.... (1 Reply)
Discussion started by: sveera
1 Replies

3. Red Hat

error : kernel panic: No init found

helo, my system is runing on redhat 9.0. but now when i run my machine i got the following error. Kernel Panic:No init found. try passing init = option to kernel. i dont have any idea about linux administration. can u help me to solve this error Thanks and Regards,... (2 Replies)
Discussion started by: amitpansuria
2 Replies

4. Linux

Kernal panic error& setuproot:error mounting /proc&/sys

Hi all, I am new to redhat/fedora linux. In fedora linux 6,we created one file system(hda3 - /fs). in this mount poing we were installed mounta vista os. while booting we are getting below error messages. 1) Booting 'mountaVisat(2.6.18_pro 500_pc_target-x86_586 smp)' root(hd0,1)... (2 Replies)
Discussion started by: arjunreddy3
2 Replies

5. Solaris

can any body tell me what is the difference between server panic and fatal error.

HI friends can any body tell me what is the difference between server panic and fatal error. (1 Reply)
Discussion started by: tv.praveenkumar
1 Replies

6. SCO

"PANIC: k_trap" error

hi I've virtualized physical SCO 5.0.6 on ESX 4 according to: Blog du DS45: HOWTO SCO P2V in the real life SCO starts with the network, but during shutdown I'm getting this message: PANIC: k_trap. My /etc/default/boot: # cat /etc/default/boot #ScoAdminInit BOOTMNT {RO RW NO} RO... (4 Replies)
Discussion started by: ccc
4 Replies

7. Red Hat

Kernel Panic Error

Hi Guys, I'm working with a down RedHat Server. Whenever the server tries to boot, there's an error stating: Kernel panic: No init found. Try passing init= option to kernel. In addition to this, the "Caps Lock" and "Scroll Lock" lights start flashing. The server doesn't boot pass this... (1 Reply)
Discussion started by: bbbngowc
1 Replies

8. Solaris

"PANIC CPU" ERROR MESSAGE

A server that I am working on (SUN FIRE V240 , SOLARIS 10) doesn't boot because of a corrupted files system. I tried to repair de file system, I also tried to to restore all the files systems with a backup of the server that I have but the message bellow appear panic/thread=30002fc2060:... (8 Replies)
Discussion started by: feg
8 Replies

9. Solaris

Panic error

Hi All, I am getting the below error after login to box. SunOS Release 5.10 Version Generic_147440-02 64-bit Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved. os-io Cross trap sync timeout: at cpu_sync.xword: 0x1010panic: failed to sto p cpu8 panic: failed to... (1 Reply)
Discussion started by: chetansingh23
1 Replies

10. Red Hat

Error: kernal panic not syncing

HI All, server stopped here, we are suspecting server crash, need install new OS. Any suggestions on this. kindly help to us. Thanks Rajesh (0 Replies)
Discussion started by: Rajesh_Apple
0 Replies
HPSA(4) 						     Linux Programmer's Manual							   HPSA(4)

NAME
hpsa - HP Smart Array SCSI driver SYNOPSIS
modprobe hpsa [ hpsa_allow_any=1 ] DESCRIPTION
hpsa is a SCSI driver for HP Smart Array RAID controllers. Options hpsa_allow_any=1: This option allows the driver to attempt to operate on any HP Smart Array hardware RAID controller, even if it is not explicitly known to the driver. This allows newer hardware to work with older drivers. Typically this is used to allow installation of operating systems from media that predates the RAID controller, though it may also be used to enable hpsa to drive older controllers that would normally be handled by the cciss(4) driver. These older boards have not been tested and are not supported with hpsa, and cciss(4) should still be used for these. Supported hardware The hpsa driver supports the following Smart Array boards: Smart Array P700M Smart Array P212 Smart Array P410 Smart Array P410i Smart Array P411 Smart Array P812 Smart Array P712m Smart Array P711m StorageWorks P1210m Since Linux 4.14, the following Smart Array boards are also supported: Smart Array 5300 Smart Array 5312 Smart Array 532 Smart Array 5i Smart Array 6400 Smart Array 6400 EM Smart Array 641 Smart Array 642 Smart Array 6i Smart Array E200 Smart Array E200i Smart Array E200i Smart Array E200i Smart Array E200i Smart Array E500 Smart Array P400 Smart Array P400i Smart Array P600 Smart Array P700m Smart Array P800 Configuration details To configure HP Smart Array controllers, use the HP Array Configuration Utility (either hpacuxe(8) or hpacucli(8)) or the Offline ROM-based Configuration Utility (ORCA) run from the Smart Array's option ROM at boot time. FILES
Device nodes Logical drives are accessed via the SCSI disk driver (sd(4)), tape drives via the SCSI tape driver (st(4)), and the RAID controller via the SCSI generic driver (sg(4)), with device nodes named /dev/sd*, /dev/st*, and /dev/sg*, respectively. HPSA-specific host attribute files in /sys /sys/class/scsi_host/host*/rescan This is a write-only attribute. Writing to this attribute will cause the driver to scan for new, changed, or removed devices (e.g., hot-plugged tape drives, or newly configured or deleted logical drives, etc.) and notify the SCSI midlayer of any changes detected. Normally a rescan is triggered automatically by HP's Array Configuration Utility (either the GUI or the command-line variety); thus, for logical drive changes, the user should not normally have to use this attribute. This attribute may be useful when hot plugging devices like tape drives, or entire storage boxes containing preconfigured logical drives. /sys/class/scsi_host/host*/firmware_revision This attribute contains the firmware version of the Smart Array. For example: # cd /sys/class/scsi_host/host4 # cat firmware_revision 7.14 HPSA-specific disk attribute files in /sys /sys/class/scsi_disk/c:b:t:l/device/unique_id This attribute contains a 32 hex-digit unique ID for each logical drive. For example: # cd /sys/class/scsi_disk/4:0:0:0/device # cat unique_id 600508B1001044395355323037570F77 /sys/class/scsi_disk/c:b:t:l/device/raid_level This attribute contains the RAID level of each logical drive. For example: # cd /sys/class/scsi_disk/4:0:0:0/device # cat raid_level RAID 0 /sys/class/scsi_disk/c:b:t:l/device/lunid This attribute contains the 16 hex-digit (8 byte) LUN ID by which a logical drive or physical device can be addressed. c:b:t:l are the controller, bus, target, and lun of the device. For example: # cd /sys/class/scsi_disk/4:0:0:0/device # cat lunid 0x0000004000000000 Supported ioctl() operations For compatibility with applications written for the cciss(4) driver, many, but not all of the ioctls supported by the cciss(4) driver are also supported by the hpsa driver. The data structures used by these ioctls are described in the Linux kernel source file include/linux/cciss_ioctl.h. CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD These three ioctls all do exactly the same thing, which is to cause the driver to rescan for new devices. This does exactly the same thing as writing to the hpsa-specific host "rescan" attribute. CCISS_GETPCIINFO Returns PCI domain, bus, device and function and "board ID" (PCI subsystem ID). CCISS_GETDRIVVER Returns driver version in three bytes encoded as: (major_version << 16) | (minor_version << 8) | (subminor_version) CCISS_PASSTHRU, CCISS_BIG_PASSTHRU Allows "BMIC" and "CISS" commands to be passed through to the Smart Array. These are used extensively by the HP Array Configuration Utility, SNMP storage agents, and so on. See cciss_vol_status at <http://cciss.sf.net> for some examples. SEE ALSO
cciss(4), sd(4), st(4), cciss_vol_status(8), hpacucli(8), hpacuxe(8), <http://cciss.sf.net>, and Documentation/scsi/hpsa.txt and Documentation/ABI/testing/sysfs-bus-pci-devices-cciss in the Linux kernel source tree COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 HPSA(4)
All times are GMT -4. The time now is 01:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy