07-23-2009
you must boot into single user mode,
then run fdisk -l, this will give you a list of your disks, then fsck the disk... they could be like /dev/sda or /dev/hda.
the reason you dont see anything is because it appears the fs is readonly can you confirm?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Anyone would know how to get rid off a message that comes up during a boot-up on Solaris? It says that the clusters for this software are not installed. I deleted the software because it was crashing some other stuff but it did not get rid off all the stuff.
Yes, I am coming from windows and... (2 Replies)
Discussion started by: softarch
2 Replies
2. Solaris
(Solaris 8, 4 cpu's)
When I look at my boot messages (/var/adm/messages or dmesg) I noticed the following:
Sep 23 08:53:00 server1 unix: cpu0: SUNW,UltraSPARC-II (upaid 0 impl 0x11 ver 0xa0 clock 450 MHz)
Sep 23 08:53:00 server1 unix: cpu1: SUNW,UltraSPARC-II (upaid 1 impl 0x11 ver... (1 Reply)
Discussion started by: finster
1 Replies
3. Linux
Where do all those messages at boot time get stored / logged?
like:
starting eth0 : OK
starting mysql : OK
etc... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
4. AIX
hi all
i just found one of my p650 server showing a warning message when i
tried to run bosboot command after upgrading TL to AIX 530803.
i also tried to run chpv -c hdisk0 and chpv -c hdisk1 to clear out the
old boot info in hdisk0 and hdisk1 and rerun bosboot -a. it still
showed... (0 Replies)
Discussion started by: rs6000er
0 Replies
5. Red Hat
Hi Guys :)
I am finding out the way to use mondorestore via command line only, no GUI.
I am able to use mondoarchive in the same way but not mondorestore.
can anybody help me out.... Thanks in advance!
halides:b: (0 Replies)
Discussion started by: halides
0 Replies
6. Filesystems, Disks and Memory
Hello All,
I backed up my RHEL 4 as an image.
Then I restored the image on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4.
The messages that are shown when the system boots are something like-
" .....
EXT3-fs:... (2 Replies)
Discussion started by: shamik
2 Replies
7. Shell Programming and Scripting
Hi All,
I have to work in the late nights some times for server maintenance and in a hurry to complete I am accidentally changing ownership or permission of directories :(
which have similar names ( /var in root and var of some other directory ).:confused:
Can some one suggest me with the... (1 Reply)
Discussion started by: shiek.kaleem
1 Replies
8. Red Hat
I am trying to understand what are the differences of boot messages verbosity levels for the kernel field in grub.conf
From my research, there appear to be three levels:
quiet
verbose
debug
I have also found documents that specify removing quiet from the kernel field. If this is done, is... (1 Reply)
Discussion started by: thaebich
1 Replies
9. Red Hat
Heyas
So i have my custom Fedora with AwesomeWM spin with alots of customizations using the kickstart method for a liveimage.
A few weeks (2-3 months) ago, i've done some changes i cannot remember.
Those changes made the image from bootable to gui, to not booting to gui any more.
Just... (3 Replies)
Discussion started by: sea
3 Replies
10. Red Hat
Hi all
Many years ago, I found online this script that was incredibly funny and I had blogged it
Unfortunately because of my poor record-keeping, I seem to have lost the shell script
Would somebody be kind enough to tell me how to replicate this?
Thank you! (0 Replies)
Discussion started by: hedkandi
0 Replies
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 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; the names of the raw files 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.
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-7)
sn UNIX system slice n (0-15)
pn fdisk partition(0)
/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.10 9 Oct 2004 cmdk(7D)