05-06-2010
Unfortunately I have no experience of v3...
But based on old issues I had to deal with, two things come to mind:
a new kernel (but too big to boot...)
someone got the disks puzzled (conflicting, you know like 2 devices with same SCSI ID...)
My 2 cents
Good luck...
I will keep you informed if I can think of anything else, but I am in a big porting phase and should be in production next week so have not much time to spare...
9 More Discussions You Might Find Interesting
1. SCO
I tried to add ppp on a serial line tty1b and I relink the kernel. Now, I would like to boot from the previous kernel because I lost the connexion for the others terminal (serial lines) too.
I would appreciate any help. (3 Replies)
Discussion started by: pacctono
3 Replies
2. BSD
Salamo Alikom after recompilation my kernel does not boot and display msg said : enter full path to bash : /bin/sh i try fsck -r ,fsck -y but the problem is steel . my make.conf : PERL_VER=5.8.8 OVERRIDE_LINUX_BASE_PORT=f8 PERL_VERSION=5.8.8 MODULES_OVERRIDE = linux acpi accf_http pccard msdosfs... (1 Reply)
Discussion started by: SIFE
1 Replies
3. HP-UX
Hi gurus,
I was more on the Sun side and now am getting exposure to the HP-UX side of the world. I have to upgrade firmware on BL870c blade.
Can some one point to a url or give procedure to follow as I couldn't find much on the web.
Thanks
Momin (1 Reply)
Discussion started by: momin
1 Replies
4. UNIX for Dummies Questions & Answers
I compiled new kernel in linux 10.04 called linux-2.6.26.8-xenomai, it runs alongside the other kernel, but when I want to boot it I get an error message saying:
Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/sda5 does not exist.
After making the modules and headers
I made the... (4 Replies)
Discussion started by: mdop
4 Replies
5. Ubuntu
Hello Everyone,
First of all, I highly appreciate all Linux forum members and whole Linux community. http://forums.linuxmint.com/images/smilies/icon_wink.gif. I wish you the best for all of you !
I will try to be short and concise: I am using Linux Mint 10 for 2 months on 2 ws, and all went... (3 Replies)
Discussion started by: cdt
3 Replies
6. Red Hat
Hello, everyone.
I am using Fedora 15, and want to upgrade to version 16. I follow the official link Upgrading Fedora using yum - FedoraProject to upgrade my OS by the following command:
yum update kernel* --releasever=16
yum groupupdate Base --releasever=16
reboot
After reboot, OS... (2 Replies)
Discussion started by: 915086731
2 Replies
7. 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
8. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
9. UNIX for Advanced & Expert Users
I'm writing a simple USB driver to drive a stepper motor based on USB Skeleton 2.2 Driver, kernel 3.8. The basic version is running properly. As a advancement, I introduced KTHREAD to call the DEVICE_WRITE (skel_write) (), so that the driver will be available for other tasks & requests.
Calling... (0 Replies)
Discussion started by: miteshgaware
0 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)