Sponsored Content
Full Discussion: dmesg error
Special Forums IP Networking dmesg error Post 31803 by PxT on Wednesday 13th of November 2002 02:53:34 PM
Old 11-13-2002
looks vaguely like a SCSI error. What type of machine? What OS? what kind of disks are attached?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

sun dmesg says

Oct 22 13:40:07 snmpdx: community_check() : bad community from Oct 22 13:40:07 snmpdx: session_open() failed for a pdu received from any help? thanks (4 Replies)
Discussion started by: yls177
4 Replies

2. UNIX for Dummies Questions & Answers

dmesg freebsd

hey,i use freeBSD 4.7stable, dmesg returns me a tons of info like: ax R *Handler Int 16 aio_max R *Handler Int 17 aio_prio_delta_max R *Handler Int 18 delaytimer_max R *Handler Int 19 mq_open_max R *Handler Int 20 pagesize R *Handler Int 21 rtsig_max R *Handler Int... (6 Replies)
Discussion started by: hachik
6 Replies

3. UNIX for Dummies Questions & Answers

dmesg error

hi, when i do a "dmesg" command, i saw many of this message appeared. Nov 12 07:00:20 catty graph_ftp: graph_ftp ftp faild it seems like it has some problems with my gftp application? pls tell me what's wrong and how to solve it. thanks alot. (1 Reply)
Discussion started by: champion
1 Replies

4. HP-UX

dmesg error ??

Hi all, I have a very weard error message in my dmesg output, and I cannot find the solution in google. Does anyone know what it might be ? Equivalently mapped reserve pool exhausted; Overall application performance may be improved by increasing the "eqmemsize" tunable parameter (currently... (3 Replies)
Discussion started by: davidg
3 Replies

5. Slackware

Printer (dmesg) error

I am setting up a printer for a friend. I've built the box using (Gnu/Linux), Slackware-current, Kernel 2.6.7. I have the same setup. Currently the only way I have access to my friends machine is across the Internet via SSH, so I'm unable to manually check cabling at the moment. On my Slackware... (0 Replies)
Discussion started by: locustfurnace
0 Replies

6. Linux

dmesg error

hi all, this is my permenent error.how to clear this error permenently... please help me out. here is my error output. please tell me clearly as i am very new to Linux(beginner) hda: packet command error: status=0x51 { DriveReady SeekComplete Error } hda: packet command error:... (2 Replies)
Discussion started by: rrlog
2 Replies

7. BSD

dmesg giving errors

When running dmesg, the output is a long list of the following: ACPI Error: No object attached to node 0xffffff00016622e0 20090521 exresnte-211 ACPI Error (uteval-0329): Method execution failed (Node 0xffffff00016622e0), AE_AML_NO_OPERAND As a workaround I resort to sysctl, which gives... (0 Replies)
Discussion started by: figaro
0 Replies

8. HP-UX

Dmesg with date possible?

Hi there, I miss date information when executing # dmesg Is it possible to add this a date information to my results of # dmesg ? Best wishes (12 Replies)
Discussion started by: System
12 Replies

9. Red Hat

Dmesg with Date and Time

Dear All, I am looking to enable Date and time in dmesg output for for centos 5.8. Unfortunately the current version doesn't support -T option. Also i am looking for solutions which can enable the date& time via kernal or updating the dmesg utility. or maybe via single command line. ... (3 Replies)
Discussion started by: pistachio
3 Replies

10. Red Hat

Dmesg errors

Dear All , Very recently I find there are a lot of I/O errors in our Red HAt Linux Server. Pl find the below end_request: I/O error, dev sdcp, sector 0 sd 7:0:0:32784: SCSI error: return code = 0x00010000 end_request: I/O error, dev sdn, sector 0 sd 7:0:0:33289: SCSI error: return... (7 Replies)
Discussion started by: jegaraman
7 Replies
SCSI(7) 						 Miscellaneous Information Manual						   SCSI(7)

NAME
SCSI, RAID - Small Computer System Interface SYNOPSIS
dsk#, tape#_d#, cdrom# DESCRIPTION
The operating system interfaces to disk and tape devices through the Small Computer System Interface (SCSI). SCSI support is limited to the Compaq-supplied storage devices and certain third-party devices. To determine which named devices are supported in the default system, refer to the file /etc/ddr.dbase. For example, the following devices are listed therein: Winchester disks: RZ24L, RZ25, RZ25L, RZ25M, RZ28M, RZ29B, RZ55, RZ56, RZ58, RZ73, RZ74, RX23, RX26, RX33, IOMEGA ZIP, RAID (Redundant Arrays of Independent Disks) SCSI controllers: HSZ10, HSZ40, HSZ80 Magnetic tapes: TZ30, TZK11, TLZ06, TKZ09, TKZ60, DLT8000, SDT-10000 Media Changers: TL800, ESL9000 Optical disks: RRD42, RRD43, RRD44 Vendors can add their own devices to ddr.dbase. Refer to the Software Product Description (SPD) for a given release of the operating system for more information on processor-specific device support. Under the operating system, a SCSI device is referred to by a device identifier that is assigned by the operating system. This name has no relationship to the descriptive name of the device, although in previous releases of the operating system disks such as the RZ74 mapped to a system-assigned rz# logical name (where # was the instance number of that disk. Current logical names for SCSI disks and tapes take the forms specified in the rz(8) and tz(7) reference pages, such as dsk? and tape?. Refer to the dsfmgr(8) reference page for the naming conventions for disks, tapes and other devices, such as CD-ROM readers. Refer to the hwmgr(8) reference page for information on determining device names and other device data. SCSI Device Limits The number of possible target device IDs is determined by the controller type and method of connection, such as a multibus connection using fibre channel. Refer to the emx(7) reference page for an example of device addressing. Device Special Files The dsfmgr command creates device special files for all the devices that are attached to SCSI controllers. This event occurs automatically on system startup, and no administrative intervention is required unless an event requires that a device be renamed or its I/O be reas- signed. In such cases, you can use dsfmgr and hwmgr to manage SCSI devices and their associated device special files without the need to calculate values from their Bus, Target ID, and LUN data. RESTRICTIONS
The SCSI device driver is not warrantied to operate with optical disks other than the devices listed in /etc/ddr.dbase/. The SCSI driver attempts to support, on a best-effort basis, disks and magnetic tapes supplied by other vendors. The following notes apply to the driver's handling of disks from other vendors: These disks are identified using the following command: # hwmgr -get attribute -a name This command will return the device name SCSI-WWID (World-Wide Identifier) for all devices on the system, which includes the model name of the device. You can filter the output by specifying categories of devices. Disks are assigned a default partition table. The default table can be modified by editing the ccmn_rzxx_sizes[8] entry in the /usr/sys/data/cam_data.c file. The disklabel command can also be used to modify the partition table on an RZxx disk. RELATED INFORMATION
atapi_ide(7), dsfmgr(8), emx(7), hwmgr(8), rz(7), tz(7), disklabel(8), ddr.dbase(4) delim off SCSI(7)
All times are GMT -4. The time now is 07:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy