[SOLVED] mount: /mnt/disk: wrong fs type, bad option, bad superblock on /dev/mapper/vg-lv

Romalian · 06-15-2018, 10:43 AM

Hello,

I have a NAS Lacie Cloudbox that have Ethernet port out of service. The disk is working but i need to recover data.

For this, i followed this tutorial :

https://www.slideshare.net/JordiClop...-data-recovery

All is working fine except 2 things :

Before step 8, i had to do the following command : sudo mkdir /mnt/disk/

After, all is okay but after step 13, i have this error :

mount: /mnt/disk: wrong fs type, bad option, bad superblock on /dev/mapper/vg-lv, missing codepage or helper program, or other error.

I am newbie with Ubuntu and Linux world...

Can someone help me please ?

Thank you.

jsbjsb001 · 06-15-2018, 10:52 AM

It looks like you're trying to mount the drive, but you have either specified the wrong device node/drive, the filesystem is corrupted/unreadable or something similar has happened.

Can you post the results of the following command:

Code:

lsblk -f

Please use CODE tags when you do - see my signature below if you're unsure how to do this.

Romalian · 06-15-2018, 11:12 AM

Hi jsbjsb001,

Sorry for delayed answer, i had to do all again as i reboot computer...

Here is the result of the command requested :

Code:

ubuntu@ubuntu:~$ sudo lsblk -f
NAME        FSTYPE            LABEL            UUID                                   MOUNTPOINT
loop0       squashfs                                                                  /rofs
loop1       squashfs                                                                  /snap/core/4486
loop2       squashfs                                                                  /snap/gnome-3-26-1604/59
loop3       squashfs                                                                  /snap/gnome-calculator/154
loop4       squashfs                                                                  /snap/gnome-characters/69
loop5       squashfs                                                                  /snap/gnome-logs/25
loop6       squashfs                                                                  /snap/gnome-system-monitor/36
sda                                                                                   
├─sda1                                                                                
├─sda2      ext2                               780f73da-df49-448f-b46d-9e5fca6c50d4   /media/ubuntu/780f73da-df49-448f-b46d-9e5fca6c50d4
├─sda3      ext2                               da0662e3-e55c-4d5e-bc1a-7fbf330ce76c   /media/ubuntu/da0662e3-e55c-4d5e-bc1a-7fbf330ce76c
├─sda4      linux_raid_member (none):4         b9e34d36-b76e-dc5e-4341-2066ef092d8f   
├─sda5      linux_raid_member (none):5         8bd2c9e1-8a10-5904-7285-9d67ace1eefa   
├─sda6      linux_raid_member (none):6         22b74044-7e4b-26bc-f6a2-a4b754da349c   
├─sda7      linux_raid_member (none):7         ecef4cf6-e802-3def-9db5-1ee0e9cd845c   [SWAP]
└─sda8      linux_raid_member LaCie-CloudBox:8 8aff748d-8c24-687f-cfd5-2ab95f34e104   
  └─md0     LVM2_member                        14E1fB-Vmfu-5WlY-th0K-7dWH-pweR-nndQw8 
    └─vg-lv                                                                           
sdb                                                                                   
├─sdb1                                                                                
└─sdb2      ntfs              test             1E30D00E30CFEABB                       /media/ubuntu/test
sdc                                                                                   
└─sdc1      vfat              UBUNTU           3C92-F6E9                              /cdrom
nvme0n1                                                                               
├─nvme0n1p1 vfat              SYSTEM_DRV       E602-D110                              
├─nvme0n1p2                                                                           
├─nvme0n1p3 ntfs              Windows          10A20675A2066018                       
├─nvme0n1p4 ntfs              LENOVO           306E3B8A6E3B483C                       
└─nvme0n1p5 ntfs              WINRE_DRV        7A8A07338A06EB87                       
ubuntu@ubuntu:~$

Thank you in advance

jsbjsb001 · 06-15-2018, 11:18 AM

From your output it looks like it's on a RAID setup.

Try the following command:

Code:

sudo mount /dev/sda8 /mnt/disk/

I'm not sure that calling the mount folder "disk" is a really good idea, while I'm not saying it won't work; next time you maybe should give it a more unique name instead.

Let us know how it works out for you.

Romalian · 06-15-2018, 11:24 AM

I did the requested command and had this result :

Code:

ubuntu@ubuntu:~$ sudo mount /dev/sda8 /mnt/disk
mount: /mnt/disk: unknown filesystem type 'linux_raid_member'.
ubuntu@ubuntu:~$

