Sponsored Content
Operating Systems Linux 0: Failure: (138) Device does not have a disk-config Post 302931930 by Junaid Subhani on Friday 16th of January 2015 02:17:13 PM
Old 01-16-2015
RedHat 0: Failure: (138) Device does not have a disk-config

Hi guys,

Any idea why I am getting the below error ?


Code:
[root@alpha ~]# drbdsetup disk-options 0 --resync-rate=500M
0: Failure: (138) Device does not have a disk-config


Some info is;

Code:
[root@alpha ~]# fdisk -l

Disk /dev/sda: 64.4 GB, 64424509440 bytes
64 heads, 32 sectors/track, 61440 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0004c300

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           2         501      512000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2             502       61440    62401536   8e  Linux LVM
Partition 2 does not end on cylinder boundary.

Disk /dev/mapper/VolGroup-lv_root: 50.6 GB, 50553946112 bytes
255 heads, 63 sectors/track, 6146 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/VolGroup-lv_swap: 8405 MB, 8405385216 bytes
255 heads, 63 sectors/track, 1021 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/VolGroup-lv_home: 4936 MB, 4936695808 bytes
255 heads, 63 sectors/track, 600 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/sdb: 17.2 GB, 17179869184 bytes
64 heads, 32 sectors/track, 16384 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc753e10f

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       16384    16777200   83  Linux

Code:
[root@alpha ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
                       47G  2.6G   42G   6% /
tmpfs                 3.9G     0  3.9G   0% /dev/shm
/dev/sda1             485M   37M  423M   9% /boot
/dev/mapper/VolGroup-lv_home
                      4.6G  138M  4.2G   4% /home
/dev/sdb1              16G  172M   15G   2% /cluster

Regards,
Junaid
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Disk failure

is there anu way by which i can find out if all the disks on the system are working ? Milind Shauche. (2 Replies)
Discussion started by: shauche
2 Replies

2. UNIX for Dummies Questions & Answers

available disk space on disk device???

Hello, Can someone please tell me which command to use to determine the available disk space on a given disk device? I have to write a shell script that compresses files and stores them in a specific location but I am not sure how "conservative" I should be? Thanks in advance! Al. (4 Replies)
Discussion started by: alan
4 Replies

3. HP-UX

Disk Failure

I am new to being a Unix admin and have a question about replacing some hardware. I have a K class box using HP-UX 10.20 with three disks. Two of the drives are in one logical volume. Every 3 or 4 days, the syslog is showing that one of these drives is experiencing "POWERFAILED" and then recovering... (6 Replies)
Discussion started by: SemiOfCol
6 Replies

4. Filesystems, Disks and Memory

Looking for a solution to disk failure!

Hi people, I have been using my disk for quite a long time but the other day I heard the drive making some noise and had to restart the system again. But when I did that the disk would not boot and I fear that the data might be deleted or lost. So, if you people have any know about the ways to get... (1 Reply)
Discussion started by: adam466
1 Replies

5. Filesystems, Disks and Memory

Looking for a solution to disk failure!

Hi people, I have been using my disk for quite a long time but the other day I heard the drive making some noise and had to restart the system again. But when I did that the disk would not boot and I fear that the data might be deleted or lost. So, if you people have any know about the ways to... (2 Replies)
Discussion started by: christopher4
2 Replies

6. Solaris

SAN disk failure

hi all, have a solaris 9 OS and a SAN disk which used to work fine is not getting picked up by my machine. can anyone point out things to check in order to troubleshoot this ?? thanks in advance. (3 Replies)
Discussion started by: cesarNZ
3 Replies

7. Red Hat

How to monitor HP server hard disk failure ?

in red hat 4, 5 any one know any commands or any scritps to monitor HP DL 380 G5/6 server and trigger alarm when hard disk failed. thanks for all support ---------- Post updated at 02:45 PM ---------- Previous update was at 12:00 PM ---------- does HP ProLiant Support Pack support is... (4 Replies)
Discussion started by: maxlee24
4 Replies

8. Solaris

Poor disk performance however no sign of failure

Hello guys, I have two servers performing the same disk operations. I believe one server is having a disk's impending failure however I have no hard evidence to prove it. This is a pair of Netra 210's with 2 drives in a hardware raid mirror (LSI raid controller). While performing intensive... (4 Replies)
Discussion started by: s ladd
4 Replies

9. UNIX for Advanced & Expert Users

RAID5 multi disk failure

Hi there, Don't know if my title is relevant but I'm dealing with dangerous materials that I don't really know and I'm very afraid to mess anything up. I have a Debian 5.0.4 server with 4 x 1TB hard drives. I have the following mdstat Personalities : md1 : active raid1 sda1 sdd1... (3 Replies)
Discussion started by: chebarbudo
3 Replies

10. AIX

AIX hard disk failure

Hi all, I have encountered the issue with the hard disk, the disk is failed and need to replace by the new one. As my understanding, this is just to take out the failed disk and insert the new ones, and that's all. But the third party hardware vendor said, there should be another procedure... (9 Replies)
Discussion started by: Phat
9 Replies
fb.modes(5)						     Linux frame buffer utils						       fb.modes(5)

NAME
fb.modes - frame buffer modes file DESCRIPTION
/etc/fb.modes contains an unlimited number of video mode descriptions. The general format of a video mode is: mode geometry <xres> <yres> <vxres> <vyres> <depth> timings <pixclock> <left> <right> <upper> <lower> <hslen> <vslen> options <value> rgba <red,green,blue,alpha> endmode OPTIONS
geometry options: xres visible horizontal resolution (in pixels) yres visible vertical resolution (in pixels) vxres virtual horizontal resolution (in pixels) vyres virtual vertical resolution (in pixels) depth display depth (in bits per pixel) timing options: pixclock length of one pixel (in picoseconds) left left margin (in pixels) right right margin (in pixels) upper upper margin (in pixel lines) lower lower margin (in pixel lines) hslen horizontal sync length (in pixels) vslen vertical sync length (in pixel lines) rgba options (only valid with truecolor): red red color bitfields (in length or length/offset) green green color bitfields (in length or length/offset) blue blue color bitfields (in length or length/offset) alpha alpha color bitfields (in length or length/offset) other options: the first value of this options is the default hsync {low|high} the horizontal sync polarity vsync {low|high} the vertical sync polarity csync {low|high} the composite sync polarity gsync {low|high} the sync on green polarity bcast {false|true} enable or disable broadcast modes. If enabled the frame buffer generates the exact timings fot several broadcast modes (e.g. PAL or NTSC). Note that this option may not be supported by every frame buffer extsync {false|true} enable or disable external resync. If enabled the sync timings are not generated by the frame buffer device and must be pro- vided externally instead. Note that this option may not be supported by every frame buffer device laced {false|true} enable or disable interlace. If enabled the display will be split in two frames, each frame contains only even and odd lines respectively. These two frames will be displayed alternating, this way twice the lines can be displayed and the vertical fre- quency for monitor stays the same, but the visible vertical frequency gets halved double {false|true} enable or disable doublescan. If enabled every line will be displayed twice and this way the horizontal frequency can easily be doubled, so that the same resolution can be displayed on different monitors, even if the horizontal frequency specifica- tion differs. Note that this option may not be supported by every frame buffer device nostd <number> select nonstandard video mode accel {false|true} enable or disable hardware text acceleration grayscale {false|true} enable or disable graylevels instead of colors INTERNALS
Generally a frame buffer display is organized as follows: +---+---------------+---+---+ | | ^ | | | | | | 5 | | | | | v | | | +---#################---+---+ | # ^ # | | | # | # | | | # | # | | | 1 # | 2 # 3 | 4 | |<->#<------+------>#<->|<->| | # | # | | | # | 6 # | | | # | # | | | # v # | | +---#################---+---+ | | ^ | | | | | | 7 | | | | | v | | | +---+---------------+---+---+ | | ^ | | | | | | 8 | | | | | v | | | +---+---------------+---+---+ 1 left margin 2 xres 3 right margin 4 horizontal sync len 5 upper margin 6 yres 7 lower margin 8 vertical sync len The area bordered with `#' is the visible display area. Horizontal and vertical frequencies can now easily be calculated, for this the sum of horizontal or vertical values are important htotal = left + xres + right + hslen vtotal = upper + yres + lower + vslen The length of one line can now be calculated with pixclock line = pixclock * htotal and we have the horizontal frequency hfreq = 1E12 / line = 1E12 / (pixclock * htotal) To get the vertical frequency vtotal must eventually adjusted. If the display is laced, vtotal must be halved or if the display is a dou- blescan one, vtotal must be doubled. Now we can calculate the length of one frame if (lace) vtotal /= 2 if (double) vtotal *= 2 frame = vtotal * line and we get also the vertical frequency vfreq = 1E12 / frame = hfreq / vtotal SEE ALSO
fbset(8), fbdev(4) 2.1 2003-08-07 fb.modes(5)
All times are GMT -4. The time now is 08:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy