Unable to mount an LVM Hard-drive after upgrade

Posted by Bruce Staples on Ask Ubuntu See other posts from Ask Ubuntu or by Bruce Staples
Published on 2012-07-08T09:38:51Z Indexed on 2012/07/09 9:23 UTC
Read the original article Hit count: 285

Filed under:
|
|

I imagine this is a basic gotcha ... but I can't see it. I have a system with 2(physical) harddrives.

The boot system (/dev/sda) was running 10.04 & the second drive (/dev/sdb) was just a mounted filesystem.

I did a clean load of Ubuntu 12.04 overwriting /dev/sda (not an upgrade) & now cannot mount the second drive. so I do not know what to enter it into the fstab ... I had expected to use:

/dev/sdb /tera ext4 defaults 0 2

But even manual mounting fails (I also have tried various "-t" options on the off chance!)

sudo mount -t ext4 /dev/sdb1 /tera

mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so

Output from disk queries indicate that it is a Linux LVM & a healthy disk still.

sudo lshw -C disk

   *-disk:0
   description: ATA Disk
   product: WDC WD5000AACS-0
   vendor: Western Digital
   physical id: 0
   bus info: scsi@2:0.0.0
   logical name: /dev/sda
   version: 01.0
   serial: WD-WCASU1401098
   size: 465GiB (500GB)
   capabilities: partitioned partitioned:dos
   configuration: ansiversion=5 signature=00015a55
   *-disk:1
   description: ATA Disk
   product: WDC WD10EADS-00L
   vendor: Western Digital
   physical id: 1
   bus info: scsi@3:0.0.0
   logical name: /dev/sdb
   version: 01.0
   serial: WD-WCAU47836304
   size: 931GiB (1TB)
   capabilities: partitioned partitioned:dos
   configuration: ansiversion=5

sudo fdisk -l

Disk /dev/sda: 500.1 GB, 500106780160 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976771055 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00015a55

Device Boot Start End Blocks Id System /dev/sda1 * 2048 972580863 486289408 83 Linux /dev/sda2 972582910 976769023 2093057 5 Extended /dev/sda5 972582912 976769023 2093056 82 Linux swap / Solaris

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000

Device Boot Start End Blocks Id System

/dev/sdb1 1 1953525167 976762583+ 8e Linux LVM

LVM doesn't appear to be an option for mount or fstab.

... and here's a Smart data Screenshot from Disk Utility.

© Ask Ubuntu or respective owner

Related posts about mount

  • 12.10 update breaks NFS mount

    as seen on Ask Ubuntu - Search for 'Ask Ubuntu'
    I've just upgraded to the latest 12.10 beta. Rebooted twice. The problem is with the NFS folders not mounting, here's a verbose log. # mount -v myserver:/nfs_shared/tools /tools/ mount: no type was given - I'll assume nfs because of the colon mount.nfs: timeout set for Mon Oct 1 11:42:28 2012 mount… >>> More

  • Mount SMB / AFP 13.10

    as seen on Ask Ubuntu - Search for 'Ask Ubuntu'
    I cannot seem to get Ubuntu to mount a mac share via SMB or AFP. I've tried the following... AFP: apt-get install afpfs-ng-utils mount_afp afp://user:password@localip/share /mnt/share Error given: "Could not connect, never got a reponse to getstatus, Connection timed out". Which is odd as I can… >>> More

  • Mount Return Code for CIFS mount

    as seen on Server Fault - Search for 'Server Fault'
    When I run the following command (as root or via sudo) from a bash script I get an exit status (or return code in mount man page parlance) of 1: mount -v -t cifs //nasbox/volume /tmpdir/ --verbose -o credentials=/root/cifsid & /tmp/mylog It outputs the following into the myflog file: parsing… >>> More

  • Disable raid member check upon mount to mount damaged nvidia raid1 member

    as seen on Server Fault - Search for 'Server Fault'
    Hi, A friend of mine destroyed his Nvidia RAID1 array somehow and in trying to fix it, he ended up with a non-working array. Because of the RAID metadata, the actual disk data was stored at an offset from the beginning. I was able to identify this offset with dd and a hexeditor and then I used losetup… >>> More

  • Network shares do not mount.

    as seen on Super User - Search for 'Super User'
    My network shares were mounting fine yesterday.. suddenly they are not. They were mounting fine for the last two weeks or however long since I added them. When I run sudo mount -a I get the following error: topsy@monolyth:~$ sudo mount -a mount error(12): Cannot allocate memory Refer to the mount… >>> More

Related posts about fstab