Udev list disks

Hello DBA's / UNIX Admins ,
Can you help me find out the command in udev to list the disks that are created for asm . Say for eg: if i have used asmlib to create the disks then i would use "/etc/init.d/oracleasm listdisks " to list the disks .
And also i would like the find out from which sd* device the asmdisk is created . I have the script for finding that output for asmlib which will return output as "ASM disk "VOL1" based on /dev/sdg1 [8, 97]" . Please help me for find the same for udev .
Thanks
Venkat

You may have setup udev rules to set device ownerships, but as far as I know there is no udev "command" to list ASM disks.
If you use Oracle ASMLib you can use:
<pre>
/etc/init.d/oracleasm querydisk -p VOL1
Disk "VOL1" is a valid ASM disk
/dev/sdb1: LABEL="VOL1" TYPE="oracleasm"
</pre>
If you don't use Oracle ASMLib, you can query the +ASM instance.
<pre>
sqlplus / as sysasm
SQL> SELECT name, header_status, path FROM V$ASM_DISK;
</pre>

Similar Messages

  • System Events equivalent to "list disks"

    I would like to mount a network share via AFP, but before doing so, I just want to check to see if it is mounted.
    In my AppleScript 1-2-3 book, it tells me there is a command called "list disks"  when I execute it:
    list disks
    -- returns {"Macintosh HD", "A Disk Name Here", "A USB Drive Name there", "A Network Drive Name over here"}
    basically, it works properly.
    Now, in the book and on Apples's own site it says that "list disks is deprecated" and to use "System Events" instead.  It even gives me a sample command to try:
    tell application "System Events" to get the name of every disk
    it is supposed to return the same list as the command "list disks", but in my case, it errors out with an error message of -1000
    What am I missing here?  I literally cut and pasted the command so I wouldn't make a mistake.

    It works now....
    I would type that exact command in
    tell application "System Events" to get the name of every disk
    and it would throw an -1000 error at me.  I even had a friend watch me to see if I was missing anything, but it still failed.  However, I did a reboot for something unrelated, and it started working.
    However, it's a moot point.  I had a really bodgy workaround going but the whole script would stop functioning when the screen saver activated which is not what I wanted. 
    So, in the end, I had to write a bash script so that it would run whether or not I was at the computer.  It actually seems to work better in bash than in AS. 

  • Unable to retrieve device ID with udev daemon

    I've recently switched from Ubuntu to Arch (did not regret it yet ). Currently, I'm trying to set up a backup. I have not done anything like that before so I cannot tell if my problem is Arch-specific but I guess, it's not.
    Since I want to backup to an external HDD with no permanent connection to my laptop, I want a backup script to be triggered each time when the HDD is plugged in. So I created an udev rule in /etc/udev/rules.d/10-local.rules (had to created that file since this directory was empty):
    ACTION=="add", SYSFS{idVendor}=="04e8", SYSFS{idProduct}=="60a6", RUN+="/usr/local/bin/makebak.sh"
    What this rule should do: Execute the script makebak.sh each time I plug in the device with vendor ID 04e8 and product ID 60a6.
    What this rule does: Nothing.
    The output of lsusb for the device in question is
    Bus 002 Device 014: ID 04e8:60a6 Samsung Electronics Co., Ltd
    I tested some things:
    1. It works if I try ACTION=="add", RUN+="/usr/local/bin/makebak.sh", but then the script is executed something like 10 times for each device I plug in. This rule is just too generic. But it proves that udev seems unable to find the device ID.
    2. I've found the command udevadm test that shows me some info about my device. However, the output is different if I execute it as root. I noticed that as root there are no informations concerning the vendor and the product id, but as regular user I can see them listed. I don't really know what this tool does but could the reason why my udev rule doesn't work be connected with that observation?
    Here is the output of udevadm test /sys/block/sdb as regular user:
    run_command: calling: test
    adm_test: version 180
    This program is for debugging only, it does not run any program,
    specified by a RUN key. It may show incorrect results, because
    some values may be different, or not available at a simulation run.
    builtin_kmod_init: load module index
    add_matching_files: unable to open '/run/udev/rules.d': No such file or directory
    parse_file: reading '/lib/udev/rules.d/10-dm.rules' as rules file
    parse_file: reading '/etc/udev/rules.d/10-local.rules' as rules file
    parse_file: reading '/lib/udev/rules.d/11-dm-lvm.rules' as rules file
    parse_file: reading '/lib/udev/rules.d/13-dm-disk.rules' as rules file
    parse_file: reading '/lib/udev/rules.d/40-gphoto.rules' as rules file
    add_rule: IMPORT found builtin 'usb_id --export %p', replacing /lib/udev/rules.d/40-gphoto.rules:11
    parse_file: reading '/lib/udev/rules.d/42-qemu-usb.rules' as rules file
    parse_file: reading '/lib/udev/rules.d/50-udev-default.rules' as rules file
    parse_file: reading '/lib/udev/rules.d/53-sane.rules' as rules file
    (... much more rules parsing ...)
    udev_rules_new: rules use 216120 bytes tokens (18010 * 12 bytes), 28505 bytes buffer
    udev_rules_new: temporary index used 52000 bytes (2600 * 20 bytes)
    udev_device_new_from_syspath: device 0x155b6d0 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb'
    udev_device_new_from_syspath: device 0x156ade0 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb'
    udev_device_read_db: device 0x156ade0 filled with db file data
    udev_rules_apply_to_event: RUN '/usr/local/bin/makebak.sh' /etc/udev/rules.d/10-local.rules:1
    udev_device_new_from_syspath: device 0x155d490 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0'
    udev_device_new_from_syspath: device 0x155dc90 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0'
    udev_device_new_from_syspath: device 0x155e480 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16'
    udev_device_new_from_syspath: device 0x155ec60 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0'
    udev_device_new_from_syspath: device 0x155f420 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1'
    udev_device_new_from_syspath: device 0x155fc00 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2'
    udev_device_new_from_syspath: device 0x15603d0 has devpath '/devices/pci0000:00/0000:00:1d.7'
    udev_device_new_from_syspath: device 0x1560b70 has devpath '/devices/pci0000:00'
    udev_rules_apply_to_event: GROUP 6 /lib/udev/rules.d/50-udev-default.rules:67
    udev_rules_apply_to_event: IMPORT 'ata_id --export /dev/sdb' /lib/udev/rules.d/60-persistent-storage.rules:37
    udev_event_spawn: starting 'ata_id --export /dev/sdb'
    spawn_wait: 'ata_id --export /dev/sdb' [2250] exit with return code 1
    udev_rules_apply_to_event: IMPORT builtin 'usb_id' /lib/udev/rules.d/60-persistent-storage.rules:39
    builtin_usb_id: /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0: if_class 8 protocol 6
    udev_builtin_add_property: ID_VENDOR=Samsung
    udev_builtin_add_property: ID_VENDOR_ENC=Samsung\x20
    udev_builtin_add_property: ID_VENDOR_ID=04e8
    udev_builtin_add_property: ID_MODEL=S2_Portable_3
    udev_builtin_add_property: ID_MODEL_ENC=S2\x20Portable\x203\x20\x20\x20
    udev_builtin_add_property: ID_MODEL_ID=60a6
    udev_builtin_add_property: ID_REVISION=2AM1
    udev_builtin_add_property: ID_SERIAL=Samsung_S2_Portable_3_000000000000011E0A60-0:0
    udev_builtin_add_property: ID_SERIAL_SHORT=000000000000011E0A60
    udev_builtin_add_property: ID_TYPE=disk
    udev_builtin_add_property: ID_INSTANCE=0:0
    udev_builtin_add_property: ID_BUS=usb
    udev_builtin_add_property: ID_USB_INTERFACES=:080650:
    udev_builtin_add_property: ID_USB_INTERFACE_NUM=00
    udev_builtin_add_property: ID_USB_DRIVER=usb-storage
    udev_rules_apply_to_event: LINK 'disk/by-id/usb-Samsung_S2_Portable_3_000000000000011E0A60-0:0' /lib/udev/rules.d/60-persistent-storage.rules:44
    udev_rules_apply_to_event: IMPORT builtin 'path_id' /lib/udev/rules.d/60-persistent-storage.rules:61
    udev_builtin_add_property: ID_PATH=pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    udev_builtin_add_property: ID_PATH_TAG=pci-0000_00_1d_7-usb-0_1_1_0-scsi-0_0_0_0
    udev_rules_apply_to_event: LINK 'disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0' /lib/udev/rules.d/60-persistent-storage.rules:62
    udev_rules_apply_to_event: IMPORT builtin 'blkid' /lib/udev/rules.d/60-persistent-storage.rules:76
    error: /dev/sdb: Permission denied
    udev_rules_apply_to_event: IMPORT 'udisks-part-id /dev/sdb' /lib/udev/rules.d/80-udisks.rules:88
    udev_event_spawn: starting 'udisks-part-id /dev/sdb'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'libudev: udev_device_new_from_syspath: device 0x1cc2680 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb''
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'libudev: udev_device_read_db: device 0x1cc2680 filled with db file data'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'using device_file=/dev/sdb syspath=/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb, offset=0 ao=0 and number=0 for /dev/sdb'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'Error opening /dev/sdb: Permission denied'
    spawn_wait: 'udisks-part-id /dev/sdb' [2251] exit with return code 0
    udev_rules_apply_to_event: IMPORT 'udisks-probe-ata-smart /dev/sdb' /lib/udev/rules.d/80-udisks.rules:112
    udev_event_spawn: starting 'udisks-probe-ata-smart /dev/sdb'
    spawn_read: 'udisks-probe-ata-smart /dev/sdb'(err) 'Failed to open disk /dev/sdb: Permission denied'
    spawn_wait: 'udisks-probe-ata-smart /dev/sdb' [2252] exit with return code 1
    udev_node_update_old_links: update old name, '/dev/disk/by-id/ata-SAMSUNG_HM100UZ_C5071E86AA22JN' no longer belonging to '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb'
    link_find_prioritized: found 'b8:16' claiming '/run/udev/links/disk\x2fby-id\x2fata-SAMSUNG_HM100UZ_C5071E86AA22JN'
    link_update: no reference left, remove '/dev/disk/by-id/ata-SAMSUNG_HM100UZ_C5071E86AA22JN'
    udev_node_update_old_links: update old name, '/dev/disk/by-id/wwn-0x50000f00aaeb0022' no longer belonging to '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb'
    link_find_prioritized: found 'b8:16' claiming '/run/udev/links/disk\x2fby-id\x2fwwn-0x50000f00aaeb0022'
    link_update: no reference left, remove '/dev/disk/by-id/wwn-0x50000f00aaeb0022'
    udev_node_add: handling device node '/dev/sdb', devnum=b8:16, mode=0660, uid=0, gid=6
    node_fixup: preserve permissions /dev/sdb, 060660, uid=0, gid=6
    node_symlink: preserve already existing symlink '/dev/block/8:16' to '../sdb'
    link_update: creating link '/dev/disk/by-id/usb-Samsung_S2_Portable_3_000000000000011E0A60-0:0' to '/dev/sdb'
    node_symlink: creating symlink '/dev/disk/by-id/usb-Samsung_S2_Portable_3_000000000000011E0A60-0:0' to '../../sdb'
    node_symlink: atomically replace '/dev/disk/by-id/usb-Samsung_S2_Portable_3_000000000000011E0A60-0:0'
    node_symlink: symlink '../../sdb' '/dev/disk/by-id/usb-Samsung_S2_Portable_3_000000000000011E0A60-0:0.udev-tmp' failed: Permission denied
    link_find_prioritized: found 'b8:16' claiming '/run/udev/links/disk\x2fby-path\x2fpci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0'
    link_update: creating link '/dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0' to '/dev/sdb'
    node_symlink: preserve already existing symlink '/dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0' to '../../sdb'
    udev_device_update_db: unable to create temporary db file '/run/udev/data/b8:16.tmp': Permission denied
    ACTION=add
    DEVLINKS=/dev/disk/by-id/usb-Samsung_S2_Portable_3_000000000000011E0A60-0:0 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    DEVNAME=/dev/sdb
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb
    DEVTYPE=disk
    ID_BUS=usb
    ID_INSTANCE=0:0
    ID_MODEL=S2_Portable_3
    ID_MODEL_ENC=S2\x20Portable\x203\x20\x20\x20
    ID_MODEL_ID=60a6
    ID_PATH=pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    ID_PATH_TAG=pci-0000_00_1d_7-usb-0_1_1_0-scsi-0_0_0_0
    ID_REVISION=2AM1
    ID_SERIAL=Samsung_S2_Portable_3_000000000000011E0A60-0:0
    ID_SERIAL_SHORT=000000000000011E0A60
    ID_TYPE=disk
    ID_USB_DRIVER=usb-storage
    ID_USB_INTERFACES=:080650:
    ID_USB_INTERFACE_NUM=00
    ID_VENDOR=Samsung
    ID_VENDOR_ENC=Samsung\x20
    ID_VENDOR_ID=04e8
    MAJOR=8
    MINOR=16
    SUBSYSTEM=block
    UDEV_LOG=6
    UDISKS_PRESENTATION_NOPOLICY=0
    USEC_INITIALIZED=2063008397
    run: '/usr/local/bin/makebak.sh'
    builtin_kmod_exit: unload module index
    And executed as root:
    run_command: calling: test
    adm_test: version 180
    This program is for debugging only, it does not run any program,
    specified by a RUN key. It may show incorrect results, because
    some values may be different, or not available at a simulation run.
    builtin_kmod_init: load module index
    add_matching_files: unable to open '/run/udev/rules.d': No such file or directory
    parse_file: reading '/lib/udev/rules.d/10-dm.rules' as rules file
    parse_file: reading '/etc/udev/rules.d/10-local.rules' as rules file
    parse_file: reading '/lib/udev/rules.d/11-dm-lvm.rules' as rules file
    parse_file: reading '/lib/udev/rules.d/13-dm-disk.rules' as rules file
    parse_file: reading '/lib/udev/rules.d/40-gphoto.rules' as rules file
    add_rule: IMPORT found builtin 'usb_id --export %p', replacing /lib/udev/rules.d/40-gphoto.rules:11
    parse_file: reading '/lib/udev/rules.d/42-qemu-usb.rules' as rules file
    parse_file: reading '/lib/udev/rules.d/50-udev-default.rules' as rules file
    parse_file: reading '/lib/udev/rules.d/53-sane.rules' as rules file
    (... much more rules parsing ...)
    udev_rules_new: rules use 216120 bytes tokens (18010 * 12 bytes), 28505 bytes buffer
    udev_rules_new: temporary index used 52000 bytes (2600 * 20 bytes)
    udev_device_new_from_syspath: device 0x21816d0 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb'
    udev_device_new_from_syspath: device 0x2190de0 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb'
    udev_device_read_db: device 0x2190de0 filled with db file data
    udev_rules_apply_to_event: RUN '/usr/local/bin/makebak.sh' /etc/udev/rules.d/10-local.rules:1
    udev_device_new_from_syspath: device 0x2183490 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0'
    udev_device_new_from_syspath: device 0x2183c90 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0'
    udev_device_new_from_syspath: device 0x2184480 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16'
    udev_device_new_from_syspath: device 0x2184c60 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0'
    udev_device_new_from_syspath: device 0x2185420 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1'
    udev_device_new_from_syspath: device 0x2185c00 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2'
    udev_device_new_from_syspath: device 0x21863d0 has devpath '/devices/pci0000:00/0000:00:1d.7'
    udev_device_new_from_syspath: device 0x2186b70 has devpath '/devices/pci0000:00'
    udev_rules_apply_to_event: GROUP 6 /lib/udev/rules.d/50-udev-default.rules:67
    udev_rules_apply_to_event: IMPORT 'ata_id --export /dev/sdb' /lib/udev/rules.d/60-persistent-storage.rules:37
    udev_event_spawn: starting 'ata_id --export /dev/sdb'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_TYPE=disk'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_BUS=ata'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_MODEL=SAMSUNG_HM100UZ'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_MODEL_ENC=SAMSUNG\x20HM100UZ\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_REVISION=2AM10010'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_SERIAL=SAMSUNG_HM100UZ_C5071E86AA22JN'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_SERIAL_SHORT=C5071E86AA22JN'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_WRITE_CACHE=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_WRITE_CACHE_ENABLED=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_HPA=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_HPA_ENABLED=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_PM=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_PM_ENABLED=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_SECURITY=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_SECURITY_ENABLED=0'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=232'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=232'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_SMART=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_SMART_ENABLED=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_AAM=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_AAM_ENABLED=0'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_AAM_VENDOR_RECOMMENDED_VALUE=254'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_AAM_CURRENT_VALUE=0'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_PUIS=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_PUIS_ENABLED=0'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_APM=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_FEATURE_SET_APM_ENABLED=0'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_DOWNLOAD_MICROCODE=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_SATA=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_SATA_SIGNAL_RATE_GEN2=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_SATA_SIGNAL_RATE_GEN1=1'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_ATA_ROTATION_RATE_RPM=5400'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_WWN=0x50000f00aaeb0022'
    spawn_read: 'ata_id --export /dev/sdb'(out) 'ID_WWN_WITH_EXTENSION=0x50000f00aaeb0022'
    spawn_wait: 'ata_id --export /dev/sdb' [2273] exit with return code 0
    udev_rules_apply_to_event: LINK 'disk/by-id/ata-SAMSUNG_HM100UZ_C5071E86AA22JN' /lib/udev/rules.d/60-persistent-storage.rules:44
    udev_rules_apply_to_event: PROGRAM 'scsi_id --whitelisted --replace-whitespace -p0x80 -d /dev/sdb' /lib/udev/rules.d/60-persistent-storage.rules:52
    udev_event_spawn: starting 'scsi_id --whitelisted --replace-whitespace -p0x80 -d /dev/sdb'
    spawn_wait: 'scsi_id --whitelisted --replace-whitespace -p0x80 -d /dev/sdb' [2274] exit with return code 1
    udev_rules_apply_to_event: IMPORT builtin 'path_id' /lib/udev/rules.d/60-persistent-storage.rules:61
    udev_builtin_add_property: ID_PATH=pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    udev_builtin_add_property: ID_PATH_TAG=pci-0000_00_1d_7-usb-0_1_1_0-scsi-0_0_0_0
    udev_rules_apply_to_event: LINK 'disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0' /lib/udev/rules.d/60-persistent-storage.rules:62
    udev_rules_apply_to_event: IMPORT builtin 'blkid' /lib/udev/rules.d/60-persistent-storage.rules:76
    builtin_blkid: probe /dev/sdb raid offset=0
    udev_builtin_add_property: ID_PART_TABLE_TYPE=dos
    udev_rules_apply_to_event: LINK 'disk/by-id/wwn-0x50000f00aaeb0022' /lib/udev/rules.d/60-persistent-storage.rules:86
    udev_rules_apply_to_event: IMPORT 'udisks-part-id /dev/sdb' /lib/udev/rules.d/80-udisks.rules:88
    udev_event_spawn: starting 'udisks-part-id /dev/sdb'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'libudev: udev_device_new_from_syspath: device 0x1af8680 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb''
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'libudev: udev_device_read_db: device 0x1af8680 filled with db file data'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'using device_file=/dev/sdb syspath=/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb, offset=0 ao=0 and number=0 for /dev/sdb'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'Entering MS-DOS parser (offset=0, size=1000204886016)'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'MSDOS_MAGIC found'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'looking at part 0 (offset 1048576, size 524288000000, type 0x07)'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'new part entry'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'looking at part 1 (offset 524289048576, size 475915091968, type 0x83)'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'new part entry'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'looking at part 2 (offset 0, size 0, type 0x00)'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'new part entry'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'looking at part 3 (offset 0, size 0, type 0x00)'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'new part entry'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'Exiting MS-DOS parser'
    spawn_read: 'udisks-part-id /dev/sdb'(err) 'MSDOS partition table detected'
    spawn_read: 'udisks-part-id /dev/sdb'(out) 'UDISKS_PARTITION_TABLE=1'
    spawn_read: 'udisks-part-id /dev/sdb'(out) 'UDISKS_PARTITION_TABLE_SCHEME=mbr'
    spawn_read: 'udisks-part-id /dev/sdb'(out) 'UDISKS_PARTITION_TABLE_COUNT=2'
    spawn_wait: 'udisks-part-id /dev/sdb' [2276] exit with return code 0
    udev_rules_apply_to_event: IMPORT 'udisks-probe-ata-smart /dev/sdb' /lib/udev/rules.d/80-udisks.rules:115
    udev_event_spawn: starting 'udisks-probe-ata-smart /dev/sdb'
    spawn_read: 'udisks-probe-ata-smart /dev/sdb'(err) 'libudev: udev_device_new_from_syspath: device 0x25b2c90 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb''
    spawn_read: 'udisks-probe-ata-smart /dev/sdb'(err) 'libudev: udev_device_read_db: device 0x25b2c90 filled with db file data'
    spawn_read: 'udisks-probe-ata-smart /dev/sdb'(err) 'libudev: udev_device_new_from_syspath: device 0x25b5230 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0''
    spawn_read: 'udisks-probe-ata-smart /dev/sdb'(err) 'libudev: udev_device_new_from_syspath: device 0x25b5720 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0''
    spawn_read: 'udisks-probe-ata-smart /dev/sdb'(err) 'libudev: udev_device_new_from_syspath: device 0x25b5d40 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16''
    spawn_read: 'udisks-probe-ata-smart /dev/sdb'(err) 'libudev: udev_device_new_from_syspath: device 0x25b6350 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0''
    spawn_read: 'udisks-probe-ata-smart /dev/sdb'(err) 'libudev: udev_device_new_from_syspath: device 0x25b6940 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1''
    spawn_read: 'udisks-probe-ata-smart /dev/sdb'(out) 'UDISKS_ATA_SMART_IS_AVAILABLE=1'
    spawn_wait: 'udisks-probe-ata-smart /dev/sdb' [2278] exit with return code 0
    udev_node_add: handling device node '/dev/sdb', devnum=b8:16, mode=0660, uid=0, gid=6
    node_fixup: preserve permissions /dev/sdb, 060660, uid=0, gid=6
    node_symlink: preserve already existing symlink '/dev/block/8:16' to '../sdb'
    link_find_prioritized: found 'b8:16' claiming '/run/udev/links/disk\x2fby-id\x2fata-SAMSUNG_HM100UZ_C5071E86AA22JN'
    link_update: creating link '/dev/disk/by-id/ata-SAMSUNG_HM100UZ_C5071E86AA22JN' to '/dev/sdb'
    node_symlink: preserve already existing symlink '/dev/disk/by-id/ata-SAMSUNG_HM100UZ_C5071E86AA22JN' to '../../sdb'
    link_find_prioritized: found 'b8:16' claiming '/run/udev/links/disk\x2fby-id\x2fwwn-0x50000f00aaeb0022'
    link_update: creating link '/dev/disk/by-id/wwn-0x50000f00aaeb0022' to '/dev/sdb'
    node_symlink: preserve already existing symlink '/dev/disk/by-id/wwn-0x50000f00aaeb0022' to '../../sdb'
    link_find_prioritized: found 'b8:16' claiming '/run/udev/links/disk\x2fby-path\x2fpci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0'
    link_update: creating link '/dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0' to '/dev/sdb'
    node_symlink: preserve already existing symlink '/dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0' to '../../sdb'
    udev_device_update_db: created db file '/run/udev/data/b8:16' for '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb'
    ACTION=add
    DEVLINKS=/dev/disk/by-id/ata-SAMSUNG_HM100UZ_C5071E86AA22JN /dev/disk/by-id/wwn-0x50000f00aaeb0022 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    DEVNAME=/dev/sdb
    DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host16/target16:0:0/16:0:0:0/block/sdb
    DEVTYPE=disk
    ID_ATA=1
    ID_ATA_DOWNLOAD_MICROCODE=1
    ID_ATA_FEATURE_SET_AAM=1
    ID_ATA_FEATURE_SET_AAM_CURRENT_VALUE=0
    ID_ATA_FEATURE_SET_AAM_ENABLED=0
    ID_ATA_FEATURE_SET_AAM_VENDOR_RECOMMENDED_VALUE=254
    ID_ATA_FEATURE_SET_APM=1
    ID_ATA_FEATURE_SET_APM_ENABLED=0
    ID_ATA_FEATURE_SET_HPA=1
    ID_ATA_FEATURE_SET_HPA_ENABLED=1
    ID_ATA_FEATURE_SET_PM=1
    ID_ATA_FEATURE_SET_PM_ENABLED=1
    ID_ATA_FEATURE_SET_PUIS=1
    ID_ATA_FEATURE_SET_PUIS_ENABLED=0
    ID_ATA_FEATURE_SET_SECURITY=1
    ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
    ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=232
    ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=232
    ID_ATA_FEATURE_SET_SMART=1
    ID_ATA_FEATURE_SET_SMART_ENABLED=1
    ID_ATA_ROTATION_RATE_RPM=5400
    ID_ATA_SATA=1
    ID_ATA_SATA_SIGNAL_RATE_GEN1=1
    ID_ATA_SATA_SIGNAL_RATE_GEN2=1
    ID_ATA_WRITE_CACHE=1
    ID_ATA_WRITE_CACHE_ENABLED=1
    ID_BUS=ata
    ID_MODEL=SAMSUNG_HM100UZ
    ID_MODEL_ENC=SAMSUNG\x20HM100UZ\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
    ID_PART_TABLE_TYPE=dos
    ID_PATH=pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
    ID_PATH_TAG=pci-0000_00_1d_7-usb-0_1_1_0-scsi-0_0_0_0
    ID_REVISION=2AM10010
    ID_SERIAL=SAMSUNG_HM100UZ_C5071E86AA22JN
    ID_SERIAL_SHORT=C5071E86AA22JN
    ID_TYPE=disk
    ID_WWN=0x50000f00aaeb0022
    ID_WWN_WITH_EXTENSION=0x50000f00aaeb0022
    MAJOR=8
    MINOR=16
    SUBSYSTEM=block
    UDEV_LOG=6
    UDISKS_ATA_SMART_IS_AVAILABLE=1
    UDISKS_PARTITION_TABLE=1
    UDISKS_PARTITION_TABLE_COUNT=2
    UDISKS_PARTITION_TABLE_SCHEME=mbr
    UDISKS_PRESENTATION_NOPOLICY=0
    USEC_INITIALIZED=2063008397
    run: '/usr/local/bin/makebak.sh'
    builtin_kmod_exit: unload module index
    Does anyone know what the problem could be (and the solution)?
    Thanks in advance!

    Sure, a loop that waits up to a certain number of seconds for you to mount the device is far more preferrable. Something like...
    #!/bin/bash
    # max time to wait
    timeout=60
    # label of device to wait for
    devlabel=blackhole
    # where to look for it
    devmount=/mnt/backup
    dev_mounted() {
    mountpoint -q "$devmount" &&
    [[ $(findmnt -runo LABEL "$devmount") = "$devlabel" ]]
    if ! dev_mounted; then
    printf "==> Waiting %s seconds for %s to be mounted on %s" "$devlabel" "$devmount"
    until dev_mounted; do
    sleep 1
    if (( --timeout == 0 )); then
    print "==> ERROR: device didn't show up after %s seconds!\n" "$timeout"
    exit 1
    fi
    done
    fi
    # do backup stuff here...

  • Disk utility reports "Device could not be opened" - error when trying to format a new drive in a Mac Pro 1,1

    MacPro 1,1 Quadcore 3 GHz (2006 "Woodcrest")
    32 GB RAM
    ATI Radeon HD 5770
    OS X 10.7.5 Lion
    I have encountered the following behavior when trying to format a new drive with disk utility. This description has also been send via the Mac Pro feedback as a bug report to Apple.
    On searching the web and forums with this particular error message and behaviour I could not find any usful results. So maybe the following description may be helpful for some users.
    Best regards.
    1. Drive Bay 1 contains the original 250 GB Startupdisk. It works without errors.
    2. Drive Bays 3 and 4 contain each a WD Caviar Black 2 TB SATA 3 HDD. They work without errors.
    3. I have purchased a third WD Caviar Black 2 TB HDD.
    4. In Drive Bay 2 there has been a Seagate 750 GB HDD, which worked in conjunction with all the other drives without error.
    5. I exchanged the Seagate HDD in Drive Bay 2 with the new WD Caviar Black 2 TB HDD.
    6. On starting the system, it will report to initialize the new drive.
    7. On trying to initialize the new drive with disk utility it reports the error [translated from German] "Erasing of the volume has failed. The device could not be opened."
    8. I thought that the drive is faulty. Thus I created an RMA-Case at WD. They exchanged the drive without problems.
    9. On getting the exchanged WD Caviar Black 2 TB drive I put it in Drive Bay 2 as before.
    10. On trying to erase and format the exchange drive I got the same error message "Drive could not be opened."
    10.1 On selecting the physical drive in the devices list, disk utility reports all information in the bottom area of its window as usual, e. g. hard disk description, connection bus, type and place, capacity, write status, SMART-status, partition scheme.
    10.1 On leaving that drive selected in the devices list and clicking the info-button, disk utility will also report additional information as usual, e. g. Name, Type, partition scheme, media-identification, media name, media type, device tree, … , number of relocated sectors, etc.. All this information appears to be valid, as can be compared to the other devices information inside the other Drive Bays. Also the disk numbering scheme appears to be standard - 4 HDDs give the numbering disk0, disk1, disk2, disk3.
    10.2 From that information I conclude that the SATA-bus and connectors electrically work properly, the drive has spun up and can be accessed by the system normally.
    11. I powered down the computer, took out the HDDs from Drive Bays 3 and 4 and put the caddy with the new exchange drive in Drive Bay 4 [Maybe, I could have also just left it alone in Drive Bay 2, or 3].
    12. After powering on the system, disk utility will quick format the exchange drive without any error message. Also, when erasing again by selecting the option to write zeros to the drive, disk utility will finish without error.
    13. After disk utility finished formatting, I put back the original drives into Drive Bay 3 and 4 and put the now newly formatted drive back into Drive Bay 2.
    14. After switching on the computer the system start and login proceeds without any error message. All drives appear as expected on the desktop.

    If anyone is reading this still looking for what caused the issue and how to fix it here is what I discovered.
    The antivirus program our company uses, Bitdefender Antivirus Plus, was causing some of the PDF files not to open. After troubleshooting the different modules and settings the culprit was..
    Scan SSL in Privacy Control Settings. Turning it OFF solved the problem and all the PDF files that previously would not open now open just fine. This issue has been sent to Bitdefender for them to review. If you use a different antivirus program and are having this issue try locating the Scan SSL setting and see if turning it off solves the problem.

  • Install Failure: Windows cannot be installed to disk 0 partition 1.

    I have problem with installation Win7 x64. Installation stops on disk selection with mesage: "Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information". I tried ICH9 controler in mode AHCI and RAID. Loading intel drivers (Ver:8.7.0.1007 and 7.5.0.1017) gives me masage "Windows cannot be installed to disk 0 partition 1." Details: "Windows is unable to install to the selected location. Error: 0x80300001". I can see drives, make new partition and format it.
    Spec:
    CPU: Intel Q6600
    RAM: 4GB
    MB: MSI Neo2 FIR (intel P35 and ICH9R)
    HDD: 2x 640GB SATA (empty)

    I had the same problem. On a new build, ASUS P8Z68-V/Gen4, I a pulled a WD 1TB Sata HDD from another computer I had and put it into my new computer.  The drive was previously used just as a data drive, not a boot disk. Win 7 didn't want load on it.
    I followed the instructions posted by BenFreefly (although abbreviated slightly) and it worked. For reference, here are the steps;
    1) After Windows gives you the error, hit SHIFT-F10 to get to the command prompt.
    2) From command prompt enter the following commands:
    diskpart
    list disk
    select disk 0    (your disk may be a different number)
    clean
    create partition primary
    exit    (exits diskpart)
    exit    (exits command prompt)
    3) Click on Refresh
    4) Windows now sees the disk as a primary disk
    5) Select the disk and click Next.
    From there, Windows will extract files and the install will boot several times.
    Phil C.
    Wow, that's weird, this is my answer that has been deleted

  • Mac Mini Not booting due to hard disk being full

    Hello All,
    I have a Mini and has worked well for the past 12 months, last week i upgraded to the OSX Lion which also went very smoothly. However yesterday i had a message on my screen stating the my startup disk was full and i needed to make space. finding this a little odd as I have a TB external hard drive that everything goes to.
    the mini frose during the deletion process after leaving for approx an hour i attempted to reboot. from this point i have only been able to access the disk utility through the DVD that came with the mini I have done a disk check and repair, also check permission all are ok exept for only having 49mb of hd space left.
    I cant access safe mode as this will not boot either (tried to load for 8 hours) re install will also not work due to the amount of hd space available
    has anyone got any ideas how i can clean the hard disk without formatting as ideally i would like to know what is causing the problem.
    like a not very bright thing i left the time machine turned off so this isnt an option either??

    Ok, basically it would involve the following
    Boot from the DVD
    Launch the Terminal.app probably from a Utilities menu which also lists Disk Utility
    In Terminal you would need to type cd /Users/accountname/.Trash followed by pressing the return key
    Then you would type ls -l and again press return
    It would then list what is in the trash for that user account. If it begins with a D it is a folder, otherwise it is likely a file. The big number before the data would give an idea of the size of the item.
    When you have found the one you want to delete (remember you cannot undo this) you would type the following to delete a file rm filename and then press return again.
    The do ls -l again to see if the file has gone.
    If you want to delete a folder that is in the trash then the command would be rm -r foldername and then again press return. Using rm -r is a particularly dangerous command if you do it in the wrong place or the wrong way you could delete everything on the hard disk.
    Normally in single user mode (which you said was not working) you have to type some other commands beforehand to allow modifying the contents of the hard disk. I have not tried this via the DVD so I do not know if the same applied. If it does it is likely to refuse to delete the file and you should come back to me and we can work out the process.

  • Problem with USB External Hard Disk Drive

    I have similar problem with hard disk MK6025GAS in Sweex casing connected via USB as Raistlfiren in this post but I am not sure if it has something to do with kernel. The problem is that when I plug the hard disk via USB it is not even shown with in /dev/ or by fdisk -l. I had similar problems with the drive before but it was always shown in /dev.
    I got same output from dmesg as Raistlfiren in the post before
    # dmesg | tail
    sd 4:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
    sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
    Info fld=0x0
    I was browsing net for a lot of time to find a solution but nothing helped a lot. The problem is closes to the one described on Gentoo Forum
    I can see that it is recognized by computer since it is shown with lsusb
    # lsusb
    Bus 001 Device 005: ID 13fd:0540 Initio Corporation
    # lsusb -d 13fd:0540 -v
    Bus 001 Device 005: ID 13fd:0540 Initio Corporation
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 64
    idVendor 0x13fd Initio Corporation
    idProduct 0x0540
    bcdDevice 0.00
    iManufacturer 1 Initio
    iProduct 2 MK6025GAS
    iSerial 3 0010100500000000
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
    Self Powered
    MaxPower 2mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 2
    bInterfaceClass 8 Mass Storage
    bInterfaceSubClass 6 SCSI
    bInterfaceProtocol 80 Bulk (Zip)
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x02 EP 2 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 1
    Device Qualifier (for other device speed):
    bLength 10
    bDescriptorType 6
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 64
    bNumConfigurations 1
    Device Status: 0x0001
    Self Powered
    From the beginning I though and I still think that the partition table is screwed up but the programs like TestDisk and fixdisktable work only with disks shown in /dev/
    Additionally, I have checked the content of /var/log/kernel.log
    Sep 16 22:03:58 hramat kernel: usb 1-2: new high speed USB device using ehci_hcd and address 5
    Sep 16 22:03:58 hramat kernel: usb 1-2: configuration #1 chosen from 1 choice
    Sep 16 22:03:58 hramat kernel: scsi4 : SCSI emulation for USB Mass Storage devices
    Sep 16 22:03:58 hramat kernel: usb-storage: device found at 5
    Sep 16 22:03:58 hramat kernel: usb-storage: waiting for device to settle before scanning
    Sep 16 22:04:03 hramat kernel: scsi 4:0:0:0: Direct-Access Initio MK6025GAS 2.23 PQ: 0 ANSI: 0
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: Attached scsi generic sg4 type 0
    Sep 16 22:04:03 hramat kernel: usb-storage: device scan complete
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] 117210240 512-byte hardware sectors: (60.0 GB/55.8 GiB)
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Write Protect is off
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Mode Sense: 86 0b 00 02
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
    Sep 16 22:04:03 hramat kernel: sdd:<6>sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
    Sep 16 22:04:03 hramat kernel: Info fld=0x0
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
    and /var/log/errors.log
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
    Sep 16 22:07:35 hramat kernel: INFO: task async/0:3957 blocked for more than 120 seconds.
    Sep 16 22:07:35 hramat kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    The only thing I understand from these logs is that the disk is blocked, therefore not listed in /dev.
    Assuming the newer kernel problems I could try to use some older live linux CD to see if that would work. I am also thinking of connecting this hard drive directly to my laptop, using live linux CD and maybe check the output of hdparm. Is there anything else I could check or try?
    Thank you for any help or suggestions
    Matej

    Thank you nTia89 for response. Sorry for not providing enough information.
    I believe the problem is not system dependent. I have dual boot with windows and there the disk has also problems. However, I do have Arch32 with Kernel 2.6.30, using Gnome. hal and dbus are also running.
    I did not tried to connect the disk to the computer directly, I will try it today.
    Yesterday I have used SystemRescueCD 0.4.1 with Kernel 2.6.22. I wanted to see if it will be recognized by the system and placed in /dev/. Yes it was. This means that the problem highlighted in Gentoo forum can be true, but it doesn't solve my problem. I have tried to connect the drive several times to Arch and it was not shown in /dev/sd*, in SystemRescueCD it was placed as /dev/sdb. Now I am sure that the partition table is screwed up.
    So I have started to play with the drive in SystemRescueCD with TestDisk and FixDiskTable but without success.
    % fdisk -l
    Disk /dev/sda: 100.0 GB, 100030242816 bytes
    255 heads, 63 sectors/track, 12161 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 1530 12289693+ 7 HPFS/NTFS
    /dev/sda2 1531 6672 41303115 7 HPFS/NTFS
    /dev/sda3 6673 12161 44090392+ f W95 Ext'd (LBA)
    /dev/sda5 * 6673 11908 42058138+ 83 Linux
    /dev/sda6 11909 12161 2032191 82 Linux swap / Solaris
    Disk /dev/sdb: 60.0 GB, 60011642880 bytes
    64 heads, 32 sectors/track, 57231 cylinders
    Units = cylinders of 2048 * 512 = 1048576 bytes
    Disk /dev/sdb doesn't contain a valid partition table
    Manufacturer disk geometry: Heads: 16; Cylinders: 16383; Sectors: 63; Logical Blocks (LBA): 117210240
    TestDisk found only Linux partitions with 43Gb while disk had only one 60Gb partitioned with FAT32/NTFS.
    Also recognized 64 heads, 57231 cylinders and 32 sectors (same as from fdisk -l), which obviously differs from manufacturer disk geometry.
    testdisk.log:
    Thu Sep 17 19:09:26 2009
    Command line: TestDisk
    TestDisk 6.8, Data Recovery Utility, August 2007
    Christophe GRENIER
    Linux version (ext2fs lib: 1.40.2, ntfs lib: 9:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: none)
    Using locale 'C'.
    Hard disk list
    Disk /dev/sda - 100 GB / 93 GiB - CHS 12161 255 63, sector size=512
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57231 64 32, sector size=512
    Disk /dev/sdb - 60 GB / 55 GiB
    Partition table type: Intel
    Interface Advanced
    New options :
    Dump : No
    Cylinder boundary : Yes
    Allow partial last cylinder : No
    Expert mode : No
    Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57231 64 32
    Current partition structure:
    Partition sector doesn't have the endmark 0xAA55
    Ask the user for vista mode
    Computes LBA from CHS for Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Allow partial last cylinder : Yes
    search_vista_part: 1
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Search for partition aborted
    Results
    interface_write()
    No partition found or selected for recovery
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Search for partition aborted
    Results
    interface_write()
    No partition found or selected for recovery
    simulate write!
    write_mbr_i386: starting...
    Store new MBR code
    write_all_log_i386: starting...
    No extended partition
    Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Current partition structure:
    Partition sector doesn't have the endmark 0xAA55
    Ask the user for vista mode
    Allow partial last cylinder : Yes
    search_vista_part: 1
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Results
    interface_write()
    No partition found or selected for recovery
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    NTFS at 8956/63/32
    heads/cylinder 255 (NTFS) != 64 (HD)
    sect/track 63 (NTFS) != 32 (HD)
    filesystem size 24579387
    sectors_per_cluster 8
    mft_lcn 1024141
    mftmirr_lcn 1650676
    clusters_per_mft_record -10
    clusters_per_index_record 1
    NTFS part_offset=9392094720, part_size=12584646144, sector_size=512
    NTFS partition cannot be added (part_offset<part_size).
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34129 1 1 75201 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=69896224, size=84116272, end=154012495, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34632 2 1 75704 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=70926400, size=84116272, end=155042671, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34668 0 1 75740 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=71000064, size=84116272, end=155116335, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34673 1 1 75745 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=71010336, size=84116272, end=155126607, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34699 2 1 75771 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=71063616, size=84116272, end=155179887, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34708 2 1 75780 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=71082048, size=84116272, end=155198319, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 36338 0 1 77410 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=74420224, size=84116272, end=158536495, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 36367 0 1 77439 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=74479616, size=84116272, end=158595887, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 36401 2 1 77473 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=74549312, size=84116272, end=158665583, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 36414 2 1 77486 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=74575936, size=84116272, end=158692207, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 37949 1 1 79021 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=77719584, size=84116272, end=161835855, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 37955 1 1 79027 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=77731872, size=84116272, end=161848143, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 37989 1 1 79061 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=77801504, size=84116272, end=161917775, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 38404 0 1 79476 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=78651392, size=84116272, end=162767663, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 39636 2 1 80708 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=81174592, size=84116272, end=165290863, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 41263 1 1 82335 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=84506656, size=84116272, end=168622927, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 41266 1 1 82338 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=84512800, size=84116272, end=168629071, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 41660 0 1 82732 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=85319680, size=84116272, end=169435951, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 42898 0 1 83970 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=87855104, size=84116272, end=171971375, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 43244 1 1 84316 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=88563744, size=84116272, end=172680015, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 44870 2 1 85942 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=91893824, size=84116272, end=176010095, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 44930 2 1 86002 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=92016704, size=84116272, end=176132975, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 46961 0 1 88033 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=96176128, size=84116272, end=180292399, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 47312 0 1 88384 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=96894976, size=84116272, end=181011247, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 48393 2 1 89465 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=99108928, size=84116272, end=183225199, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 49633 2 1 90705 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=101648448, size=84116272, end=185764719, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 50767 1 1 91839 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=103970848, size=84116272, end=188087119, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 51150 1 1 92222 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=104755232, size=84116272, end=188871503, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 51941 1 1 93013 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=106375200, size=84116272, end=190491471, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 52759 0 1 93831 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=108050432, size=84116272, end=192166703, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 53069 1 1 94141 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=108685344, size=84116272, end=192801615, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 53768 0 1 94840 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=110116864, size=84116272, end=194233135, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54287 0 1 95359 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=111179776, size=84116272, end=195296047, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54493 2 1 95565 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=111601728, size=84116272, end=195717999, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54861 1 1 95933 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=112355360, size=84116272, end=196471631, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54890 2 1 95962 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=112414784, size=84116272, end=196531055, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54953 2 1 96025 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=112543808, size=84116272, end=196660079, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 56330 1 1 97402 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=115363872, size=84116272, end=199480143, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 56334 0 1 97406 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=115372032, size=84116272, end=199488303, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 57203 0 1 98275 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=117151744, size=84116272, end=201268015, disk end=117211136)
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Check the harddisk size: HD jumpers settings, BIOS detection...
    The harddisk (60 GB / 55 GiB) seems too small! (< 103 GB / 95 GiB)
    The following partitions can't be recovered:
    D Linux 34129 1 1 75201 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34632 2 1 75704 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34668 0 1 75740 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34673 1 1 75745 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34699 2 1 75771 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34708 2 1 75780 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 36338 0 1 77410 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 36367 0 1 77439 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 36401 2 1 77473 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 36414 2 1 77486 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 37949 1 1 79021 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 37955 1 1 79027 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 37989 1 1 79061 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 38404 0 1 79476 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 39636 2 1 80708 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 41263 1 1 82335 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 41266 1 1 82338 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 41660 0 1 82732 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 42898 0 1 83970 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 43244 1 1 84316 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 44870 2 1 85942 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 44930 2 1 86002 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 46961 0 1 88033 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 47312 0 1 88384 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 48393 2 1 89465 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 49633 2 1 90705 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 50767 1 1 91839 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 51150 1 1 92222 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 51941 1 1 93013 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 52759 0 1 93831 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 53069 1 1 94141 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 53768 0 1 94840 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54287 0 1 95359 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54493 2 1 95565 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54861 1 1 95933 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54890 2 1 95962 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54953 2 1 96025 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 56330 1 1 97402 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 56334 0 1 97406 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 57203 0 1 98275 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    Results
    interface_write()
    No partition found or selected for recovery
    simulate write!
    write_mbr_i386: starting...
    Store new MBR code
    write_all_log_i386: starting...
    No extended partition
    Interface Advanced
    Disk /dev/sdb - 60 GB / 55 GiB
    Partition table type: Intel
    Disk /dev/sdb - 60 GB / 55 GiB
    Partition table type: Intel
    New options :
    Dump : No
    Cylinder boundary : Yes
    Allow partial last cylinder : No
    Expert mode : No
    New options :
    Dump : No
    Cylinder boundary : Yes
    Allow partial last cylinder : No
    Expert mode : No
    Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Current partition structure:
    Partition sector doesn't have the endmark 0xAA55
    Ask the user for vista mode
    Allow partial last cylinder : No
    search_vista_part: 0
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Search for partition aborted
    Results
    Can't open backup.log file: No such file or directory
    interface_load
    interface_write()
    No partition found or selected for recovery
    simulate write!
    write_mbr_i386: starting...
    Store new MBR code
    write_all_log_i386: starting...
    No extended partition
    TestDisk exited normally.
    fixdisktable first output:
    % ./fixdisktable -d /dev/sdb
    Getting hard disk geometry
    cylinders=57231, heads=64, sectors=32
    end_offset: 2147482624
    FfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSs
    EXT2 partition at offset 56832, length=(41072.398 MB) 43067531264
    Sectors: start= 111, end= 84116382, length= 84116272
    Hd,Sec,Cyl: start(3,16,0) end(28,31,41072)
    Done searching for partitions.
    Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
    1 80 3 16 0 63 32 1023 111 84116273 83 (Interpretted)
    1 80 3 16 0 63 224 255 111 84116273 83 (RAW)
    1: 8003 1000 833f e0ff 6f00 0000 3183 0305
    2: 0000 0000 0000 0000 0000 0000 0000 0000
    3: 0000 0000 0000 0000 0000 0000 0000 0000
    4: 0000 0000 0000 0000 0000 0000 0000 0000
    Do you wish to write this partition table to disk (yes/no)? no
    fixdisktable second output:
    % ./fixdisktable -d -r -v /dev/sdb
    Getting hard disk geometry
    cylinders=57231, heads=64, sectors=32
    end_offset: 2147482624
    FfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSs
    NTFS partition at offset 17483776, length=(17592186043512.582 MB) 184467440727622 49216
    Sectors: start= 34148, end=36028797017147916, length=36028797017113768
    Hd,Sec,Cyl: start(43,5,16) end(16,12,2096265)
    Done searching for partitions.
    Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
    1 80 43 5 16 63 32 1023 34148 -1850199 07 (Interpretted)
    1 80 43 5 16 63 224 255 34148 -1850199 07 (RAW)
    1: 802b 0510 073f e0ff 6485 0000 a9c4 e3ff
    2: 0000 0000 0000 0000 0000 0000 0000 0000
    3: 0000 0000 0000 0000 0000 0000 0000 0000
    4: 0000 0000 0000 0000 0000 0000 0000 0000
    Do you wish to write this partition table to disk (yes/no)? no
    This string "FfEeSsNnBbUu" was repeating there for longer time and it was most probably related to debugging or a verbose mode of fixdisktable
    As I have mentioned I will try to connect the disk directly to the computer and see what will happen.
    Shall I try to correct the disk geometry to the one specified by manufacturer? Is it possible?
    Any suggestions?

  • MDT 2013 Fails to Format or Partition disk on Surface Pro 3

    I have been trying to image a Surface Pro 3 using MDT 2013 and have been unable to get past the Format and Partition portion of the deployment.  At first I would get an error that it was unable to format or partition the drive and then after that it
    just reboots after trying for so long.  I am able to image any other device with the same task sequence and have no issue just having an issue with the Surface Pro 3.  Any help would be great.
    Thanks in advance.
    I am getting the error FAILURE (5210)
    ZTI Error - Unhandled error returned by ZTIDISKPART: Object required (424)

    I think our problem is also hardware failure although without re-imaging a working surface pro 3 I can't be sure.
    I tried what imfusio suggested in this thread.
    https://social.technet.microsoft.com/Forums/en-US/d31384bc-4e96-4a5b-a400-637bd6006d81/failure-5456-unable-to-determine-destination-disk-partition-and-or-drive-surface-pro-3?forum=mdt
    Unfortunately the deployment failed with the same ZTI Error - Unhandled error returned by ZTIDISKPART:
    Object required (424)
    I then rebooted into WinPE and ran diskpart, I could see the two volumes (EFI and OSDisk). I then tried to format the OS disk volume using diskpart. I got a paramater is incorrect error and the disk was no longer visible with a 'list disk' command. So it's
    like the format is putting the disk offline. I'm going to try restore one of these surfaces, apply all firmware updates then re-image. If that doesn't work I'm out of ideas.

  • Is It Possible to Install Windows 7 on a GUID Partition Table Disk?

    Is it possible to install Windows 7 on a GPT disk?
    I created a RAID 0 array on my dual Xeon 5580 system and tried installing Windows 7 Ultimate 64-bit RTM. When I got to the "Where do you want to install Windows" part I used shift-F10 to open up a command window, then I used diskpart to create a GPT with the following partitions:
    Disk 0 Part 1 -  102 MB EFI System
    Disk 0 Part 2 -  128 MB MSR
    Disk 0 Part 3 -  500 MB Primary
    Disk 0 Part 4 - 7446 GB Primary
    But there was a message "Windows cannot be installed to Disk 0 Partition 3 (show details)" - clicking on "show details" gave me "Windows cannot be installed to this disk. The selected disk is of the GPT partition style."
    What gives? I thought Windows Vista and beyond supported GPT.
    The problem with MBR is that you can't have a file system larger than 2 TB.
    Cheers, Eric

    I am trying to install Windows Server 2008 R2 Ent edition onto system that has an ASUS M3A78 Pro motherboard with 8GB of memory & an AMD Phenom II x3 2.6GHz Socket AM3 Processor
    (X3 710).
    I realize that this system doesn't support UEFI but I have an Adaptec 3805 RAID controller in this system that does support the advanced format hard drives, so I would think I should
    be OK there.
    Attached to the RAID controller are 3 - 1.5TB SATA Hard Drives in a RAID 5 yeilding 2.72TB's of usable space.
    I followed the following process to convert the array to GPT.
    I booted to the Server 2008 R2 Ent installation DVD.
    I select next at the language \ time & currency format \ Keyboard selection screen.
    Then I select the 'repair your computer' option at the following screen.
    I do not select the 'repair' (default) option, but instead select the radio button above it (I forget what that's labeled) working from memory here - which gives me the option to
    launch a command prompt.
    I launch diskaprt from that command prompt.
    First I selected the disk
    list disk (this displays the installed disks)
    select disk 0
    The I converted the disk to gpt
    convert gpt
    Then I created 200 MB EFI partition:
    create partition
    efi size=200
    Then I created MSR
    partition:
    create partition
    msr size=128
    Then I created primary
    partition:
    create partition
    primary
    ...and it took remaining
    available space to itself.
    I assigned drive
    letter C to this new first "primary" partition
    Assign letter=c
    I confirmed the order is:
    I confirmed the partition order is:
    ESP > MSR > DATA Partition
    After all of that I restart into the Windows installation and attempt to install by selecting the newly created primary partition and am presented with an error that states:
    “Windows cannot be installed to Disk 0 Partition 3. (Show details)”
    and the details show:
    "Windows cannot be installed to this disk. The selected disk is of the gpt partition style."
    Any help anyone could provide would be greatly appreciated.
    Thanks

  • No more optical drive and windows 8 issue: "Windows cannot be installed on this disk as it has an MBR partition table."

    I have an Early 2011 13" MBP going strong with an SSD and original HDD installed in the optical drive. However, having had success with windows 7 on my old HDD I was planning to install Windows 8.1 (from .iso) on my SSD. However, for the past day or so it's been a nightmare.
    I tried the official procedure but by editing the bootcamp info.plist so I could boot from USB (you can't install windows from an external optical drive apparently) partitioning as bootcamp wanted too.
    I then tried it a number of different ways using disk utility etc and with an empty space
    However, I always seem to end up with the error "“Windows cannot be installed on this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only installed on GPT disks“
    I read some interesting stuff here http://www.royhochstenbach.com/installing-windows-8-1-on-a-2013-mac-pro/
    He points out that
    "Windows 7 and 8 in x64 support EFI. Normally if you install Windows on a Mac and use the installation DVD, it boots into regular BIOS mode, thus can be installed on an MBR partition. I tried the same, but since the Mac Pro doesn’t have an optical drive I had to use an external drive. And apparently the Mac boots external optical drives in EFI mode too. The Bootcamp wizard is aware of this, and creates a GPT partition on a non-superdrive Mac but an MBR partition on a superdrive Mac."
    This means Bootcamp is essentially making the wrong type of partition?
    My real question is? How do I install it windows 8? I'm really on my last legs!
    I really don't want to have to open this thing up and reinsert my optical drive as its really really difficult to get out of the enclosure (would probably have to break it).
    A huge thanks in advance!

    Hi,
    Have you tried that suggestion?
    You also could use this commands to check and install again:
    Inside windows installer, hit Shift+F10 to get a command prompt, then run diskpart and type List disk to displays a list of disks and information about them, such as their size, amount of available free space, whether the disk is a basic or dynamic disk,
    and whether the disk uses the master boot record (MBR) or GUID partition table (GPT) partition style.
    and then select the target disk. Zap the drive (with the clean command), create GPT table (new gpt), create the GPT-EFI special partitions.
    Step-by-step instructions is here for reference:
    HOW TO: Use the Diskpart.efi Utility to Create a GUID Partition Table Partition on a Raw Disk in Windows
    http://support.microsoft.com/kb/297800?wa=wsignin1.0
    Then reboot so the firmware finds those partitions and adds the disk to the EFI-native boot order (Windows installer checks this).
    Karen Hu
    TechNet Community Support

  • HT201250 Time Machine backup disk not found

    I recently reconfigured my external disks, creating a 500GB oartition for Time Machine backup. thefirst time I set up Time machine to use that partition all went well. Seconed time it failed "cannot find backup disk." 
    This is a 24 inch, mid 2007 iMac OS X 10.8.2.  I am using two external backup drives - 1T LaCie with 4 partitions and a BlackX removable adaptor with a WD 1T drive plugged in.  Both are formatted Mac OS Extended (Journaled)  In the view below the top "Time Machine" drive at the top is a duplicate of the last drive in the list.
    If I select the top drive - I have the option to "Remove Disk" - NOT to "Use this Disk." So I have to select the bottom "Time Machine" drive.  The backup will then run once but on the second try I get "Time Machine couldn't complete the backup to "Time Machine". Unable to complete backup. An error occured while creating backup folder."  Whether I remove the top listed disk or not doesn't seem to matter, sometimes it finds the drive, sometimes not!
    The BlackX is a USB connected directly to the iMac.  The other partition on that drive contains movie clips and they run fine.
    There is a backup folder on the Time Machine drive with six backups - however I have to "reset" the Time Machine each time to get it to backup.  It craps out on the second try every time.  Got me buffaloed!  Any ideas?

    Assuming you have nothing on your Time Machine volume that you need, erase that volume and Verify it from Disk Utilities. Repair if necessary. Then, go into the Time Machine Preferences and Remove the selected drive to use. Now, reselect it and try a backup.

  • Attachment of a data disk to new VM.

    After attachment of an empty disk the VM, It shows 3 disks in list:
    Disk 0: The OS Disk.
    Disk 1: Temporary resource 
    Disk 2: Data disk (what we attached)
    Why Disk 1 should not be used for data storage and what is the meaning of temporary storage?

    Hi Pawan,
    Thanks for posting here.
    Temporary Disk The temporary storage drive, labeled as the D: drive is not persisted and is not saved in the Windows Azure Blob storage. It is used primarily for the page file and its performance is not guaranteed to be predictable. Management tasks such
    as a change to the virtual machine size, resets the D: drive. In addition, Windows Azure erases the data on the temporary storage drive when a virtual machine fails over. The D: drive is not recommended for storing any user or system database files, including
    tempdb.
    The temporary storage drive, labeled as the D: drive, is not persisted to Azure blob storage. Do not store your data or log files on the
    D: drive.
    Only store tempdb and/or Buffer Pool Extensions on the
    D drive when using the D-Series Virtual Machines (VMs). Unlike the other VM series, the
    D drive in the D-Series VMs is SSD-based. This can improve the performance of workloads that heavily use temporary objects or that have working sets which don't fit in memory. For more information, see
    Using SSDs in Azure VMs to store SQL Server TempDB and Buffer Pool Extensions.
    Reference:
    http://blogs.msdn.com/b/mast/archive/2013/12/07/understanding-the-temporary-drive-on-windows-azure-virtual-machines.aspx
    Girish Prajwal

  • Solaris 8 x86: How to install on disk connected via IDE controller

    I have a PC with a Pentium 4 processor and the following IDE disks:
    Disk 1 and 2 at the primary IDE bus.
    Disk 3 connected via Promise Ultra 133 IDE controller.
    I want to install Solaris 8 Intel x86 edition on Disk 3, but the installation
    program only lists disks 1 and 2 as locations for install.
    Is there any method how to get Solaris 8 installed on Disk 3?
    Thank you very much for your help!
    Thomas

    Hello Michael,
    thanks for the information.
    There is no support for the Promise Ultra 133 IDE controller listed.
    Also, searching the internet for a private developed driver was not
    successful.
    Anyway, I have tried to make a test installation on a hard disk
    connected to the primary IDE controller and I detected a lot of
    further installation problems with my equipments because of
    missing or not properly identified drivers.
    So I think I have to make further investigations on concepts
    how to get Solaris 8 run in the best way.
    Thanks again for your help,
    Thomas

  • Solaris 8 x86: Installation on disk connected via IDE controller

    I have a PC with a Pentium 4 processor and the following IDE disks:
    Disk 1 and 2 at the primary IDE bus.
    Disk 3 connected via Promise Ultra 133 IDE controller.
    I want to install Solaris 8 Intel x86 edition on Disk 3, but the installation
    program only lists disks 1 and 2 as locations for install.
    Is there any method how to get Solaris 8 installed on Disk 3?
    Thank you very much for your help!

    Hello Michael,
    thanks for the information.
    There is no support for the Promise Ultra 133 IDE controller listed.
    Also, searching the internet for a private developed driver was not
    successful.
    Anyway, I have tried to make a test installation on a hard disk
    connected to the primary IDE controller and I detected a lot of
    further installation problems with my equipments because of
    missing or not properly identified drivers.
    So I think I have to make further investigations on concepts
    how to get Solaris 8 run in the best way.
    Thanks again for your help,
    Thomas

  • CSV disk signature and backup

    I would like to be able to take a snapshot backup of a CSV directly from my SAN and mount it back into the cluster in orer to recover files. 
    Right now, if i do this, the cluster detects the disk as a CSV (presumably a pre-existing CSV), i guess there is a signature on the disk identifying it as a particular cluster shared volume. This makes perfect sense. 
    Is there some way of remove this signature\ID, to ostensibly allow me to have two copies if the same disk mounted at any one time? I.e. one as CSV, which remains unaffected and in use, and one as a 'normal' disk which i can mount and assign a drive letter
    to? 
    Cheers.

    Mount the disk on a standalone system and use diskpart to change the signature, then mount the disk with the changed signature on the cluster.
    DISKPART> list disk
    DISKPART> uniqueid disk (get current signature)
    DISKPART> select disk ID
    DISKPART> uniqueid disk ID=[NEW SIGNATURE]
    . : | : . : | : . tim

Maybe you are looking for