linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Adam Olsen <arolsen@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!
Date: Tue, 21 Jul 2009 13:55:50 -0600	[thread overview]
Message-ID: <2473b43f0907211255u7c116b1er9c3483bec2472cd@mail.gmail.com> (raw)

This pretty much sums it up:

imgserv:/storage/# lvscan
  ACTIVE            '/dev/storage/storage' [3.62 TB] inherit
imgserv:/storage/# fdisk /dev/storage/storage

Unable to read /dev/storage/storage

I can't mount it, access it with fdisk.  Here's the lvdisplay output:

imgserv:/storage/# lvdisplay
  --- Logical volume ---
  LV Name                /dev/storage/storage
  VG Name                storage
  LV UUID                Cw8aAr-YHsR-oVfH-7AAx-2ppa-Zm3M-U9z1eA
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                3.62 TB
  Current LE             948962
  Segments               3
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0

This is on debian etch.   This is what I see at the end of dmesg:

cdrom: open failed.
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54

Which I don't think has anything to do with this problem, as hdc is
NOT one of the physical volumes... it's a cdrom drive.

Is there anything I can do to debug this?

-- 
Adam Olsen
SendOutCards.com
http://www.vimtips.org
http://last.fm/user/synic

             reply	other threads:[~2009-07-21 19:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 19:55 Adam Olsen [this message]
2009-07-21 19:58 ` [linux-lvm] Can't mount or run fdisk on an existing logical volume, help! Ray Van Dolson
2009-07-21 20:01   ` Adam Olsen
2009-07-21 20:07     ` Ray Van Dolson
2009-07-21 20:29       ` Adam Olsen
2009-07-21 20:35         ` Ray Van Dolson
2009-07-21 20:46           ` Sven Eschenberg
2009-07-21 20:47           ` Adam Olsen
2009-07-21 21:07             ` Ray Van Dolson
2009-07-21 21:24               ` Adam Olsen
2009-07-21 21:59                 ` Ray Van Dolson
2009-07-21 22:09                   ` Adam Olsen
2009-07-21 22:21                     ` Ray Van Dolson
2009-07-21 22:43                       ` Adam Olsen
2009-07-21 22:50                         ` Ray Van Dolson
2009-07-22 13:08                     ` Bryn M. Reeves
2009-07-24  1:38                     ` Ron Johnson
2009-07-22 13:17     ` Bryn M. Reeves
2009-07-22  5:26   ` Ron Johnson
2009-07-22  5:41     ` Adam Olsen
2009-07-22  5:49       ` Ron Johnson
2009-07-22  6:01         ` Adam Olsen
2009-07-22 15:42           ` Sven Eschenberg
2009-07-22 16:49             ` Bryn M. Reeves
2009-07-23 23:42               ` Adam Olsen
2009-07-22 13:06       ` Bryn M. Reeves
2009-07-22 13:05     ` Bryn M. Reeves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2473b43f0907211255u7c116b1er9c3483bec2472cd@mail.gmail.com \
    --to=arolsen@gmail.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).