jsbjsb001 · 06-15-2018, 11:29 AM

This is what I was afraid of, because it's on a RAID setup, the mount command doesn't like it. It looks like you have to "assemble" the RAID first which means you then should be able to mount it with the mount command.

I'm not up-to-date when it comes to RAID setups, but I have found the following link for you to review:

https://serverfault.com/questions/38...ux-raid-member

Romalian · 06-15-2018, 11:33 AM

Thank you jsbjsb001 but did you check the tutorial i used ?

Have the assemble step on the image number 10. Can you check where can be the problem in the procedure of the tutorial please ?

jsbjsb001 · 06-15-2018, 11:37 AM

Quote:

Originally Posted by Romalian

Thank you jsbjsb001 but did you check the tutorial i used ?

Have the assemble step on the image number 10. Can you check where can be the problem in the procedure of the tutorial please ?

I did have a look at it, but I didn't get that far.

As long as you have the mdadm and the lvm2 packages installed, it looks like it's the same procedure as in the link I gave you in my previous post.

Have you got those two packages installed? If not, install them first and then follow Step 10 (slide 10) in the link you supplied in your first post.

Romalian · 06-15-2018, 11:41 AM

Give me 10 minutes. I will reboot and do again, then, i will post all with code.

jsbjsb001 · 06-15-2018, 11:46 AM

Quote:

Originally Posted by Romalian

Give me 10 minutes. I will reboot and do again, then, i will post all with code.

No worries, just remember, after you've "assembled" your RAID, it looks like it will be the following command to mount it:

Code:

sudo mount /dev/md0 /mnt/disk/

Romalian · 06-15-2018, 11:53 AM

Here is the full result, with a change as the disk is not sda but sdb this time.

I tried also to mount as you explain on your last post at the end.

Code:

ubuntu@ubuntu:~$ sudo parted -l
Model: SanDisk Ultra USB 3.0 (scsi)
Disk /dev/sda: 15.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  15.4GB  15.4GB  primary  fat32        boot, lba


Model: Prolific ATAPI-6 Bridge C (scsi)
Disk /dev/sdb: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name         Flags
 1      1049kB  2097kB  1049kB                  grub_core    bios_grub
 2      2097kB  203MB   201MB   ext2            boot_rescue
 3      203MB   204MB   1049kB  ext2            nv_data
 4      204MB   1815MB  1611MB  ext2            root_1       raid
 5      1815MB  3426MB  1611MB  ext2            root_2       raid
 6      3426MB  4499MB  1074MB  ext3            var          raid
 7      4499MB  4768MB  268MB   linux-swap(v1)  swap         raid
 8      4768MB  3001GB  2996GB                  user_data    raid


Model: Prolific ATAPI-6 Bridge C (scsi)
Disk /dev/sdc: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      17.4kB  134MB   134MB                Microsoft reserved partition  msftres
 2      135MB   3001GB  3000GB  ntfs         Basic data partition          msftdata


Model: NVMe Device (nvme)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  274MB  273MB   fat32        EFI system partition          boot, esp
 2      274MB   290MB  16.8MB               Microsoft reserved partition  msftres
 3      290MB   228GB  228GB   ntfs         Basic data partition          msftdata
 4      228GB   255GB  26.8GB  ntfs         Basic data partition          msftdata
 5      255GB   256GB  1049MB  ntfs         Basic data partition          hidden, diag


ubuntu@ubuntu:~$ sudo mkdir /mnt/disk/
ubuntu@ubuntu:~$ sudo mount /dev/sdb8 /mnt/disk/
mount: /mnt/disk: unknown filesystem type 'linux_raid_member'.
ubuntu@ubuntu:~$ sudo apt-get install mdadm
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Suggested packages:
  default-mta | mail-transport-agent dracut-core
