Cluster resource ' Disk Name' of type 'Physical Disk' in clustered role 'Role Name' failed.

We have been observing issues with our file Cluster (Windows Server 2012 R2 Std Clustered with 2 Nodes) where File Server gets
unresponsive for SMB access request event id 30809 in Microsoft-Windows-SMBClient/Connectivity is observed
and when we try to failover the role clustered disks fail to get offline with an error in event id 1069 Cluster resource ' Disk Name' of type 'Physical Disk' in clustered role 'Role Name' failed, we have to force fully reboot the node which faces this
issue. It works properly for a week and again we get the same issue, this happens with all the disks in different file server roles.
Regards Ajinkya Ghare MCITP-Server Administrator | MCTS

we didn't found any thing in the cluster logs, in the WitnessClientAdmin logs we found errors related to failed registration
Witness Client failed registration request for \\fileserver\sharename with error (The request is not supported.)
Regards Ajinkya Ghare MCITP-Server Administrator | MCTS

Similar Messages

  • Cluster resource 'Analysis Services' of type 'Generic Service' in clustered role 'SQL Server' failed.

    Windows Server 2012 R2
    SQL Server 2012
    After a recent cluster failover from node 1 to node 2, the Analysis Services role is in a failed state, with the service stopped. When attempting to start the service, there are two error messages captured in Failover Cluster Manager:
    Log Name:      System
    Source:        Microsoft-Windows-FailoverClustering
    Date:          4/10/2014 11:48:49 AM
    Event ID:      1042
    Task Category: Generic Service Resource
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      HQ-HASQL-1.sbgnet.int
    Description:
    Generic service 'Analysis Services (HASQL)' failed with error '1067'. Please examine the application event log.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
        <EventID>1042</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>16</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-04-10T15:48:49.752168200Z" />
        <EventRecordID>26212</EventRecordID>
        <Correlation />
        <Execution ProcessID="9036" ThreadID="14748" />
        <Channel>System</Channel>
        <Computer>HQ-HASQL-1.sbgnet.int</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="ResourceName">Analysis Services (HASQL)</Data>
        <Data Name="Status">1067</Data>
      </EventData>
    </Event>
    Log Name:      System
    Source:        Microsoft-Windows-FailoverClustering
    Date:          4/10/2014 11:48:49 AM
    Event ID:      1069
    Task Category: Resource Control Manager
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      HQ-HASQL-1.sbgnet.int
    Description:
    Cluster resource 'Analysis Services (HASQL)' of type 'Generic Service' in clustered role 'SQL Server (HASQL)' failed.
    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster
    Manager or the Get-ClusterResource Windows PowerShell cmdlet.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
        <EventID>1069</EventID>
        <Version>1</Version>
        <Level>2</Level>
        <Task>3</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-04-10T15:48:49.752168200Z" />
        <EventRecordID>26213</EventRecordID>
        <Correlation />
        <Execution ProcessID="6464" ThreadID="9076" />
        <Channel>System</Channel>
        <Computer>HQ-HASQL-1.sbgnet.int</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="ResourceName">Analysis Services (HASQL)</Data>
        <Data Name="ResourceGroup">SQL Server (HASQL)</Data>
        <Data Name="ResTypeDll">Generic Service</Data>
      </EventData>
    </Event>
    With just these generic error messages being present, this has been difficult to diagnose. Some research has yielded possible resolutions of the Event Viewer log being full, .NET corruption, missing registry entries, but none of those seem to be the issue
    (Event Viewer logs cleared, Analysis services is working on the same physical servers in a different cluster, and the registry entries was only a supported issue for SQL Server 2008 and 2008 R2).
    Any help would be greatly appreciated.

    Bring up Configuration Manager, look at binary path for SSAS.  Make sure BOTH folders exist.  Sometimes with failovers mappings get screwed up.

  • Name : leopard Type : Volume  Disk Identifier : disk1s2 Mount Point

    Early in October, after installing SL and the first upgrade, I began experiencing colour flashes on transitions on slideshow projects created in iMovie '09. I contacted Apple Support and began working with one of the technicians. She reported that after viewing a short sample slideshow/movie that I sent her, Apple engineers concluded that something in SL was interfering with the video card. So far, no fix from Apple.
    One workaround suggested by a reader on these support discussions was to install Leopard on an external drive and work with iMovie from there. My contact person helped me connect and set up the external drive. She also talked me through steps that allowed me to continue using iMovie '09, my photos in iPhoto, and the iTunes Music Library on my internal drive to build my slideshows and have all of this 'show up' on the external drive. Really, all I was doing on the external drive was using iMovie to export my project and create a *.mov file.
    Until three days ago, I hadn't tried to access the external drive for about a month and I found that I couldn't. I called Apple Support again for help. In the end, the person I was working with suggested that he would get in touch with my first contact to see if written instructions could be sent to me so that I could repeat her process. At the same time, he suggested I ask for help here. When I first noticed the problem, the icon for the external drive was on my desktop; today it isn't. Below is the information that is relevant (I hope).
    *+From Disc Utility: Information on External Drive+*
    Name : leopard
    Type : Volume
    Disk Identifier : disk1s2
    Mount Point : Not mounted
    File System : Mac OS Extended (Journaled)
    Connection Bus : USB
    Device Tree : IODeviceTree:/PCI0@0/USB7@1D,7
    Writable : Yes
    Universal Unique Identifier : CED756E6-8A72-33BB-B79B-469908923E54
    Capacity : 999.16 GB (999,157,620,736 Bytes)
    Owners Enabled : No
    Can Turn Owners Off : Yes
    Can Be Formatted : Yes
    Bootable : Yes
    Supports Journaling : Yes
    Journaled : No
    Disk Number : 1
    Partition Number : 2
    *+Information from First Aid/Repair Disc+*
    Invalid node structure
    The volume leopard could not be verified completely.
    Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    *+Information at bottom of Disc Utility Window:+*
    Mount Point : Not mounted Capacity : 999.16 GB (999,157,620,736 Bytes)
    Format : Mac OS Extended (Journaled) Available : -
    Owners Enabled : - Used : -
    Number of Folders : - Number of Files : -
    I have no idea what is wrong or what to do now. I do know that the first thing is to reformat the drive, but I don't know how to do that. The second thing will be to install all the upgrades so that both internal and external drives are exactly the same - that I can manage! The third thing is to figure out how to get back to the original set up.
    If anyone can help or point me to sites that will tell me how to do any or all of this, I will be most appreciative.

    {quote:}I wanted help with two things: (1) getting the external HD back up and (2) reestablishing the connections that had been made so that iMovie, iPhoto, and iTunes pointed back to those applications and libraries on the internal HD. In other words, before I lost the connection to the external HD, when I clicked on iMovie on the external HD, what opened was iMovie on the internal HD, with all of my projects available. Same with the other two.{quote}
    To be honest I'm not sure why you were opening an Applications from the External HD and pointing it to the Library on the Internal HD? Seem's like it would be a lot simpler and easier just to open and run everything right from the Internal HD. Some folk's will open and run the Application from there Internal HD and then point it to the Library on the External HD, but you need to be very careful doing so because if the external HD fails then you lose your data.
    {quote:}Until about 3 hours ago, I couldn't use Disk Utility to erase the external HD and start over because the icon wasn't showing in the Devices panel. I have been at this all day and finally the icon did appear and I erased the external drive. After 4 attempts to reinstall Leopard OS, that, too finally worked. I have now reinstalled iLife '09 and all of the necessary upgrades.{quote}
    Not sure why you lost the connection to the External HD, could be just a bad connection or a early warning sign for a failing drive?
    {quote:}I knew that if I erased the external HD I would lose all of the connections I had between the two drives. That was why I was hoping for a way to fix it without erasing. So now I need help with (2) above: reestablishing those connections. I'm afraid I don't understand partitioning - what it is or what it does. If you have time to explain it to me, I will certainly give it a try.{quote}
    I think you need to run everything from your Internal HD and only use the External HD as a backup drive either with Time Machine or on the great advise of elmac using SuperDuper.
    As for Partitioning and Formatting I can give you some article's to study, but would suggest not fussing or experimenting unless you had a second External HD to play around with.
    Dennis

  • Getting only name of the physical disk from cluster group

    hi experts,
    i want to know the name of my cluster disk example - `Cluster Disk 2` available in a cluster group. Can i write a command something like below.
    Get-ClusterGroup –Name FileServer1 | Get-ClusterResource   where  ResourceType is Physical Disk
    Thanks
    Sid
    sid

    thanks Chaib... its working.
    However i tried this
    Get-ClusterGroup
    ClusterDemoRole
    | Get-ClusterResource
    | fl name
    |  findstr
    "physical Disk"
    which is also working.
    sid

  • HP Pavilion dv7 6031eo hard disk voodoo, making 2 physical disk appear as 1 physical disk

    My HP Pavilion dv7 6031eo hard disk is failing.  88 Bad sectors.
    I was planning to bring new hard disk. I decided to look under hood to see what kind of disk I would need.
    Suprise suprise, I already had 2 hard disk in my HP Pavilion dv7 6031eo. Windows detects only 1 hard disk. It is detected as TOSHIBA MK1059GSM.
    So 2 things are possible :-
    HP performs the feature of a "spanned disk" at the mother board level and hides dual/double disks from the OS. It then presents to OS a single disk of 1TB as TOSHIBA MK1059GSM (not sure why TOSHIBA)
    HP forgot the plug in the second hard disk during manufacturing
    Which one is it ?
    Now the thing(s) is/are failing as per SMART values.
    How am I suppose to replace the disk ? 
    Do I need to replace both of disks, even though only a single disk is failing as per OS ?
    Will replacing the disks with any other disk work or the HP firmware will go nuts ?
    Why don't you document these things ? 

    I would replace the hard drive. That is a 640 gig 5400 rpm drive and you can get a bigger faster drive for a reasonable price. 
    http://www.newegg.com/Product/Product.aspx?Item=9SIA2W014M8026
    If the computer is still working well enough to boot into Windows you can do a complete system backup and recover all your data, settings, programs, etc onto the new drive or we can help you do a disk clone of the old drive to the new. 
    Since your laptop will actually hold two hard drives simultaneously you could even put the old drive in the secondary bay so you have a copy of all your old stuff right at hand. 
    This video will be helpful:
    https://www.youtube.com/watch?v=EZgiX-pzdL8
    Post back if you need any more help. 
    If this is "the Answer" please click "Accept as Solution" to help others find it. 

  • Powershell- Associate Mount Point to Physical Disk

    I need to be able to associate mount points (Get-WmiObject -Class Win32_MountPoint) with the physical drive on which it resides.
    Scenario: I have physical disks (SAN LUNs) mounted as folders on an E: drive (also a SAN LUN) of a server.  I need to be able to, via a PowerShell script, associate the "folder" name to the physical disk (i.e., Harddisk4 or PhysicalDrive4).
    I can get Mount Point associated with the Volume, etc., but can't make the link to the physical disk.
    Any help is appreciated.

    Unfortunately there isn't an association class between mount points and physical disks like there is between logical and physical disks. I did a blog about finding partition alignment which required using Win32_LogicalDiskToPartition class. One of the comments
    suggested using Sysinternals diskext as workaround. See comments:
    http://sev17.com/2009/02/disk-alignment-partitioning-the-good-the-bad-the-ok-and-the-not-so-ugly/

  • What is the difference between Logical Disk and Physical Disk?

    Hi.
    When I do Performance Monitor, I got Logical Disk Avg. Disk sec/Write counter and  Physical Disk Avg. Disk sec/Write counter.
    But I can see the different Avg. value and Max. value. 
    Even if Logical and Physical Disk are one-to-one mapping.
    Why did i get the result?
    One the other hands, I got a same result that Logical Disk Avg. Disk sec/Read counter and  Physical Disk Avg. Disk sec/Read counter's Avg. value and Max. value.

    Physical Disk refers to an actual physical HDD (or array in a hardware RAID setup), whereas Logical Disk refers to a Volume that has been created on that disk.
    So if you have one disk with one volume created on it then the values are likely to be 1 to 1, but if you have multiple volumes on the disk, for instance a physical disk with C:\ and D:\ volumes running on it, then the logical disks relate to c:\ and d:\
    rather than the disk they're running on.
    See
    http://blogs.technet.com/b/askcore/archive/2012/03/16/windows-performance-monitor-disk-counters-explained.aspx for a more in depth explanation.

  • Losing disk partition after choosing startup disk

    Hi,
    I'm using MB Pro retina 2012, I have 3 disk partitions. 1 for Mac osx, 1 for windows (bothcamp) and 1 for data (ExFAT). I using it normally until I change startup disk to Windows. After that, data drive is not show anymore. I have more than 100GB important data on this drive. What happend? How to restore them? I cant repair disk, it doesnt work for me. It show like this on disk utility.
    I've tried to mount it, repair, verify but not successful. This is the log:
    2013-07-18 15:39:32 +0700: Disk Utility started.
    2013-07-18 15:44:53 +0700: Verifying partition map for “APPLE SSD SM512E Media”
    2013-07-18 15:44:53 +0700: Starting verification tool:
    2013-07-18 15:44:53 +0700: Checking prerequisites
    2013-07-18 15:44:53 +0700: Checking the partition list
    2013-07-18 15:44:53 +0700: Checking for an EFI system partition
    2013-07-18 15:44:53 +0700: Checking the EFI system partition’s size
    2013-07-18 15:44:53 +0700: Checking the EFI system partition’s file system
    2013-07-18 15:44:53 +0700: Checking all HFS data partition loader spaces
    2013-07-18 15:44:53 +0700: Checking Core Storage Physical Volume partitions
    2013-07-18 15:44:53 +0700: The partition map appears to be OK
    2013-07-18 15:44:53 +0700:
    2013-07-18 15:44:53 +0700:
    2013-07-18 15:44:55 +0700: Verifying and repairing partition map for “APPLE SSD SM512E Media”
    2013-07-18 15:44:55 +0700: Starting repair tool:
    2013-07-18 15:44:55 +0700: Checking prerequisites
    2013-07-18 15:44:55 +0700: Checking the partition list
    2013-07-18 15:44:55 +0700: Adjusting partition map to fit whole disk as required
    2013-07-18 15:44:55 +0700: Checking for an EFI system partition
    2013-07-18 15:44:55 +0700: Checking the EFI system partition’s size
    2013-07-18 15:44:55 +0700: Checking the EFI system partition’s file system
    2013-07-18 15:44:55 +0700: Checking all HFS data partition loader spaces
    2013-07-18 15:44:55 +0700: Reviewing boot support loaders
    2013-07-18 15:44:55 +0700: Checking Core Storage Physical Volume partitions
    2013-07-18 15:44:55 +0700: Updating Windows boot.ini files as required
    2013-07-18 15:44:55 +0700: The partition map appears to be OK
    2013-07-18 15:44:55 +0700:
    2013-07-18 15:44:55 +0700:
    2013-07-18 15:51:33 +0700: Disk Utility started.
    2013-07-18 15:59:19 +0700: Disk Utility started.
    2013-07-18 15:59:36 +0700: Preparing to remove partition from disk: “APPLE SSD SM512E Media”
    2013-07-18 15:59:36 +0700:           Partition Scheme: GUID Partition Table
    2013-07-18 15:59:36 +0700:           1 partition will be removed
    2013-07-18 15:59:36 +0700:           1 partition will not be changed
    2013-07-18 15:59:36 +0700:
    2013-07-18 15:59:36 +0700:           Partition 1
    2013-07-18 15:59:36 +0700:                     Name                    : “Mac”
    2013-07-18 15:59:36 +0700:                     Size                    : 101.93 GB
    2013-07-18 15:59:36 +0700:                     File system          : Mac OS Extended (Journaled)
    2013-07-18 15:59:36 +0700:                     Do not erase contents
    2013-07-18 15:59:36 +0700:
    2013-07-18 15:59:36 +0700:           Partition 2
    2013-07-18 15:59:36 +0700:                     Size                    : 398 GB
    2013-07-18 15:59:36 +0700:                     File system          : Free Space
    2013-07-18 15:59:36 +0700:
    2013-07-18 15:59:36 +0700: Beginning partition operations
    2013-07-18 15:59:36 +0700: Unmounting disk
    2013-07-18 15:59:36 +0700: Finishing partition modifications
    2013-07-18 15:59:36 +0700: Waiting for the disks to reappear
    2013-07-18 15:59:36 +0700: Partition complete.
    2013-07-18 15:59:36 +0700:
    2013-07-18 15:59:42 +0700: Preparing to partition disk: “APPLE SSD SM512E Media”
    2013-07-18 15:59:42 +0700:           Partition Scheme: GUID Partition Table
    2013-07-18 15:59:42 +0700:           1 partition will be created
    2013-07-18 15:59:42 +0700:
    2013-07-18 15:59:42 +0700:           Partition 1
    2013-07-18 15:59:42 +0700:                     Name                    : “Mac”
    2013-07-18 15:59:42 +0700:                     Size                    : 499.93 GB
    2013-07-18 15:59:42 +0700:                     File system          : Mac OS Extended (Journaled)
    2013-07-18 15:59:42 +0700:                     Do not erase contents
    2013-07-18 15:59:42 +0700:
    2013-07-18 15:59:42 +0700: Beginning partition operations
    2013-07-18 15:59:42 +0700: Verifying the disk
    2013-07-18 15:59:42 +0700: Checking file system
    2013-07-18 15:59:42 +0700: Performing live verification.
    2013-07-18 15:59:42 +0700: Checking Journaled HFS Plus volume.
    2013-07-18 15:59:42 +0700: Checking extents overflow file.
    2013-07-18 15:59:42 +0700: Checking catalog file.
    2013-07-18 15:59:53 +0700: Checking multi-linked files.
    2013-07-18 15:59:53 +0700: Checking catalog hierarchy.
    2013-07-18 15:59:53 +0700: Checking extended attributes file.
    2013-07-18 15:59:53 +0700: Checking volume bitmap.
    2013-07-18 15:59:53 +0700: Checking volume information.
    2013-07-18 15:59:53 +0700: The volume Mac appears to be OK.
    2013-07-18 15:59:53 +0700: Unmounting disk
    2013-07-18 15:59:53 +0700: Finishing partition modifications
    2013-07-18 15:59:53 +0700: Waiting for the disks to reappear
    2013-07-18 15:59:53 +0700: Growing disk
    2013-07-18 15:59:54 +0700: Partition complete.
    2013-07-18 15:59:54 +0700:
    2013-07-18 16:36:53 +0700: Disk Utility started.
    2013-07-18 16:37:07 +0700: Preparing to partition disk: “APPLE SSD SM512E Media”
    2013-07-18 16:37:07 +0700:           Partition Scheme: GUID Partition Table
    2013-07-18 16:37:07 +0700:           3 partitions will be created
    2013-07-18 16:37:07 +0700:
    2013-07-18 16:37:07 +0700:           Partition 1
    2013-07-18 16:37:07 +0700:                     Name                    : “Mac”
    2013-07-18 16:37:07 +0700:                     Size                    : 100 GB
    2013-07-18 16:37:07 +0700:                     File system          : Mac OS Extended (Journaled)
    2013-07-18 16:37:07 +0700:                     Do not erase contents
    2013-07-18 16:37:07 +0700:
    2013-07-18 16:37:07 +0700:           Partition 2
    2013-07-18 16:37:07 +0700:                     Name                    : “Mac 2”
    2013-07-18 16:37:07 +0700:                     Size                    : 298.93 GB
    2013-07-18 16:37:07 +0700:                     File system          : Mac OS Extended (Journaled)
    2013-07-18 16:37:07 +0700:
    2013-07-18 16:37:07 +0700:           Partition 3
    2013-07-18 16:37:07 +0700:                     Name                    : “BOOTCAMP”
    2013-07-18 16:37:07 +0700:                     Size                    : 101 GB
    2013-07-18 16:37:07 +0700:                     File system          : Windows NT File System (NTFS)
    2013-07-18 16:37:07 +0700:                     Do not erase contents
    2013-07-18 16:37:07 +0700:
    2013-07-18 16:37:07 +0700: Beginning partition operations
    2013-07-18 16:37:07 +0700: Verifying the disk
    2013-07-18 16:37:07 +0700: Checking file system
    2013-07-18 16:37:07 +0700: Performing live verification.
    2013-07-18 16:37:07 +0700: Checking Journaled HFS Plus volume.
    2013-07-18 16:37:07 +0700: Checking extents overflow file.
    2013-07-18 16:37:18 +0700: Checking catalog file.
    2013-07-18 16:37:19 +0700: Checking multi-linked files.
    2013-07-18 16:37:19 +0700: Checking catalog hierarchy.
    2013-07-18 16:37:19 +0700: Checking extended attributes file.
    2013-07-18 16:37:19 +0700: Checking volume bitmap.
    2013-07-18 16:37:19 +0700: Checking volume information.
    2013-07-18 16:37:19 +0700: The volume Mac appears to be OK.
    2013-07-18 16:37:19 +0700: Shrinking the disk
    2013-07-18 16:37:19 +0700: Unmounting disk
    2013-07-18 16:37:19 +0700: Finishing partition modifications
    2013-07-18 16:37:19 +0700: Waiting for the disks to reappear
    2013-07-18 16:37:20 +0700: Formatting disk0s5 as Mac OS Extended (Journaled) with name Mac 2
    2013-07-18 16:37:21 +0700: Initialized /dev/rdisk0s5 as a 278 GB HFS Plus volume with a 24576k journal
    2013-07-18 16:37:21 +0700: Mounting disk
    2013-07-18 16:37:21 +0700: Partition complete.
    2013-07-18 16:37:21 +0700:
    2013-07-18 16:37:35 +0700: Preparing to erase : “Data”
    2013-07-18 16:37:35 +0700:           Partition Scheme: GUID Partition Table
    2013-07-18 16:37:35 +0700:           1 volume will be erased
    2013-07-18 16:37:35 +0700:                     Name                    : “Data”
    2013-07-18 16:37:35 +0700:                     Size                    : 298.8 GB
    2013-07-18 16:37:35 +0700:                     File system          : ExFAT
    2013-07-18 16:37:35 +0700: Unmounting disk
    2013-07-18 16:37:35 +0700: Erasing
    2013-07-18 16:37:35 +0700: Volume name      : Data
    Partition offset : 195984280 sectors (100343951360 bytes)
    Volume size      : 583593064 sectors (298799648768 bytes)
    Bytes per sector : 512
    Bytes per cluster: 131072
    FAT offset       : 2048 sectors (1048576 bytes)
    # FAT sectors    : 18432
    Number of FATs   : 1
    Cluster offset   : 20480 sectors (10485760 bytes)
    # Clusters       : 2279580
    Volume Serial #  : 51e7b75f
    Bitmap start     : 2
    Bitmap file size : 284948
    Upcase start     : 5
    Upcase file size : 5836
    Root start       : 6
    2013-07-18 16:37:35 +0700: Mounting disk
    2013-07-18 16:37:35 +0700: Erase complete.
    2013-07-18 16:37:35 +0700:
    2013-11-07 13:52:44 +0700: Disk Utility started.
    2013-11-07 14:04:32 +0700:
              Name :           disk0s3
              Type :           Partition
              Disk Identifier :           disk0s3
              Mount Point :           Not mounted
              File System :           MS-DOS (FAT)
              Connection Bus :           SATA
              Device Tree :           IODeviceTree:/PCI0@0/SATA@1F,2/PRT0@0/PMP@0
              Writable :           Yes
              Capacity :           298.8 GB (298,799,648,768 Bytes)
              Owners Enabled :           No
              Can Turn Owners Off :           No
              Can Be Formatted :           Yes
              Bootable :           No
              Supports Journaling :           No
              Journaled :           No
              Disk Number :           0
              Partition Number :           3
    2013-11-07 14:26:36 +0700: Disk Utility started.
    2013-11-07 14:26:47 +0700: Verify and Repair volume “disk0s3”
    2013-11-07 14:26:47 +0700: Starting repair tool:
    2013-11-07 14:26:47 +0700: Checking file system2013-11-07 14:26:47 +0700: ** /dev/disk0s3
    2013-11-07 14:26:47 +0700: Invalid sector size: 0
    2013-11-07 14:26:47 +0700: Volume repair complete.2013-11-07 14:26:47 +0700: Updating boot support partitions for the volume as required.2013-11-07 14:26:47 +0700: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.2013-11-07 14:26:47 +0700:
    2013-11-07 14:26:47 +0700: Disk Utility stopped repairing “disk0s3”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    2013-11-07 14:26:47 +0700:
    2013-11-07 14:27:21 +0700: Verifying volume “disk0s3”
    2013-11-07 14:27:21 +0700: Starting verification tool:
    2013-11-07 14:27:21 +0700: Checking file system2013-11-07 14:27:21 +0700: ** /dev/disk0s3
    2013-11-07 14:27:21 +0700: Invalid sector size: 0
    2013-11-07 14:27:21 +0700: Error: This disk needs to be repaired. Click Repair Disk.2013-11-07 14:27:21 +0700:
    2013-11-07 14:27:21 +0700: Disk Utility stopped verifying “disk0s3”: This disk needs to be repaired. Click Repair Disk.
    2013-11-07 14:27:21 +0700:
    2013-11-07 14:27:30 +0700: Verify and Repair volume “disk0s3”
    2013-11-07 14:27:30 +0700: Starting repair tool:
    2013-11-07 14:27:30 +0700: Checking file system2013-11-07 14:27:30 +0700: ** /dev/disk0s3
    2013-11-07 14:27:30 +0700: Invalid sector size: 0
    2013-11-07 14:27:30 +0700: Volume repair complete.2013-11-07 14:27:30 +0700: Updating boot support partitions for the volume as required.2013-11-07 14:27:30 +0700: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.2013-11-07 14:27:30 +0700:
    2013-11-07 14:27:30 +0700: Disk Utility stopped repairing “disk0s3”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    2013-11-07 14:27:30 +0700:
    2013-11-07 14:32:17 +0700:
              Name :           APPLE SSD SM512E Media
              Type :           Disk
              Partition Map Scheme :           GUID Partition Table
              Disk Identifier :           disk0
              Media Name :           APPLE SSD SM512E Media
              Media Type :           Generic
              Connection Bus :           SATA
              Device Tree :           IODeviceTree:/PCI0@0/SATA@1F,2/PRT0@0/PMP@0
              Writable :           Yes
              Ejectable :           No
              Location :           Internal
              Solid State Disk :           Yes
              Total Capacity :           500.28 GB (500,277,790,720 Bytes)
              Disk Number :           0
              Partition Number :           0
              S.M.A.R.T. Status :           Verified
              Raw Read Error :           000000000000
              Reallocated Sector Count :           000000000000
              Power On Hours :           0000000003B2
              Power Cycle :           000000000DD0
              Temperature :           004F00040027
              UDMA CRC Error (PATA only) :           000000000000
    2013-11-07 14:39:58 +0700:
              Name :           disk0s3
              Type :           Partition
              Disk Identifier :           disk0s3
              Mount Point :           Not mounted
              File System :           MS-DOS (FAT)
              Connection Bus :           SATA
              Device Tree :           IODeviceTree:/PCI0@0/SATA@1F,2/PRT0@0/PMP@0
              Writable :           Yes
              Capacity :           298.8 GB (298,799,648,768 Bytes)
              Owners Enabled :           No
              Can Turn Owners Off :           No
              Can Be Formatted :           Yes
              Bootable :           No
              Supports Journaling :           No
              Journaled :           No
              Disk Number :           0
              Partition Number :           3
    2013-11-07 14:43:11 +0700: Disk Utility started.
    Thanks for help

    You CAN'T have 3 partitions on your Mac and have the Windows install work. Windows only allows 4 Primary partitions on any one physical hard drive. Since you created a exFAT partition you have past that Windows limit.
    One partition for OS X, one for Windows, one for the OS X Recovery HD and the forth for the EFI. Now that you have created a so called Data partition windows will no longer boot.
    You are basically TOAST and might need to start over with a total wipe, Re-Partitioning, of the drive then reinstall OS X and you programs and files then reinstall Windows program and files and then do not try fooling with the partitions again, any of them on the OS X or Windows side, because if you do Windows again will not boot.

  • Cannot use file for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Serve

    Hi
    Windows serv 2012 cluster on sql 2012 cluster with 2 instance. on works fine , Second instanc ewhen i try to creat DB a get this message. 
    Cannot use file  for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql
    Server does not have a dependency on it.
    CREATE DATABASE failed. Some file names listed could not be created. Check related errors. (Microsoft SQL Server, Error: 5184)
    Any help please
    kam
    KAMEL

    Hi Saurabh
    Exactly I have SQL SERVER 2012
    Failover Clustering   in windows server 2012 with two nodes with
    two instances and exactly I run them in the same server and each instance with
    three drives Backup, Data and log.   
    KAMEL

  • HT201376 Hello, I am trying to reset my macbook pro to its factory settings but I can't type the name of the formatted disk nor can I click on erase, as this feature is disabled. Could you please assist?

    Hello, I am trying to reset my macbook pro to its factory settings but I can't type the name of the formatted disk nor can I click on erase, as this feature is disabled. The 'type name' space and the 'erase' button are in light grey - Could you please assist?

    Hello!
    Did you boot to the Internet Recovery Partition?
    Here’s how:
    1/ Make sure your computer is completely shut down.
    2/ You’ll have to be quick next: Press the Mac’s power button. As soon as you either hear the loud chime, or see the display light up - usually after a second or 2 - on your keyboard press [alt] + [cmd] + [r] Keep these keys on your keyboard pressed until you see a spinning globe with the text “starting Internet Recovery” You might have to connect to your Wi-Fi network before you can continue here.
    After a few minutes, you’ll be presented with a Utilities screen. This is the Internet Recovery partition. If this step is already giving you problems, try using a USB-keyboard. It doesn’t have to be an Apple-keyboard. If you have a Windows-tailored keyboard laying around, use the “Windows-flag” key in stead of the [cmd]-key and it should also work.
    3/ Choose Disk Utility and click [continue]

  • Cluster resource 'SQL Network Name (SQLCLUS1)' of type 'Network Name' in clustered role 'SQL Server (DB1)' failed.

    Cluster resource 'SQL Network Name (SQLCLUS1)' of type 'Network Name' in clustered role 'SQL Server (DB1)' failed.
    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster
    Manager or the Get-ClusterResource Windows PowerShell cmdlet.
    I keep getting this error message. Can someone please help. Thank You.
    Kranp.

    Hi Kranp,
    As the issue is more related to Windows Server high availability
    , I recommend you post the question in the
     Windows Server High Availability (Clustering)
     forum. It is appropriate and more experts will assist you.
    Besides, there are similar threads regarding to the above error for your reference.
    2012 Cluster service name failing
    SQL 2012 Failover Cluster - unable to start because
    of 'Network Name' failed
    Issues with resource creation on W2K12 SQL
    failover cluster, confirm procedures
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • OVS 2.2 :: Unable to install RHEL HVM on physical disk from command line

    [root@ovs2 xen]# /usr/sbin/virt-install hvm name=test2 ram=1024 vcpus=1 bridge=xenbr0 file /dev/sdc --nographics
    What would you like to use for the virtual CD image? /var/ovs/mount/1FB2E6B36D21418792A1DD30B62C689F/iso_pool/rhel-server-5.6-x86_64-dvd.iso
    Starting install...
    Guest installation complete... restarting guest.
    exception was: Domain named test2 already exists!
    Domain installation may not have been
    successful. If it was, you can restart your domain
    by running 'xm create -c test2'; otherwise, please
    restart your installation.
    [root@ovs2 xen]# more test2
    # Automatically generated xen config file
    name = "test2"
    builder = "hvm"
    memory = "1024"
    disk = [ 'phy:/dev/sdc,hda,w', ]
    vif = [ 'type=ioemu, mac=00:16:3e:3d:d0:5c, bridge=xenbr0', ]
    uuid = "f99f6a07-6d03-a0ae-8f2f-a7a0e1af5e31"
    device_model = "/usr/lib/xen/bin/qemu-dm"
    kernel = "/usr/lib/xen/boot/hvmloader"
    nographic=1
    timer_mode=0
    apic=1
    acpi=1
    pae=1
    vcpus=1
    serial = "pty" # enable serial console
    on_reboot = 'restart'
    on_crash = 'restart'
    [root@ovs2 xen]# xm console test2
    xenconsole: Could not read tty from store: No such file or directory
    [root@ovs2 xen]#
    + No errors in xend.log or qemu-*.log
    + hypervisor inittab is default .. co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav
    Using similar syntax, and installing paravirtualized guest to physical disk works fine.
    [root@ovs2 xen]# /usr/sbin/virt-install paravirt name=demo3 ram=1024 vcpus=2 bridge=xenbr0 file=/dev/sdc nographics location=http://192.168.229.74/RHEL5764bit
    Starting install...
    Bootdata ok (command line is method=http://192.168.229.74/RHEL5764bit )
    Linux version 2.6.18-238.el5xen ([email protected]) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-50)) #1 SMP Sun Dec 19 14:42:02 EST 2010
    BIOS-provided physical RAM map:
    Xen: 0000000000000000 - 0000000040800000 (usable)
    No mptable found.
    Built 1 zonelists. Total pages: 264192
    Kernel command line: method=http://192.168.229.74/RHEL5764bit ...................................
    Any suggestions ??

    and i go to the temp mountpoint that the script will mount on
    Starting install...
    ERROR: Invalid NFS location given: [Errno 2] No such file or directory: '/var/lib/xen/xennfs.7x4Rf4/boot/x86_64/vmlinuz-xen'
    [root@ovs2 opt1]# df
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/cciss/c0d0p2 3050092 3033308 0 100% /
    /dev/cciss/c0d0p1 101086 47114 48753 50% /boot
    tmpfs 288856 0 288856 0% /dev/shm
    none 288768 40 288728 1% /var/lib/xenstored
    /dev/cciss/c0d0p3 288623616 301056 288322560 1% /var/ovs/mount/A52CB661C1CF41D198D50F6379822694
    /var/isos/OracleLinux-R5-U7-Server-x86_64-dvd.iso
    3755446 3755446 0 100% /el/EL5-x86
    192.168.229.110:/el/EL5-x86
    3755456 3755456 0 100% /opt1
    192.168.229.110:/el/EL5-x86/
    3755456 3755456 0 100% /var/lib/xen/xennfs.NnE54I
    [root@ovs2 opt1]# cd /var/lib/xen/xen
    xend-db/ xennfs.7jHT0q/ xennfs.fQNnQD/ xennfs.LR6hDx/ xennfs.QnxyeH/
    xennfs.5Pr0vm/ xennfs.8aMSAA/ xennfs.fRhXiN/ xennfs.NnE54I/ xennfs.yEw4KL/
    [root@ovs2 opt1]# cd /var/lib/xen/xen
    xend-db/ xennfs.7jHT0q/ xennfs.fQNnQD/ xennfs.LR6hDx/ xennfs.QnxyeH/
    xennfs.5Pr0vm/ xennfs.8aMSAA/ xennfs.fRhXiN/ xennfs.NnE54I/ xennfs.yEw4KL/
    [root@ovs2 opt1]# cd /var/lib/xen/xennfs.NnE54I/
    [root@ovs2 xennfs.NnE54I]# ls
    blafdoc.css EULA GPL README-en RELEASE-NOTES-en.html Server VT
    Cluster eula.en_US images README-en.html RPM-GPG-KEY supportinfo
    ClusterStorage eula.py isolinux RELEASE-NOTES-en RPM-GPG-KEY-oracle TRANS.TBL
    [root@ovs2 xennfs.NnE54I]# find . -name vmlinuz\*
    ./images/pxeboot/vmlinuz
    ./images/xen/vmlinuz
    ./isolinux/vmlinuz
    [root@ovs2 xennfs.NnE54I]#

  • Storage Spaces - Remove Physical Disk from Simple layout

    I am running Server 2012 RTM with a single storage pool containing 4 drives - 2.73TB, 1.36TB, 465GB and 148GB. There is a single virtual disk created, with thin provisioning, using the Simple layout, with a current maximum size of 2.73TB, and with 1.32TB
    allocated. I want to remove the 148GB drive and replace it with a 465GB drive. When I right-click the 148GB disk and select Remove, I get a warning that Windows will attempt to rebuild any virtual disks that store data on the disk I'm trying to remove, and
    that in order to succeed, the storage pool must have enough free space to accommodate the data from the disk I'm trying to remove. There is more than enough space in the virtual disk to accommodate whatever files may be stored on the 148GB disk - over 1TB
    unallocated. However, when I confirm that I want to remove the disk from the pool, I get the following message:
    This physical disk is used by one or more virtual disks that use the Simple (no resiliency) layout. To remove this physical disk, delete the following virtual disks: Simple
    Surely the fact that it's a simple volume (rather than mirrored/parity) shouldn't affect the ability to move the data off the disk? It appears that disk removal is implemented as a simulated drive failure, forcing a rebuild of the resiliency data, rather
    than by simply moving the data off the disk onto other available disks.
    Additionally, after I've attempted to remove the disk, it's now been marked as 'Retired'.
    Is there any simple way to remove this disk?

    Same problem here, but I have some workaround for the problem.
    But, even in Windows Home Server with its awesome disk extender (predecessor of Storage Spaces) you had to take the shares (meaning volumes in our case) offline so you could take out the disk from the pool.
    Agree that it would make more sense to be able to remove disk from the pool online and the technology is most likely is already there: online cluster moves with defragmentation API was there for years and ReFS moves clusters online when it detects disk errors.
    Anyway here is the process that may work for you if taking volume offline is an option in your case:
    Try to remove physical disk in Server Manager - it will fail with abovementioned error, but the disk will go into "Retired" state.
    Now provision a new Virtual Disk and a volume of your choice. Most likely you will pick the same disk and volume type as you already had, but this is the chance to change the topology. You should be able to do this since you have a lot of physical disk
    space, especially if you used Thin provisioning.
    It looks like at this point retired physical disk is not included into the new Virtual Disk provisioning, but it is still accessible via existing virtual disk.
    Copy over all files from your old volume to a new volume.
    Now delete old Virtual Disk.
    If you want - change disk name and volume letter of new virtual disk that you created and new volume to what you had before.
    Now in Disk Manager take failing physical disk offline.
    Replace failing disk, initialize new disk and add it to the pool.
    Note: for me sometimes removing disk in via Storage Pool management GUI does not mark it as "Retired". In this case you can open PowerShell as Admin and assuming you want to remove PhysicalDisk2 - run the following command:
    Set-PhysicalDisk -FriendlyName PhysicalDisk2 -Usage Retired
    HTH

  • Physical disk not showing up in Disk Utility

    I'm in the process of selling my mac mini.
    I went to the disk utility and erased per the instructions here:
    http://support.apple.com/en-us/HT201065
    The only thing I did differently was I adjusted the security settings to do a pass of writing zeroes. 
    Then I went to reinstall OS X per the instructions and there was no drive available on the "select the disk where you want to install os x" screen.
    I tried to do a restore from backup and got the same symptom - no disk to restore to. Also doesn't show when I go to choose a startup disk.
    I went back to the Disk Utility and noticed some weirdness:
    - The Macintosh HD logical volume is showing in the upper left, but there's no physical disk showing as its parent! See attached screenshot - I can repair and verify the logical volume without any problems. It also says that the volume is online and has 1.1 TB as it should. 
    I've also tried resetting the NVRAM and PRAM, with no luck
    Any help is much appreciated!!!

    Hi PabloHoney1979,
    When I check my Mac I see the same Macintosh HD, Logical Volume Group with an indented partition under it. So it looks like you are looking at the physical disk without a partition on it.  Try the Partition tab and create a partition on the drive.
    Disk Utility 12.x: Partition a disk
    3.  In the Mac OS X Utilities window, select Disk Utility, and then click Continue.
    4.  Select the disk that you want to partition and click Partition.
    5.  Choose the number of partitions from the Volume Scheme pop-up menu.
    6.  Click each partition and type a name for it, choose a format, and type a size. You can also drag the divider between the partitions to change their sizes. If a partition’s name has an asterisk beside it, it’s shown larger than its actual size in order to display its name clearly.
    7.  If you’ll be using a partition as a Mac OS X startup disk, click Options, and choose the the GUID partition scheme.
    8.  Click Apply.
    Take care,
    Nubz

  • Is it possible to mount a physical disk (/dev/mapper/ disk) on one of my Oracle VM server

    I have a physical disk that I can see from multipath -ll  that shows up as such
    # multipath -ll
    3600c0ff00012f4878be35c5401000000 dm-115 HP,P2000G3 FC/iSCSI
    size=410G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=active
    | `- 7:0:0:49  sdcs 70:0   active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
      `- 10:0:0:49 sdcr 69:240 active ready running
    That particular is visible in the OVMM Gui as a physical disk that I can present to one of my VMs but currently its not presented to any of them.
    I have about 50 physical LUNs that my Oracle VM server can see.  I believe I can see all of them from a fdisk -l, but "dm-115" (which is from the multipath above) doesnt show up.
    This disk has 3 usable partitions on it, plus a Swap.
    I want to mount the 3rd partition temporarily on the OVM server itself and I receive
    # mount /dev/mapper/3600c0ff00012f4878be35c5401000000p3 /mnt
    mount: you must specify the filesystem type
    If I present the disk to a VM and then try to mount the /dev/xvdx3 partition -it of course works.  (x3 - represents the 3rd partition on what ever letter position the disk shows up as)
    Is this possible?

    Its more of the correct syntax. Like I can not seem to figure out how to translate the /dev/mapper path above into what fdisk -l shows. Perhaps if I knew how fdisk and multipath can be cross referenced I could mount the partition.
    I had already tried what you suggested. Here is the output if I present the disk to a VM and then mount the 3rd partition.
    # fdisk -l
    Disk /dev/xvdh: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/xvdh1   *           1          13      104391   83  Linux
    /dev/xvdh2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/xvdh3            2103       27783   206282632+  83  Linux
    /dev/xvdh4           27784       30394    20972857+   5  Extended
    /dev/xvdh5           27784       30394    20972826   83  Linux
    # mount /dev/xvdh3 /mnt  <-- no error
    # df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/xvda3            197G  112G   75G  60% /
    /dev/xvda5             20G 1011M   18G   6% /var
    /dev/xvda1             99M   32M   63M  34% /boot
    tmpfs                 2.0G     0  2.0G   0% /dev/shm
    /dev/xvdh3            191G   58G  124G  32% /mnt  <-- mounted just fine
    Its ext3 partition
    # df -T
    /dev/xvdh3
    ext3   199822096  60465024 129042944  32% /mnt
    Now if I go to my vm.cfg file, I can see the disk that is presented.
    My disk line contains
    disk = [...'phy:/dev/mapper/3600c0ff00012f4878be35c5401000000,xvdh,w', ...]
    Multipath shows that disk and says "dm-115" but that does not translate on fdisk
    # multipath -ll
    3600c0ff00012f4878be35c5401000000 dm-115 HP,P2000G3 FC/iSCSI
    size=410G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=active
    | `- 7:0:0:49  sdcs 70:0   active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
      `- 10:0:0:49 sdcr 69:240 active ready running
    I have around 50 disks on this server, but the ones of the same size from fdisk -l from the server shows me many.
    # fdisk -l
    Disk /dev/sdp: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdp1   *           1          13      104391   83  Linux
    /dev/sdp2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdp3            2103       27783   206282632+  83  Linux
    /dev/sdp4           27784       30394    20972857+   5  Extended
    /dev/sdp5           27784       30394    20972826   83  Linux
    Disk /dev/sdab: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdab1   *           1          13      104391   83  Linux
    /dev/sdab2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/sdab3            1319       27783   212580112+  83  Linux
    /dev/sdab4           27784       30394    20972857+   5  Extended
    /dev/sdab5           27784       30394    20972826   83  Linux
    Disk /dev/sdac: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdac1   *           1          13      104391   83  Linux
    /dev/sdac2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdac3            2103       27783   206282632+  83  Linux
    /dev/sdac4           27784       30394    20972857+   5  Extended
    /dev/sdac5           27784       30394    20972826   83  Linux
    Disk /dev/sdad: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdad1   *           1          13      104391   83  Linux
    /dev/sdad2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/sdad3            1319       27783   212580112+  83  Linux
    /dev/sdad4           27784       30394    20972857+   5  Extended
    /dev/sdad5           27784       30394    20972826   83  Linux
    Disk /dev/sdae: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdae1   *           1          13      104391   83  Linux
    /dev/sdae2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdae3            2103       27783   206282632+  83  Linux
    /dev/sdae4           27784       30394    20972857+   5  Extended
    /dev/sdae5           27784       30394    20972826   83  Linux
    Disk /dev/sdaf: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdaf1   *           1          13      104391   83  Linux
    /dev/sdaf2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdaf3            2103       27783   206282632+  83  Linux
    /dev/sdaf4           27784       30394    20972857+   5  Extended
    /dev/sdaf5           27784       30394    20972826   83  Linux
    Disk /dev/sdag: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdag1   *           1          13      104391   83  Linux
    /dev/sdag2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdag3            2103       27783   206282632+  83  Linux
    /dev/sdag4           27784       30394    20972857+   5  Extended
    /dev/sdag5           27784       30394    20972826   83  Linux
    Disk /dev/dm-13: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-13p1   *           1          13      104391   83  Linux
    /dev/dm-13p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-13p3            2103       27783   206282632+  83  Linux
    /dev/dm-13p4           27784       30394    20972857+   5  Extended
    /dev/dm-13p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-25: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-25p1   *           1          13      104391   83  Linux
    /dev/dm-25p2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/dm-25p3            1319       27783   212580112+  83  Linux
    /dev/dm-25p4           27784       30394    20972857+   5  Extended
    /dev/dm-25p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-26: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-26p1   *           1          13      104391   83  Linux
    /dev/dm-26p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-26p3            2103       27783   206282632+  83  Linux
    /dev/dm-26p4           27784       30394    20972857+   5  Extended
    /dev/dm-26p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-27: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-27p1   *           1          13      104391   83  Linux
    /dev/dm-27p2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/dm-27p3            1319       27783   212580112+  83  Linux
    /dev/dm-27p4           27784       30394    20972857+   5  Extended
    /dev/dm-27p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-28: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-28p1   *           1          13      104391   83  Linux
    /dev/dm-28p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-28p3            2103       27783   206282632+  83  Linux
    /dev/dm-28p4           27784       30394    20972857+   5  Extended
    /dev/dm-28p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-29: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-29p1   *           1          13      104391   83  Linux
    /dev/dm-29p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-29p3            2103       27783   206282632+  83  Linux
    /dev/dm-29p4           27784       30394    20972857+   5  Extended
    /dev/dm-29p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-30: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-30p1   *           1          13      104391   83  Linux
    /dev/dm-30p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-30p3            2103       27783   206282632+  83  Linux
    /dev/dm-30p4           27784       30394    20972857+   5  Extended
    /dev/dm-30p5           27784       30394    20972826   83  Linux
    How to translate the /dev/mapper address into the correct fdisk, I think I can then mount it.
    If I try the same command as before with the -t option it gives me this error.
    # mount -t ext3 /dev/mapper/3600c0ff00012f48791975b5401000000p3 /mnt
    mount: special device /dev/mapper/3600c0ff00012f48791975b5401000000p3 does not exist
    I know I am close here, and feel it should be possible, I am just missing something.
    Thanks for any help

Maybe you are looking for