LinuxQuestions.org - mount partition type 'fd' fails with " unknown filesystem type 'linux_raid

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - mount partition type 'fd' fails with " unknown filesystem type 'linux_raid_member'" (https://www.linuxquestions.org/questions/linux-software-2/mount-partition-type-fd-fails-with-unknown-filesystem-type-linux_raid_member-4175445710/)

mount partition type 'fd' fails with " unknown filesystem type 'linux_raid_member'"

Hi,

I had an old NAS - single drive so no RAID that I configured.

Built the disk into a system I installed ubunto onto in the hopes of getting my data back. The disk is giving a SMART error, so it cannot/will not boot anymore - but seems to be okay as 'just a disk'.

(I am aware of the posts http://www.linuxquestions.org/questi...-drive-925485/ and http://www.linuxquestions.org/questi...1-disk-723225/ However, I have not understood them well enough to move forward - additional software (raid management) and different partition type (83 I believe).

Thanks for your assistence!

After powering up:

# fdisk -> p output:

Code:

Disk /dev/sdb: 750.2 GB, 750156374016 bytes

255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 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: 0x00007c00



  Device Boot      Start        End      Blocks  Id  System

/dev/sdb1          48195    5927984    2939895  fd  Linux raid autodetect

/dev/sdb2        5927985    6136829      104422+  fd  Linux raid autodetect

/dev/sdb3        6136830    8112824      987997+  fd  Linux raid autodetect

/dev/sdb4        8112825  1465144064  728515620  fd  Linux raid autodetect

mount fails...

Code:

root@ubuntu:~# mount -r /dev/sdb4 /data/x002

mount: unknown filesystem type 'linux_raid_member'

fdisk -> l command (for reference)

Code:

Command (m for help): l            



 0  Empty          24  NEC DOS        81  Minix / old Lin bf  Solaris        

 1  FAT12          27  Hidden NTFS Win 82  Linux swap / So c1  DRDOS/sec (FAT-

 2  XENIX root      39  Plan 9          83  Linux          c4  DRDOS/sec (FAT-

 3  XENIX usr      3c  PartitionMagic  84  OS/2 hidden C:  c6  DRDOS/sec (FAT-

 4  FAT16 <32M      40  Venix 80286    85  Linux extended  c7  Syrinx        

 5  Extended        41  PPC PReP Boot  86  NTFS volume set da  Non-FS data    

 6  FAT16          42  SFS            87  NTFS volume set db  CP/M / CTOS / .

 7  HPFS/NTFS/exFAT 4d  QNX4.x          88  Linux plaintext de  Dell Utility  

 8  AIX            4e  QNX4.x 2nd part 8e  Linux LVM      df  BootIt        

 9  AIX bootable    4f  QNX4.x 3rd part 93  Amoeba          e1  DOS access    

 a  OS/2 Boot Manag 50  OnTrack DM      94  Amoeba BBT      e3  DOS R/O        

 b  W95 FAT32      51  OnTrack DM6 Aux 9f  BSD/OS          e4  SpeedStor      

 c  W95 FAT32 (LBA) 52  CP/M            a0  IBM Thinkpad hi eb  BeOS fs        

 e  W95 FAT16 (LBA) 53  OnTrack DM6 Aux a5  FreeBSD        ee  GPT            

 f  W95 Ext'd (LBA) 54  OnTrackDM6      a6  OpenBSD        ef  EFI (FAT-12/16/

10  OPUS            55  EZ-Drive        a7  NeXTSTEP        f0  Linux/PA-RISC b

11  Hidden FAT12    56  Golden Bow      a8  Darwin UFS      f1  SpeedStor      

12  Compaq diagnost 5c  Priam Edisk    a9  NetBSD          f4  SpeedStor      

14  Hidden FAT16 <3 61  SpeedStor      ab  Darwin boot    f2  DOS secondary  

16  Hidden FAT16    63  GNU HURD or Sys af  HFS / HFS+      fb  VMware VMFS    

17  Hidden HPFS/NTF 64  Novell Netware  b7  BSDI fs        fc  VMware VMKCORE 

18  AST SmartSleep  65  Novell Netware  b8  BSDI swap      fd  Linux raid auto

1b  Hidden W95 FAT3 70  DiskSecure Mult bb  Boot Wizard hid fe  LANstep        

1c  Hidden W95 FAT3 75  PC/IX          be  Solaris boot    ff  BBT            

1e  Hidden W95 FAT1 80  Old Minix

Without copying/pasting check out the thread on hardforums. This is caused by a software layer raid that was implemented on the drive. Probably automatically by your NAS. You will need to mount it with mdadm and try to rebuild it to access your data.

http://hardforum.com/showthread.php?t=1453689

Hopefully this is a linear - those partitions being different sizes. But don't go messing with anything (particularly partition type) till you know what you're dealing with.
The second thread you posted probably has all the doco you need. Let's see the output of

Code:

cat /proc/mdadm

Yes the /proc/mdadm file is going to be a great place to look. Depending upon the output and what info is actually missing an mdadm with a scan argument may fill in the missing info and get you there.

You could also try explicitly specifying the file system type on the mount command and see if that works, its kind of hit or miss in this situation. Try adding a "-t ext3" to your mount command and see if it takes.

Guess I have some prep work to do...

Code:

michael@ubuntu:~$ cat /proc/mdadm

cat: /proc/mdadm: No such file or directory

OK. I installed mdadm, still no /proc/mdadm

Mounting with -t ext3 took longer for a reply, but still no success.

Code:

root@ubuntu:~# mount -r -t ext3 /dev/sdb4 /data/x052

mount: wrong fs type, bad option, bad superblock on /dev/sdb4,

      missing codepage or helper program, or other error

      In some cases useful info is found in syslog - try

      dmesg | tail  or so

Not accustomed on AIX to rebooting after installing, I suspect this is not a solution for Linux either, but will try a reboot before proceeding.

Before I try a mdadm command going to read the help and hop to understand that (a bit of explanation is missing in your 3-year post, but :smiley" when I saw type 'fd'!

A "Thank you" will be coming soon - perhaps two!

no reboot - yet. No help on -R option (rebuild?), so unsure about using it. Do not want to destroy data.

Code:

root@ubuntu:~# mdadm --help-options | grep R

root@ubuntu:~# mdadm --help-options | grep build

  --build      -B  : Build an array without metadata

After a reboot - had to reattach a keyboard and monitor to see I needed to press F1.

reboot was needed because system no longer saw disk (after the -t ext3 mount command I expect)

System (on console) said something about degraded state - I said yes, and mdadm starting doing "stuff" :)

Code:

root@ubuntu:~# mdadm -Q /dev/sdb4

/dev/sdb4: is not an md array

/dev/sdb4: device 0 in 2 device active raid1 /dev/md4.  Use mdadm --examine for more detail.

I am guessing that the mdX devices are virtualizations of the sdbX devices.

Code:

root@ubuntu:~# ls -l /dev/md?

brw-rw---- 1 root disk 9, 1 Jan 16 14:13 /dev/md1

brw-rw---- 1 root disk 9, 2 Jan 16 14:13 /dev/md2

brw-rw---- 1 root disk 9, 3 Jan 16 14:13 /dev/md3

brw-rw---- 1 root disk 9, 4 Jan 16 14:13 /dev/md4

root@ubuntu:~# ls -l /dev/sdb?

brw-rw---- 1 root disk 8, 17 Jan 16 14:13 /dev/sdb1

brw-rw---- 1 root disk 8, 18 Jan 16 14:13 /dev/sdb2

brw-rw---- 1 root disk 8, 19 Jan 16 14:13 /dev/sdb3

brw-rw---- 1 root disk 8, 20 Jan 16 14:13 /dev/sdb4

Still no /proc/mdadm info

Code:

root@ubuntu:~# cat /proc/mdadm

cat: /proc/mdadm: No such file or directory

So, back to mdadm's suggestion to examine...

Code:

root@ubuntu:~# mdadm --help-options | grep examine

or, for --examine-bitmap, a file name.

  --examine    -E  : Examine superblock on an array component

  --examine-bitmap -X: Display the detail of a bitmap file

Hmm, was the NAT being tricky entering the device twice? Or does this mean something else.
Will wait for assistance now ... (note: I will probably not be able to look at this tomorrow, so my responses will be delayed).

Code:

root@ubuntu:~# mdadm -E /dev/md4

mdadm: No md superblock detected on /dev/md4.

root@ubuntu:~# mdadm -E /dev/sdb4

/dev/sdb4:

          Magic : a92b4efc

        Version : 0.90.00

          UUID : a6ebb52b:a91421c4:a20483f2:e535f949

  Creation Time : Thu Jan 24 10:51:54 2002

    Raid Level : raid1

  Used Dev Size : 728515520 (694.77 GiB 746.00 GB)

    Array Size : 728515520 (694.77 GiB 746.00 GB)

  Raid Devices : 2

  Total Devices : 1

Preferred Minor : 4



    Update Time : Wed Jan 16 15:13:10 2013

          State : clean

 Active Devices : 1

Working Devices : 1

 Failed Devices : 1

  Spare Devices : 0

      Checksum : 39576ddd - correct

        Events : 2063303





      Number  Major  Minor  RaidDevice State

this    0      8      20        0      active sync  /dev/sdb4



  0    0      8      20        0      active sync  /dev/sdb4

  1    1      0        0        1      faulty removed

root@ubuntu:~#

Still where I started...

Code:

root@ubuntu:~# mount -r /dev/sdb4 /data/x052

mount: unknown filesystem type 'linux_raid_member'

-R is "force run" it basically says to mdadm, mount this even if you don't want to.

Here is a good man page for it.
http://linux.die.net/man/8/mdadm

The error indicates that the superblock has this drive set to be one of the members of a two drive RAID1 software raid setup. This was more than likely implemented by the NAS automatically without your knowledge. Good news, its a RAID1 and you should be able to get your data back without much trouble.

So you should be able to do the mdadm assemble with the run option to get it mounted. It will just be in a "degraded" state forever unless you get a second drive rebuilt into the array.

This is the second time I run these steps, first time was on a console so I could not cut/paste the output.

stderr had many errors, so I suspect the disk is, for all effective purposes - dead.

What I could see this time:

Code:

root@ubuntu:~# fdisk -l /dev/sdb



Disk /dev/sdb: 750.2 GB, 750156374016 bytes

255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 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: 0x00007c00



  Device Boot      Start        End      Blocks  Id  System

/dev/sdb1          48195    5927984    2939895  fd  Linux raid autodetect

/dev/sdb2        5927985    6136829      104422+  fd  Linux raid autodetect

/dev/sdb3        6136830    8112824      987997+  fd  Linux raid autodetect

/dev/sdb4        8112825  1465144064  728515620  fd  Linux raid autodetect

root@ubuntu:~# mdadm -A -R /dev/md4 /dev/sdb4

mdadm: /dev/sdb4 is busy - skipping

root@ubuntu:~# mount /dev/sdb4 /data/x053

mount: unknown filesystem type 'linux_raid_member'

root@ubuntu:~# mount /dev/md4 /data/x053

mount: wrong fs type, bad option, bad superblock on /dev/md4,

      missing codepage or helper program, or other error

      In some cases useful info is found in syslog - try

      dmesg | tail  or so



root@ubuntu:~# fdisk -l /dev/sdb

Note: this was a single disk NAS (WD "blue ring" something book), so yes, it made it RAID without me ever knowing ;)

=== update ===
found messages - presented courtesy of dmesg
just the end, there are many many more.

Quote:

[ 181.156518] end_request: I/O error, dev sdb, sector 1276627665
[ 181.156859] sd 3:0:0:0: [sdb] Unhandled error code
[ 181.156862] sd 3:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 181.156865] sd 3:0:0:0: [sdb] CDB: Write(10): 2a 00 50 c3 ca b9 00 00 18 00
[ 181.156874] end_request: I/O error, dev sdb, sector 1355008697
[ 181.157216] sd 3:0:0:0: [sdb] Unhandled error code
[ 181.157219] sd 3:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 181.157222] sd 3:0:0:0: [sdb] CDB: Write(10): 2a 00 51 8b ca b9 00 00 18 00
[ 181.157231] end_request: I/O error, dev sdb, sector 1368115897
[ 181.157576] sd 3:0:0:0: [sdb] Unhandled error code
[ 181.157579] sd 3:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 181.157582] sd 3:0:0:0: [sdb] CDB: Write(10): 2a 00 57 4f ca c9 00 00 08 00
[ 181.157591] end_request: I/O error, dev sdb, sector 1464847049
[ 181.161432] sd 3:0:0:0: [sdb] Truncating mode parameter data from 11824 to 512 bytes
[ 181.161538] sd 3:0:0:0: [sdb] Got wrong page
[ 181.161675] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 181.161803] sdb: detected capacity change from 750156374016 to 0
[ 181.161941] JBD: recovery failed
[ 181.161945] EXT3-fs (md4): error loading journal
[ 181.364067] md: super_written gets error=-5, uptodate=0

This indeed looks like a hardware error, I would recommend to test the disk with the manufacturer's diagnosis tool.

No time for 24 hours, will let you know what the results are - IF i can find the right program.

Would you happen to have a link to a linux program for Western Digital disks - SATA?

Western Digital seems to be Windows only nowadays, but you can use SeaTools for this job. Here a link to a bootable ISO: http://origin-www.seagate.com/suppor...ls-dos-master/

Hi Michael, have you finally solved the issue? I'm in a similar situation and have difficulties to mount the disks onto another computer.

No. I tried several times, but it seems the disk is too far damaged for any recovery using simple hardware.

Good luck!

I do want to add that the suggestions provided (which I have now forgotten) seemed very promising and worth the effort. But sometimes a disk is just "gone".

Now I have a real RAID6 NAS, and have a spare in the closet.