Sponsored Content
Full Discussion: hard disk meltdown
Special Forums Hardware Filesystems, Disks and Memory hard disk meltdown Post 31262 by Henrik on Tuesday 5th of November 2002 07:23:54 AM
Old 11-05-2002
hard disk meltdown

I had an issue with a second hard disk in my machine. I have a sparc station running solaris 7. It was working fine but now it wont mount on boot up and when you try to mount it manually it gives an I/O error. I tried a different disk as a control which was fine. What I want to know is if my corrupt disk is salvagable. When I try to format it (or run a probe-scsi command from the prom monitor prompt) it recognises that a disk exists but none of its detail and so asks me for input regarding the number of cylinders, heads ...etc.Even then it wont format it and gives the following error to the console window. Is there any hope for this disk or is there any way to analyse what caused the problem in the first place.

14:20:10 m1f526 unix: WARNING: /sbus@1f,0/espdma@e,8400000/esp@e,8800000/sd@4,0 (sd4): Nov 4 14:20:10 m1f526 Error for Command: load/start/stop Error Level: Retryable Nov 4 14:20:10 m1f526 unix: Requested Block: 0 Error Block: 0 Nov 4 14:20:10 m1f526 unix: Vendor: IBM Serial Number: AK0M8545 Nov 4 14:20:10 m1f526 unix: Sense Key: Not Ready Nov 4 14:20:10 m1f526 unix: ASC: 0x4 (LUN not ready), ASCQ: 0x0, FRU: 0x0 Nov 4 14:20:15 m1f526 unix: WARNING: /sbus@1f,0/espdma@e,8400000/esp@e,8800000/sd@4,0 (sd4): Nov 4 14:20:15 m1f526 Error for Command: load/start/stop Error Level: Retryable Nov 4 14:20:15 m1f526 unix: Requested Block: 0 Error Block: 0 Nov 4 14:20:15 m1f526 unix: Vendor: IBM Serial Number: AK0M8545 Nov 4 14:20:15 m1f526 unix: Sense Key: Not Ready Nov 4 14:20:15 m1f526 unix: ASC: 0x4 (LUN not ready), ASCQ: 0x0, FRU: 0x0 Nov 4 14:20:31 m1f526 unix: WARNING: /sbus@1f,0/espdma@e,8400000/esp@e,8800000/sd@4,0 (sd4): Nov 4 14:20:31 m1f526 Error for Command: load/start/stop Error Level: Retryable Nov 4 14:20:31 m1f526 unix: Requested Block: 0 Error Block: 0 Nov 4 14:20:31 m1f526 unix: Vendor: IBM Serial Number: AK0M8545 Nov 4 14:20:31 m1f526 unix: Sense Key: Not Ready Nov 4 14:20:31 m1f526 unix: ASC: 0x4 (LUN not ready), ASCQ: 0x0, FRU: 0x0

Any thoughts would be much appreciated
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hard Disk Problem

Does anyone know of any commands that offer the same sort of facilities of scandisk on windows. My Linux server (Mandrake 6.2) keeps crashing and gives hard disk errors when I reboot. I've used fcsk to fix any problems that arise but when I use dumpe2fs to display disk information it says that... (1 Reply)
Discussion started by: DGM
1 Replies

2. UNIX for Dummies Questions & Answers

RAM, Hard Disk

Hi, I work in a production support environment. All our PROD machines SPARC machines and Solaris O/S. I want to know how to find out what the hard disk size, RAM size etc. of our PROD machines. Please let me know if there is any way to find out this (other than from system administrator). ... (2 Replies)
Discussion started by: ramaraju
2 Replies

3. UNIX Desktop Questions & Answers

Hard Disk

I have a cuestion. How Can I to add other hard disk to my computer? I need to configurate anyone? (4 Replies)
Discussion started by: hmaraver
4 Replies

4. Solaris

how to format a hard disk

hi, i want to format one hard disk in solaris. can you pls help on this.. (2 Replies)
Discussion started by: visu_ak
2 Replies

5. HP-UX

how can i get hard disk usage

I want to get hard disk usage hard disk usage= already allocated/total allocated first I use ioscan -kfnC disk get disk name c#t#d# then I use diskinfo /dev/rdsk/c#t#d# but this command can only get total disk size,not disk usage has any command can get that thanks:) (2 Replies)
Discussion started by: alert0919
2 Replies

6. UNIX for Dummies Questions & Answers

Hard Disk at 99% Help!

:eek: I use this Solaris to run CMS a call acounting software package for my job. No one could run reports today because it said the this when you logged on "The following file systems are low, and could adversely affect server performance: File system /: 99%full" Can some one please explain... (9 Replies)
Discussion started by: mannyisme
9 Replies

7. SCO

declare disk driver for IDE hard disk

hi I've a fresh installation of SCO 5.0.7 on the IDE hard disk. For SCSI hard disk I can declare, for example blc disk driver using: # mkdev hd 0 SCSI-0 0 blc 0but it works for IDE hard disk? (3 Replies)
Discussion started by: ccc
3 Replies

8. Solaris

Need Hard Disk Details

Hi freinds, What is the command to find out the hard disk details (logical name, FS type etc,). Because i connected one ntfs partition and i don't know the hard disk logical and physical name to mount it.Kindly do the needful. Thanks | P.Bharathiraja. :mad: (2 Replies)
Discussion started by: bharathiraja
2 Replies