The following NEW packages will be installed:
  mdadm
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 408 kB of archives.
After this operation, 1199 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 mdadm amd64 4.0-2ubuntu1 [408 kB]
Fetched 408 kB in 2s (208 kB/s)
Preconfiguring packages ...
Selecting previously unselected package mdadm.
(Reading database ... 143897 files and directories currently installed.)
Preparing to unpack .../mdadm_4.0-2ubuntu1_amd64.deb ...
Unpacking mdadm (4.0-2ubuntu1) ...
Processing triggers for ureadahead (0.100.0-20) ...
Setting up mdadm (4.0-2ubuntu1) ...
Generating mdadm.conf... done.
update-initramfs is disabled since running on read-only media
/usr/sbin/grub-probe: error: failed to get canonical path of `/cow'.
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for ureadahead (0.100.0-20) ...
ubuntu@ubuntu:~$ sudo apt-get install lvm2
Reading package lists... Done
Building dependency tree       
Reading state information... Done
lvm2 is already the newest version (2.02.176-4.1ubuntu3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
ubuntu@ubuntu:~$ sudo mdadm --assemble --run /dev/md0 /dev/sdb8
mdadm: /dev/md0 has been started with 1 drive.
ubuntu@ubuntu:~$ sudo lvmdiskscan
  /dev/nvme0n1   [     238.47 GiB] 
  /dev/loop0     [      <1.71 GiB] 
  /dev/md0       [       2.72 TiB] LVM physical volume
  /dev/dm-0      [       2.72 TiB] 
  /dev/nvme0n1p1 [     260.00 MiB] 
  /dev/loop1     [      86.55 MiB] 
  /dev/sda1      [     <14.32 GiB] 
  /dev/nvme0n1p2 [      16.00 MiB] 
  /dev/loop2     [    <140.04 MiB] 
  /dev/nvme0n1p3 [    <212.23 GiB] 
  /dev/nvme0n1p4 [      25.00 GiB] 
  /dev/loop4     [      12.21 MiB] 
  /dev/nvme0n1p5 [    1000.00 MiB] 
  /dev/loop5     [      20.98 MiB] 
  /dev/loop6     [       3.25 MiB] 
  /dev/sdb2      [     192.00 MiB] 
  /dev/sdc1      [     128.00 MiB] 
  /dev/sdc2      [      <2.73 TiB] 
  0 disks
  17 partitions
  0 LVM physical volume whole disks
  1 LVM physical volume
ubuntu@ubuntu:~$ sudo lvdisplay
  --- Logical volume ---
  LV Path                /dev/vg/lv
  LV Name                lv
  VG Name                vg
  LV UUID                NSZAM9-joOB-Hk6I-mb0U-8BKQ-dCBj-GKusYa
  LV Write Access        read/write
  LV Creation host, time , 
  LV Status              available
  # open                 0
  LV Size                2.72 TiB
  Current LE             714260
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0
   
ubuntu@ubuntu:~$ sudo mkdir /mnt/cloudbox
ubuntu@ubuntu:~$ sudo mount /dev/vg/lv /mnt/cloudbox/
mount: /mnt/cloudbox: wrong fs type, bad option, bad superblock on /dev/mapper/vg-lv, missing codepage or helper program, or other error.
ubuntu@ubuntu:~$ sudo mount /dev/sdb8 /mnt/cloudbox/
mount: /mnt/cloudbox: unknown filesystem type 'linux_raid_member'.
ubuntu@ubuntu:~$

jsbjsb001 · 06-15-2018, 11:56 AM

Yeah, sorry about that, I just corrected my reply in post #10 (my last reply before this one), can you try that instead. Sorry about that.

Romalian · 06-15-2018, 11:58 AM

Yes, just tried and i have this :

Code:

ubuntu@ubuntu:~$ sudo mount /dev/md0 /mnt/cloudbox/
mount: /mnt/cloudbox: unknown filesystem type 'LVM2_member'.

jsbjsb001 · 06-15-2018, 12:04 PM

I was hoping we had finally nailed it, but anyhow, try this:

Code:

sudo mount /dev/vg/lv /mnt/cloudbox/

Because of your latest output, I assume you have changed "/mnt/disk" to "/mnt/cloudbox/" for the mount folder. If not, use "/mnt/disk" instead.

If the above fails, you could also try something like:

Code:

sudo mount /dev/md1 /mnt/cloudbox/

Although, it does say it's on "/dev/md0" in your latest output.

If all of the above fails, try the command in my post #4 again. - with "/mnt/cloudbox/" instead of "/mnt/disk/".

Romalian · 06-15-2018, 12:09 PM

I have these results...

Code:

ubuntu@ubuntu:~$ sudo mount /dev/vg/lv /mnt/cloudbox/
mount: /mnt/cloudbox: wrong fs type, bad option, bad superblock on /dev/mapper/vg-lv, missing codepage or helper program, or other error.
ubuntu@ubuntu:~$ sudo mount /dev/md1 /mnt/cloudbox/
mount: /mnt/cloudbox: special device /dev/md1 does not exist.
ubuntu@ubuntu:~$ sudo mount /dev/vg/lv /mnt/disk/
mount: /mnt/disk: wrong fs type, bad option, bad superblock on /dev/mapper/vg-lv, missing codepage or helper program, or other error.
ubuntu@ubuntu:~$