What I'm Doing:
I'm developing a python script that scans for all storage devices and their respective sizes. Python does not have a command that returns the /dev paths of storage devices or the respective sizes. So, I need to pipe a shell command to python.
The Problem:
In root, I've used fdisk to get all storage device paths and their respective sizes and send that to a file that python can open to retrieve the path and size info. Here is what fdisk sends to a file:
Code:
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8941fb29
Device Boot Start End Blocks Id System
/dev/sda1 * 1 12748 102398278+ 83 Linux
/dev/sda2 37811 38913 8859847+ 5 Extended
/dev/sda3 12749 20397 61440592+ 83 Linux
/dev/sda4 25497 37810 98912205 83 Linux
/dev/sda5 37811 38913 8859816 82 Linux swap / Solaris
Partition table entries are not in disk order
Disk /dev/sdb: 126 MB, 126779392 bytes
4 heads, 61 sectors/track, 1014 cylinders
Units = cylinders of 244 * 512 = 124928 bytes
Disk identifier: 0x5b1b8282
Disk /dev/sdc: 2004 MB, 2004877312 bytes
255 heads, 63 sectors/track, 243 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000a8c94
Device Boot Start End Blocks Id System
/dev/sdc1 1 243 1951866 83 Linux
My Question
Is there a way to grep this info so that the paths and their respectives sizes are returned? Or, for anyone who understands what I'm trying to achieve here, could you offer some other solution besides an attempt to grep?
Dear linuxers,
I have a usb mess storage device.
My OS is rh as3 update2.
Each time I use the command
mount -t vfat /dev/sda1 /mnt/usb
I got the error "the device is not a valid block device".
I found from google that I should install the module sd_mod
I use the command
insmod sd_mod... (2 Replies)
Hello,
I have a sun blade 100 with solaris 10 and am perplexed by the instances of devices that I see when I attach a usb flash stick to one of the ports in the back of the chassis.
Here is what I see for USB storage in /etc/path_to_inst:
"/pci@1f,0/usb@c,3/storage@3" 0 "scsa2usb"... (0 Replies)
Have connected a non-IBM storage device to AIX host via fibre channel. If the storage is rebooted or a raid controller fails over whilst connected to the host, the paths that drop do not come back online when the ports become active again.
I have tried enabling dynamic tracking and delayed_fail... (3 Replies)
Hello,
I've been searching your forum for an answer to the following question and whilst I've seen several which may help I'm afraid my inexperience with UNIX systems has got the better of me and I'm incapable of piecing your considerable expertise together.
Problem:
I have a linux box which... (5 Replies)
I need a way to reliably detect a USB storage device from a bash script. I know how to use 'lsusb' to list the USB devices - but then how can I match a device listed in 'lsusb' output to an actual disk device? Is there some way to map one to the other?
Any help appreciated. (3 Replies)
I want example of a file representing the hard disk storage device In UNIX ? (6 Replies)
Discussion started by: tamer11007
6 Replies
LEARN ABOUT DEBIAN
fdisk
CFDISK(8) GNU fdisk Manual CFDISK(8)NAME
GNU fdisk, lfdisk, gfdisk - manipulate partition tables on a hard drive
SYNOPSIS
fdisk [options] [device]
DESCRIPTION
fdisk is a disk partition manipulation program, which allows you to create, destroy, resize, move and copy partitions on a hard drive using
a menu-driven interface. It is useful for organising the disk space on a new drive, reorganising an old drive, creating space for new oper-
ating systems, and copying data to new hard disks. For a list of the supported partition types, see the --list-partition-types option
below.
It comes in two variants, gfdisk and lfdisk. Lfdisk aims to resemble Linux fdisk 2.12, while gfdisk supports more advanced disk operations,
like resizing the filesystem, moving and copying partitions. When starting fdisk, the default is to run gfdisk.
OPTIONS -h, --help
displays a help message.
-v, --version
displays the program's version.
-L, --linux-fdisk
turns on Linux fdisk compatibility mode. This is the same as running lfdisk.
-G, --gnu-fdisk
turns off Linux fdisk compatibility mode.
-i, --interactive
where necessary, prompts for user intervention.
-p, --script
never prompts for user intervention.
-l, --list
lists the partition table on the specified device and exits. If there is no device specified, lists the partition tables on all
detected devices.
-r, --raw-list
displays a hex dump of the partition table of the disk, similar to the way Linux fdisk displays the raw data in the partition table.
-u, --sector-units
use sectors, instead of cylinders for a default unit.
-s, --size=DEVICE
prints the size of the partition on DEVICE is printed on the standard output.
-t, --list-partition-types
displays a list of supported partition types and features.
The following options are available only to lfdisk.
-b, --sector-size=SIZE
Specify the sector size of the disk. Valid values are 512, 1024 and 2048. Should be used only on older kernels, which don't guess
the correct sector size.
-C, --cylinders=CYLINDERS
Specify the number of cylinders of the disk. Currently does nothing, it is left for Linux fdisk compatibility.
-H, --heads=HEADS
Specify the number of heads of the disk. Reasonable values are 255 or 16.
-S, --sectors=SECTORS
Specify the number of sectors per track. A reasonable value is 63.
BUGS
Before editing a BSD disklabel, the partition with the disklabel should already exist on the disk and be detected by the OS. If you have
created a BSD-type partition, you need to write the changes to the disk. If fdisk fails to notify the OS about the changes in partition ta-
ble, you need to restart your computer. As fdisk tries to guess the device holding the BSD disklabel, it might fail to edit it at all, even
if the OS has detected it. In this case you are adviced to simply open the device with fdisk directly. It is possible that it doesn't work
on some operating systems.
Getting the size of a partition with -s might fail, if fdisk fails to guess the disk device, for the same reasons as with the previous bug.
SEE ALSO mkfs(8), cfdisk(8), parted(8) The fdisk program is fully documented in the info(1) format GNU fdisk User Manual manual.
fdisk 18 August, 2006 CFDISK(8)