9. UNIX for Advanced & Expert Users

Need help for getting hard-disk traces

When we write a programme,we declare variables and compiler allocates memory to them.I want to get access to the physical block number of hard-disk where actually the data is stored by the programme " Some one help me out... (3 Replies)
Discussion started by: nagraz007
3 Replies

10. Linux

C++ Code to Access Linux Hard Disk Sectors (with a LoopBack Virtual Hard Disk)

Hi all, I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies
scsi_vu_errmsg(9F)					   Kernel Functions for Drivers 					scsi_vu_errmsg(9F)

NAME
scsi_vu_errmsg - display a SCSI request sense message SYNOPSIS
#include <sys/scsi/scsi.h> void scsi_vu_errmsg(struct scsi_pkt *pktp, char *drv_name, int severity, int err_blkno, struct scsi_key_strings *cmdlist, struct scsi_extended_sense *sensep, struct scsi_asq_key_strings *asc_list, char **decode_fru struct scsi_device*, char *, int, char); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). PARAMETERS
The following parameters are supported: devp Pointer to the scsi_device(9S) structure. pktp Pointer to a scsi_pkt(9S) structure. drv_name String used by scsi_log(9F). severity Error severity level, maps to severity strings below. blkno Requested block number. err_blkno Error block number. cmdlist An array of SCSI command description strings. sensep A pointer to a scsi_extended_sense(9S) structure. asc_list A pointer to a array of asc and ascq message list.The list must be terminated with -1 asc value. decode_fru This is a function pointer that will be called after the entire sense information has been decoded. The parameters will be the scsi_device structure to identify the device. Second argument will be a pointer to a buffer of length specified by third argument. The fourth argument will be the FRU byte. decode_fru might be NULL if no special decoding is required. decode_fru is expected to return pointer to a char string if decoding possible and NULL if no decoding is possible. DESCRIPTION
This function is very similar to scsi_errmsg(9F) but allows decoding of vendor-unique ASC/ASCQ and FRU information. The scsi_vu_errmsg() function interprets the request sense information in the sensep pointer and generates a standard message that is dis- played using scsi_log(9F). It first searches the list array for a matching vendor unique code if supplied. If it does not find one in the list then the standard list is searched. The first line of the message is always a CE_WARN, with the continuation lines being CE_CONT. sensep may be NULL, in which case no sense key or vendor information is displayed. The driver should make the determination as to when to call this function based on the severity of the failure and the severity level that the driver wants to report. The scsi_device(9S) structure denoted by devp supplies the identification of the device that requested the display. severity selects which string is used in the Error Level: reporting, according to the table below: Severity Value: String: SCSI_ERR_ALL All SCSI_ERR_UNKNOWN Unknown SCSI_ERR_INFO Information SCSI_ERR_RECOVERED Recovered SCSI_ERR_RETRYABLE Retryable SCSI_ERR_FATAL Fatal blkno is the block number of the original request that generated the error. err_blkno is the block number where the error occurred. cmdlist is a mapping table for translating the SCSI command code in pktp to the actual command string. The cmdlist is described in the structure below: struct scsi_key_strings { int key; char *message; }; For a basic SCSI disk, the following list is appropriate: static struct scsi_key_strings scsi_cmds[] = { 0x00, "test unit ready", 0x01, "rezero/rewind", 0x03, "request sense", 0x04, "format", 0x07, "reassign", 0x08, "read", 0x0a, "write", 0x0b, "seek", 0x12, "inquiry", 0x15, "mode select", 0x16, "reserve", 0x17, "release", 0x18, "copy", 0x1a, "mode sense", 0x1b, "start/stop", 0x1e, "door lock", 0x28, "read(10)", 0x2a, "write(10)", 0x2f, "verify", 0x37, "read defect data", 0x3b, "write buffer", -1, NULL }; CONTEXT
The scsi_vu_errmsg() function may be called from user, interrupt, or kernel context. EXAMPLES
Example 1 Using scsi_vu_errmsg() struct scsi_asq_key_strings cd_slist[] = { 0x81, 0, "Logical Unit is inaccessable", -1, 0, NULL, }; scsi_vu_errmsg(devp, pkt, "sd", SCSI_ERR_INFO, bp->b_blkno, err_blkno, sd_cmds, rqsense, cd_list, my_decode_fru); This generates the following console warning: WARNING: /sbus@1,f8000000/esp@0,800000/sd@1,0 (sd1): Error for Command: read Error Level: Informational Requested Block: 23936 Error Block: 23936 Vendor: XYZ Serial Number: 123456 Sense Key: Unit Attention ASC: 0x81 (Logical Unit is inaccessable), ASCQ: 0x0 FRU: 0x11 (replace LUN 1, located in slot 1) SEE ALSO
cmn_err(9F), scsi_errmsg(9F), scsi_log(9F), scsi_errmsg(9F), scsi_asc_key_strings(9S), scsi_device(9S), scsi_extended_sense(9S), scsi_pkt(9S) Writing Device Drivers STREAMS Programming Guide SunOS 5.11 16 Jan 2006 scsi_vu_errmsg(9F)
All times are GMT -4. The time now is 11:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy