Its regarding boot block Post: 302080983

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Cannot boot - Boot : Panic : File size out of range (EWS-UX/V unix)

Hey ! I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range. According to user guide, this error is occuring when a file exceeding the limit and/or...

2. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading...

3. Solaris

cannot find boot device and won't boot off cdrom

I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me...

4. Solaris

Boot block corrupted then how can i solve that

HI every one, i need some information that is if any boot block is corrupted den we have to go to ok prompt then boot from cdrom or network if ok prompt also not working at dat time wat i have to do .please any one can help me . Thanking for reply

5. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and...

6. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD...

7. News, Links, Events and Announcements

MS to block linux boot

Microsoft to stop Linux, older Windows, from running on Windows 8 PCs | ZDNet isn't that deserve an anti trust investigation? MS monopoly is transfer into the hardware.

8. Solaris

Verification of the Boot Block

Guys, I have a rusty question that I need help with. It has been a while since I supoprted Solaris boxes. I have several hundred solaris systems running Sol 8 and Sol 10. I built the original 250 but they have added several hundred more and I am seeing issues with these boxes that I need to...

9. Solaris

How to cross check created boot block in second disk

Hi All, I have copied a existing root file system from c0t0d0 to c0t1d0 in SUN Fire 6800 by using the below command, ufsdump 0ucf - / | (cd /new.root ; ufsrestore -rf - ) and later on I created a boot block on c0t1d0s0 by using the below command installboot /usr/platform/`uname...

LEARN ABOUT OPENSOLARIS

cmdk

cmdk(7D)							      Devices								  cmdk(7D)

NAME

       cmdk - common disk driver

SYNOPSIS

       cmdk@target, lun : [ partition | slice ]

DESCRIPTION

       The  cmdk  device  driver  is  a  common interface to various disk devices. The driver supports magnetic fixed disks and magnetic removable
       disks.

       The cmdk device driver supports three different disk labels: fdisk partition table, Solaris x86 VTOC and EFI/GPT.

       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 sin-
       gle read or write call usually results in one I/O operation; raw I/O is therefore considerably more efficient when many bytes are transmit-
       ted. The names of the block files are found in /dev/dsk. Raw file names are found in /dev/rdsk.

       I/O  requests  to the magnetic disk must have an offset and transfer length that is a multiple of 512 bytes or the driver returns an EINVAL
       error.

       Slice 0 is normally used for the root file system on a disk, slice 1 as a paging area (for example, swap), and slice 2 for backing  up  the
       entire fdisk partition for Solaris software. Other slices may be used for usr file systems or system reserved area.

       The fdisk partition 0 is to access the entire disk and is generally used by the fdisk(1M) program.

FILES

       /dev/dsk/cndn[s|p]n	 block device (IDE)

       /dev/rdsk/cndn[s|p]n	 raw device (IDE)

				 where:

				 cn    controller n.

				 dn    lun n (0-1).

				 sn    UNIX system slice n (0-15).

				 pn    fdisk partition (0-36).

       /kernel/drv/cmdk 	 32-bit kernel module.

       /kernel/drv/amd64/cmdk	 64-bit kernel module.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Architecture		     |x86			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       fdisk(1M), mount(1M), lseek(2), read(2), write(2), readdir(3C), scsi(4), vfstab(4), attributes(5), dkio(7I)

SunOS 5.11							    4 Nov 2008								  cmdk(7D)