Sponsored Content
Operating Systems Solaris Boot issues Solaris 10 + V440 Post 302422370 by bluescreen on Tuesday 18th of May 2010 08:18:48 AM
Old 05-18-2010
Quote:
Originally Posted by stoci
Code:
Bad magic number in disk label
Can't open disk label package

It could be that your install dvd is corrupted. Can you try another dvd?


Yes, you should be able to boot even though the key is in diag mode - it just take longer.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solaris boot issues

i'm having 2 problems. 1. the system will always look to boot from the net. i've changed the prom settings so that it boots from the disk, by entering "setenv boot-device disk0:3", but the system still seems to want to boot from the net. 2. i replaced my creator3d with an elitem6 and i did... (6 Replies)
Discussion started by: xyyz
6 Replies

2. Solaris

Solaris box V440 got stucked

Hi Friends, My solaris box V440 got stucked. I couldn't accessit from the remote console. Finally i restarted the box. Can you tell me what are the ways we can find out the issues and what are the logs we can check other than /var/log/messages. Thanks Jinu (1 Reply)
Discussion started by: Jinu
1 Replies

3. Solaris

Windows,Solaris, Red Hat triple boot issues

I have a pentium IV with 512 MB ram and 80 GB HDD. I first installed windows XP on the first primary partition, then Solaris on the second with 20 GB for the solaris partition, and when rebooted , the grub menu functioned as expected giving me the options to dual boot, so next I wanted to install... (3 Replies)
Discussion started by: saagar
3 Replies

4. Solaris

Firmware password Solaris Sun Fire v440

Hi: I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies

5. Solaris

SAS drive USB caddy on Solaris V440

Got a T2000 which has got the 2.5" SAS drives. Want to be able, if I can, to connect to USB caddy and connect to a V440. Anyone ever tried this? To be honest, having problems even finding a SAS-USB caddy. (0 Replies)
Discussion started by: psychocandy
0 Replies

6. Solaris

Sun-Fire V440 boot disk issue

Hi, I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken. Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies

7. Solaris

Solaris V440 keeps crashing

Hi, I have Sun Solaris V440, every two days or so, the system crashes and it's at OK prompt. After that I do the FSCK and clear all the bad sectors. Then system stays up for close to 48 hours. Then it crashes again. I checked the logs and I don't see anything under /var/adm/messages file. ... (1 Reply)
Discussion started by: samnyc
1 Replies

8. Solaris

Removing a disk from SUN Fire V440 running Solaris 8

Hi, I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either. Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies

9. Solaris

Auto Power On on V440 Solaris system

Hi there, I have a V440 Server based on Sun Microsystem with Solaris OS. Is there any way to auto power on the system only with cabling the V440 with 220 v? Thanks! (10 Replies)
Discussion started by: proof_enrique
10 Replies

10. Red Hat

Boot Issues

I am installing Red Hat Linux 6.9 as a VM in Hyper-V on an HP laptop running Windows 10. After the install completes and the VM reboots, it gives me the message, "Detected CPU Family 6 model 142; Warning: Intel CPU model - this hardware has not undergone testing by Red Hat and might not be... (1 Reply)
Discussion started by: tigers580307
1 Replies
dad(7D) 							      Devices								   dad(7D)

NAME
dad - driver for IDE disk devices SYNOPSIS
dad@ target,lun:partition DESCRIPTION
This driver handles the ide disk drives on SPARC platforms. The type of disk drive is determined using the ATA IDE identify device command and by reading the volume label stored on block 0 of the drive. The volume label describes the disk geometry and partitioning; it must be present or the disk cannot be mounted by the system. The block-files access the disk using the system's normal buffering mechanism and are read and written without regard to physical disk records. There is also a "raw" interface that provides for direct transmission between the disk and the user's read or write buffer. A single read or write call usually results in one I/O operation; raw I/O is therefore considerably more efficient when many bytes are trans- mitted. The names of the block files are found in /dev/dsk; the names of the raw files are found in /dev/rdsk. I/O requests to the raw device must be aligned on a 512-byte (DEV_BSIZE) boundary and must have a length that is a multiple of 512 bytes. Requests which do not meet the restrictions will cause the driver to return an EINVAL error. I/O requests to the block device have no alignment or length restrictions. Device Statistics Support Each device maintains I/O statistics both for the device and for each partition allocated on that device. For each device/partition, the driver accumulates reads, writes, bytes read, and bytes written. The driver also takes hi-resolution time stamps at queue entry and exit points, which facilitates monitoring the residence time and cumulative residence-length product for each queue. Each device also has error statistics associated with it. These must include counters for hard errors, soft errors and transport errors. Other data may be implemented as required. FILES
/dev/dsk/cntndnsn block files /dev/rdsk/cntndnsn raw files where: cn controller n tn IDE target id n (0-3) dn Always 0. sn partition n (0-7) The target ide numbers are assigned as: 0 Master disk on Primary channel. 1 Slave disk on Primary channel. 2 Master disk on Secondary channel 3 Slave disk on Secondary channel. IOCTLS
Refer to dkio(7I). ERRORS
EACCES Permission denied. EBUSY The partition was opened exclusively by another thread. EFAULT The argument was a bad address. EINVAL Invalid argument. EIO An I/O error occurred. ENOTTY This indicates that the device does not support the requested ioctl function. ENXIO During opening, the device did not exist. EROFS The device is a read-only device. SEE ALSO
format(1M), mount(1M), lseek(2), read(2), write(2), driver.conf(4), vfstab(4), dkio(7I) X3T10 ATA-4 specifications. DIAGNOSTICS
Command:<number>, Error:<number>, Status:<number> Indicates that the command failed with an error and provides status register contents. Where <number> is a hexadecimal value. offline The driver has decided that the target disk is no longer there. disk ok The target disk is now responding again. corrupt label - bad geometry The disk label is corrupted. corrupt label - label checksum failed The disk label is corrupted. corrupt label - wrong magic number The disk label is corrupted. disk not responding to selection The target disk is not responding. i/o to invalid geometry The geometry of the drive could not be established. incomplete read/write - retrying/giving up There was a residue after the command completed normally. no bp for disk label A bp with consistent memory could not be allocated. no memory for disk label Free memory pool exhausted. ATA transport failed: reason 'nnnn': {retrying|giving} The host adapter has failed to transport a command to the target for the reason stated. The driver will either retry the command or, ultimately, give up. corrupt label - wrong magic number The disk label is corrupted. corrupt label - label checksum failed The disk label is corrupted. corrupt label - bad geometry The disk label is corrupted. no mem for property Free memory pool exhausted. transport rejected (<n>) Host adapter driver was unable to accept a command. Device Fault There has been a Device Fault - reason for such error is vendor specific. SunOS 5.10 15 Mar 2004 dad(7D)
All times are GMT -4. The time now is 07:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy