Boonstra
Data Recovery Noob
Posts: 6
Joined: Mon Sep 25, 2017 5:49 pm

Crashed mdadm raid 5

Mon Sep 25, 2017 5:59 pm

Who can help me determine the right steps to recapture files from my MDADM raid 5?

My self-build after that was time for hardware replacement and have ordered and assembled a new U-NAS case, motherboard, xeon and ecc memory.

After some setbacks it was possible to install OMV on a M2 with NVMe.
So it's time to move my disks from my old after that to the new setup.

Unfortunately, the raid did not come online by itself, which was the case with an earlier move. After retrieving some info from the disks I found out that of the 5x 3tb raid5 setup on the 3 older disks my superblocks had disappeared: - (.

Tried to force the raid to restart again without result. And to make things worse, I accidentally ordered in a wisdom amazement after many attempts to set up a new journal there.

After that, I stopped and removed the disks and sent them to a professional recovery company to send. In a team view session I have seen that files can be retrieved (I have checked this by opening many photos, among other things).

For research, I had to pay an x amount after which they would make a quotation what the recovery costs would be (which they had actually already done). This was without obligation.

The amount was so high that I saw it off at that time and wanted to have my disks back with the idea that this is always possible.

Meanwhile, I have cloned the disks and with these disks I want to try to recover the files myself.


I have a parted magic distribution where I want to use photorec / testdisk to search, and
but how to proceed now.
I don't know the order of the disks in the raid except for 2 disks.

Will it be a matter of forcing several raid sequences and then scanning?


Code: Select all

[size=50]
login as: root
[email protected]'s password:
Linux DARK-VAULT 3.2.0-4-amd64 #1 SMP Debian 3.2.89-2 x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Jul  5 21:33:30 2017
[email protected]:~# mdadm -Q /dev/md0
/dev/md0: 0.00KiB raid5 5 devices, 0 spares. Use mdadm --detail for more detail.
[email protected]:~# mdadm --eximine /dev/sdb
mdadm: unrecognized option '--eximine'
Usage: mdadm --help
  for help
[email protected]:~# mdadm --examine /dev/sdb
/dev/sdb:
          Magic    : a92b4efc
        Version    : 1.2
    Feature Map   : 0x0
     Array UUID   : 78601ff4:5022822d:40ae7e71:1794c4d6
           Name : openmediavault:0
  Creation Time : Sat Jan  5 23:58:39 2013
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 5860271024 (2794.40 GiB 3000.46 GB)
     Array Size : 11720540160 (11177.58 GiB 12001.83 GB)
  Used Dev Size : 5860270080 (2794.39 GiB 3000.46 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 08c8efa3:e8b07613:0a79598e:521e0a25

    Update Time : Sat Jul  1 20:40:48 2017
       Checksum : d4655f24 - correct
         Events : 57494

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 4
   Array State : AAAAA ('A' == active, '.' == missing)
[email protected]:~# mdadm --examine /dev/sdc
/dev/sdc:
   MBR Magic : aa55
Partition[0] :   4294967295 sectors at            1 (type ee)
[email protected]:~# mdadm --examine /dev/sdd
/dev/sdd:
   MBR Magic : aa55
Partition[0] :   4294967295 sectors at            1 (type ee)
[email protected]:~# mdadm --examine /dev/sde
/dev/sde:
   MBR Magic : aa55
Partition[0] :   4294967295 sectors at            1 (type ee)
[email protected]:~# mdadm --examine /dev/sde1
mdadm: No md superblock detected on /dev/sde1.
[email protected]:~# mdadm --examine /dev/sdf
/dev/sdf:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 78601ff4:5022822d:40ae7e71:1794c4d6
           Name : openmediavault:0
  Creation Time : Sat Jan  5 23:58:39 2013
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 5860271024 (2794.40 GiB 3000.46 GB)
     Array Size : 11720540160 (11177.58 GiB 12001.83 GB)
  Used Dev Size : 5860270080 (2794.39 GiB 3000.46 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : f7fdb09f:f7b15921:2152c830:c11fb3d3

    Update Time : Sat Jul  1 20:40:48 2017
       Checksum : 2f2170a6 - correct
         Events : 57494

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 0
   Array State : AAAAA ('A' == active, '.' == missing)
[email protected]:~# mdadm --examine /dev/sdf
/dev/sdf:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 78601ff4:5022822d:40ae7e71:1794c4d6
           Name : openmediavault:0
  Creation Time : Sat Jan  5 23:58:39 2013
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 5860271024 (2794.40 GiB 3000.46 GB)
     Array Size : 11720540160 (11177.58 GiB 12001.83 GB)
  Used Dev Size : 5860270080 (2794.39 GiB 3000.46 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : f7fdb09f:f7b15921:2152c830:c11fb3d3

    Update Time : Sat Jul  1 20:40:48 2017
       Checksum : 2f2170a6 - correct
         Events : 57494

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 0
   Array State : AAAAA ('A' == active, '.' == missing)
[email protected]:~# mdadm --examine /dev/sdb
/dev/sdb:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 78601ff4:5022822d:40ae7e71:1794c4d6
           Name : openmediavault:0
  Creation Time : Sat Jan  5 23:58:39 2013
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 5860271024 (2794.40 GiB 3000.46 GB)
     Array Size : 11720540160 (11177.58 GiB 12001.83 GB)
  Used Dev Size : 5860270080 (2794.39 GiB 3000.46 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 08c8efa3:e8b07613:0a79598e:521e0a25

    Update Time : Sat Jul  1 20:40:48 2017
       Checksum : d4655f24 - correct
         Events : 57494

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 4
   Array State : AAAAA ('A' == active, '.' == missing)
[email protected]:~# mdadm --examine /dev/sdc
/dev/sdc:
   MBR Magic : aa55
Partition[0] :   4294967295 sectors at            1 (type ee)
[email protected]:~# cd /etc/mdadm/
[email protected]:/etc/mdadm# ls
mdadm.conf
[email protected]:/etc/mdadm# nano mdadm.conf
[email protected]:/etc/mdadm# ls
mdadm.conf
[email protected]:/etc/mdadm# cd ll
-bash: cd: ll: Bestand of map bestaat niet
[email protected]:/etc/mdadm# ls
mdadm.conf
[email protected]:/etc/mdadm# cd .
[email protected]:/etc/mdadm# cd ..
[email protected]:/etc# ls
acpi                           debconf.conf      init.d               mdadm           postfix         sensors.d
adduser.conf                   debian_version    initramfs-tools      mime.types      ppp             services
adjtime                        default           inittab              minidlna.conf   profile         shadow
aliases                        deluser.conf      inputrc              mke2fs.conf     profile.d       shadow-
aliases.db                     dhcp              insserv              modprobe.d      proftpd         shells
alternatives                   dhcp3             insserv.conf         modules         protocols       skel
anacrontab                     dpkg              insserv.conf.d       monit           pulse           smartd.conf
apache2                        emacs             iproute2             mono            python          smartmontools
apm                            environment       issue                motd            python2.7       snmp
apparmor.d                     exports           issue.net            mpd.conf        python3         ssh
apt                            fonts             kernel               mtab            python3.2       ssl
avahi                          fstab             kernel-img.conf      mysql           quotagrpadmins  staff-group-for-usr-local
avserver.conf                  fstab.d           ldap                 nanorc          quotatab        sudoers
bash.bashrc                    ftpusers          ld.so.cache          netconfig       rc0.d           sudoers.d
bash_completion                fuse.conf         ld.so.conf           network         rc1.d           sysctl.conf
bash_completion.d              gai.conf          ld.so.conf.d         networks        rc2.d           sysctl.d
bindresvport.blacklist         groff             libao.conf           nginx           rc3.d           systemd
blkid.tab                      group             libnl-3              nsswitch.conf   rc4.d           terminfo
blkid.tab.old                  group-            locale.alias         ntp.conf        rc5.d           timezone
ca-certificates                grub.d            locale.gen           omvextras       rc6.d           transmission-daemon
ca-certificates.conf           gshadow           localtime            omv-support.d   rc.local        ts.conf
ca-certificates.conf.dpkg-old  gshadow-          logcheck             openmediavault  rcS.d           ucf.conf
calendar                       gssapi_mech.conf  login.defs           openvpn         resolvconf      udev
clamav                         gtk-2.0           logrotate.conf       opt             resolv.conf     ufw
collectd                       gtk-3.0           logrotate.d          os-release      rmt             vim
cron-apt                       hdparm.conf       lsb-base-logging.sh  pam.conf        rpc             warnquota.conf
cron.d                         host.conf         lvm                  pam.d           rsyslog.conf    watchdog.conf
cron.daily                     hostname          magic                passwd          rsyslog.d       wgetrc
cron.hourly                    hosts             magic.mime           passwd-         samba           wpa_supplicant
cron.monthly                   hosts.allow       mailcap              pcmcia          screenrc        X11
crontab                        hosts.deny        mailcap.order        pear            securetty       xdg
cron.weekly                    idmapd.conf       mailname             perl            security
dbconfig-common                ifplugd           mail.rc              php5            selinux
dbus-1                         init              manpath.config       pm              sensors3.conf
[email protected]:/etc# mdadm --examine /dev/sdc
/dev/sdc:
   MBR Magic : aa55
Partition[0] :   4294967295 sectors at            1 (type ee)
[email protected]:/etc# mdadm --examine /dev/sdc
/dev/sdc:
   MBR Magic : aa55
Partition[0] :   4294967295 sectors at            1 (type ee)
[email protected]:/etc# mdadm --examine /dev/sdb
/dev/sdb:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 78601ff4:5022822d:40ae7e71:1794c4d6
           Name : openmediavault:0
  Creation Time : Sat Jan  5 23:58:39 2013
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 5860271024 (2794.40 GiB 3000.46 GB)
     Array Size : 11720540160 (11177.58 GiB 12001.83 GB)
  Used Dev Size : 5860270080 (2794.39 GiB 3000.46 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 08c8efa3:e8b07613:0a79598e:521e0a25

    Update Time : Sat Jul  1 20:40:48 2017
       Checksum : d4655f24 - correct
         Events : 57494

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 4
   Array State : AAAAA ('A' == active, '.' == missing)
[email protected]:/etc# mdadm --mdadm --detail
mdadm: unrecognized option '--mdadm'
Usage: mdadm --help
  for help
[email protected]:/etc# mdadm --detail
mdadm: No devices given.
[email protected]:/etc# /proc/mdstat
-bash: /proc/mdstat: Toegang geweigerd
[email protected]:/etc# cd /dev/
[email protected]:/dev# ls
agpgart          dri    loop3         net                 rtc   sde1      stderr  tty16  tty27  tty38  tty49  tty6   uinput   vcsa3
autofs           fb0    loop4         network_latency     rtc0  sdf       stdin   tty17  tty28  tty39  tty5   tty60  urandom  vcsa4
block            fd     loop5         network_throughput  sda   sg0       stdout  tty18  tty29  tty4   tty50  tty61  vcs      vcsa5
bsg              full   loop6         null                sda1  sg1       tty     tty19  tty3   tty40  tty51  tty62  vcs1     vcsa6
btrfs-control    fuse   loop7         oldmem              sda2  sg2       tty0    tty2   tty30  tty41  tty52  tty63  vcs2     vga_arbiter
bus              hpet   loop-control  port                sda5  sg3       tty1    tty20  tty31  tty42  tty53  tty7   vcs3     watchdog
char             input  MAKEDEV       ppp                 sdb   sg4       tty10   tty21  tty32  tty43  tty54  tty8   vcs4     xconsole
console          kmsg   mapper        psaux               sdc   sg5       tty11   tty22  tty33  tty44  tty55  tty9   vcs5     zero
core             log    mcelog        ptmx                sdc1  shm       tty12   tty23  tty34  tty45  tty56  ttyS0  vcs6
cpu              loop0  md            pts                 sdd   snapshot  tty13   tty24  tty35  tty46  tty57  ttyS1  vcsa
cpu_dma_latency  loop1  md0           random              sdd1  snd       tty14   tty25  tty36  tty47  tty58  ttyS2  vcsa1
disk             loop2  mem           root                sde   sndstat   tty15   tty26  tty37  tty48  tty59  ttyS3  vcsa2
[email protected]:/dev# cd md/
[email protected]:/dev/md# ls
[email protected]:/dev/md# nano /etc/mdadm/mdadm.conf
[email protected]:/dev/md# mdadm --create /dev/md/0 --chunk=512 --raid-devices=5 --spare-devices=0 --assume-clean --level=5 --name=openmediavault /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf --verbose
mdadm: layout defaults to left-symmetric
mdadm: layout defaults to left-symmetric
mdadm: super1.x cannot open /dev/sdb: Device or resource busy
mdadm: failed container membership check
mdadm: cannot open /dev/sdb: Device or resource busy
[email protected]:/dev/md# mdadm --create /dev/md/0 --chunk=512 --raid-devices=5 --spare-devices=0 --assume-clean --level=5 --name=openmediavault /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf --verbose
mdadm: layout defaults to left-symmetric
mdadm: layout defaults to left-symmetric
mdadm: super1.x cannot open /dev/sdb: Device or resource busy
mdadm: failed container membership check
mdadm: cannot open /dev/sdb: Device or resource busy
[email protected]:/dev/md# proc/mdstat
-bash: proc/mdstat: Bestand of map bestaat niet
[email protected]:/dev/md# catproc/mdstat
-bash: catproc/mdstat: Bestand of map bestaat niet
[email protected]:/dev/md# cat proc/mdstat
cat: proc/mdstat: Bestand of map bestaat niet
[email protected]:/dev/md# cat proc/mdstat
cat: proc/mdstat: Bestand of map bestaat niet
[email protected]:/dev/md# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : inactive sdf[5] sdb[8]
      5860271024 blocks super 1.2

unused devices: <none>
[email protected]:/dev/md# mdadm --stop /dev/md0
mdadm: stopped /dev/md0
[email protected]:/dev/md# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
unused devices: <none>
[email protected]:/dev/md# mdadm --create /dev/md/0 --chunk=512 --raid-devices=5 --spare-devices=0 --assume-clean --level=5 --name=openmediavault /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf --verbose
mdadm: layout defaults to left-symmetric
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdb appears to be part of a raid array:
    level=raid5 devices=5 ctime=Sat Jan  5 23:58:39 2013
mdadm: /dev/sdc appears to be part of a raid array:
    level=raid0 devices=0 ctime=Thu Jan  1 01:00:00 1970
mdadm: partition table exists on /dev/sdc but will be lost or
       meaningless after creating array
mdadm: /dev/sdd appears to be part of a raid array:
    level=raid0 devices=0 ctime=Thu Jan  1 01:00:00 1970
mdadm: partition table exists on /dev/sdd but will be lost or
       meaningless after creating array
mdadm: /dev/sde appears to be part of a raid array:
    level=raid0 devices=0 ctime=Thu Jan  1 01:00:00 1970
mdadm: partition table exists on /dev/sde but will be lost or
       meaningless after creating array
mdadm: /dev/sdf appears to be part of a raid array:
    level=raid5 devices=5 ctime=Sat Jan  5 23:58:39 2013
mdadm: size set to 2930135040K
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md/0 started.
[email protected]:/dev/md# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active (auto-read-only) raid5 sdf[4] sde[3] sdd[2] sdc[1] sdb[0]
      11720540160 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]

unused devices: <none>
[email protected]:/dev/md#
Broadcast message from [email protected] (Wed Jul  5 22:14:24 2017):

The system is going down for reboot NOW!
login as: root
[email protected]'s password:
Linux DARK-VAULT 3.2.0-4-amd64 #1 SMP Debian 3.2.89-2 x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Jul  5 21:36:36 2017 from big-dark.universe
[email protected]:~# cat /proc/mdstat
Personalities :
unused devices: <none>
[email protected]:~# mdadm --create /dev/md/0 --chunk=512 --raid-devices=5 --spare-devices=0 --assume-clean --level=5 --name=openmediavault /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf --verbose
mdadm: layout defaults to left-symmetric
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdb appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:13:02 2017
mdadm: /dev/sdc appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:13:02 2017
mdadm: partition table exists on /dev/sdc but will be lost or
       meaningless after creating array
mdadm: /dev/sdd appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:13:02 2017
mdadm: partition table exists on /dev/sdd but will be lost or
       meaningless after creating array
mdadm: /dev/sde appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:13:02 2017
mdadm: partition table exists on /dev/sde but will be lost or
       meaningless after creating array
mdadm: /dev/sdf appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:13:02 2017
mdadm: size set to 2930135040K
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md/0 started.
[email protected]:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active (auto-read-only) raid5 sdf[4] sde[3] sdd[2] sdc[1] sdb[0]
      11720540160 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]

unused devices: <none>
[email protected]:~#
Broadcast message from [email protected] (Wed Jul  5 22:21:50 2017):

The system is going down for system halt NOW!
login as: root
[email protected]'s password:
Linux DARK-VAULT 3.2.0-4-amd64 #1 SMP Debian 3.2.89-2 x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Jul  5 22:16:46 2017 from big-dark.universe
[email protected]:~# cat /proc/mdstat
Personalities :
unused devices: <none>
[email protected]:~# mdadm --create /dev/md/0 --chunk=512 --raid-devices=5 --spare-devices=0 --assume-clean --level=5 --name=openmediavault /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf --verbose
mdadm: layout defaults to left-symmetric
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdb appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:17:10 2017
mdadm: partition table exists on /dev/sdb but will be lost or
       meaningless after creating array
mdadm: /dev/sdc appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:17:10 2017
mdadm: partition table exists on /dev/sdc but will be lost or
       meaningless after creating array
mdadm: /dev/sdd appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:17:10 2017
mdadm: /dev/sde appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:17:10 2017
mdadm: partition table exists on /dev/sde but will be lost or
       meaningless after creating array
mdadm: /dev/sdf appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:17:10 2017
mdadm: size set to 2930135040K
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md/0 started.
[email protected]:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active (auto-read-only) raid5 sdf[4] sde[3] sdd[2] sdc[1] sdb[0]
      11720540160 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]

unused devices: <none>
[email protected]:~#
Broadcast message from [email protected] (Wed Jul  5 22:29:32 2017):

The system is going down for reboot NOW!
login as: root
[email protected]'s password:
Access denied
[email protected]'s password:
Linux DARK-VAULT 3.2.0-4-amd64 #1 SMP Debian 3.2.89-2 x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Jul  5 22:25:13 2017 from big-dark.universe
[email protected]:~# cat /proc/mdstat
Personalities :
unused devices: <none>
[email protected]:~# mdadm --create /dev/md/0 --chunk=512 --raid-devices=5 --spare-devices=0 --assume-clean --level=5 --name=openmediavault /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf --verbose
mdadm: layout defaults to left-symmetric
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdb appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:25:22 2017
mdadm: partition table exists on /dev/sdb but will be lost or
       meaningless after creating array
mdadm: /dev/sdc appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:25:22 2017
mdadm: partition table exists on /dev/sdc but will be lost or
       meaningless after creating array
mdadm: /dev/sdd appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:25:22 2017
mdadm: /dev/sde appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:25:22 2017
mdadm: partition table exists on /dev/sde but will be lost or
       meaningless after creating array
mdadm: /dev/sdf appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:25:22 2017
mdadm: size set to 2930135040K
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md/0 started.
[email protected]:~#
login as: root
[email protected]'s password:
Linux DARK-VAULT 3.2.0-4-amd64 #1 SMP Debian 3.2.89-2 x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Jul  5 22:32:02 2017 from big-dark.universe
[email protected]:~# cat /proc/mdstat
Personalities :
unused devices: <none>
[email protected]:~# mdadm --create /dev/md/0 --chunk=512 --raid-devices=5 --spare-devices=0 --assume-clean --level=5 --name=openmediavault /dev/sda /dev/sdb /dev/sdd /dev/sde /dev/sdf --verbose
mdadm: layout defaults to left-symmetric
mdadm: layout defaults to left-symmetric
mdadm: /dev/sda appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:32:11 2017
mdadm: partition table exists on /dev/sda but will be lost or
       meaningless after creating array
mdadm: /dev/sdb appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:32:11 2017
mdadm: /dev/sdd appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:32:11 2017
mdadm: partition table exists on /dev/sdd but will be lost or
       meaningless after creating array
mdadm: /dev/sde appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:32:11 2017
mdadm: partition table exists on /dev/sde but will be lost or
       meaningless after creating array
mdadm: /dev/sdf appears to be part of a raid array:
    level=raid5 devices=5 ctime=Wed Jul  5 22:32:11 2017
mdadm: size set to 2930135040K
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md/0 started.
[email protected]:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active (auto-read-only) raid5 sdf[4] sde[3] sdd[2] sdb[1] sda[0]
      11720540160 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]

unused devices: <none>
[email protected]:~# cd /dev/md/0
-bash: cd: /dev/md/0: Is geen map
[email protected]:~# mount .
./             ../            .bash_history  .bashrc        .config/       .inputrc       .nano_history  .profile       .ssh/
[email protected]:~# mount .
./             ../            .bash_history  .bashrc        .config/       .inputrc       .nano_history  .profile       .ssh/
[email protected]:~# mount /dev/md0
mount: can't find /dev/md0 in /etc/fstab or /etc/mtab
[email protected]:~# mount /dev/md/0
mount: can't find /dev/md/0 in /etc/fstab or /etc/mtab
[email protected]:~# ls
[email protected]:~# cd ..
[email protected]:/# cd ..
[email protected]:/# ls
bin   dev  export  initrd.img  lib64       media  opt   root  sbin     srv  tmp  var
boot  etc  home    lib         lost+found  mnt    proc  run   selinux  sys  usr  vmlinuz
[email protected]:/# cd mnt/
[email protected]:/mnt# ls
Blackhole  Download  Incomplete  Movies
[email protected]:/mnt# mdadm --detail
mdadm: No devices given.
[email protected]:/mnt# mdadm --detail /md0
mdadm: cannot open /md0: No such file or directory
[email protected]:/mnt#
[email protected]:/mnt# mdadm --detail md0
mdadm: cannot open md0: No such file or directory
[email protected]:/mnt# mdadm --examine /dev/sdb
/dev/sdb:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 66e4947b:bca8fc39:3a9383a0:f430d086
           Name : DARK-VAULT:openmediavault  (local to host DARK-VAULT)
  Creation Time : Wed Jul  5 22:42:13 2017
     Raid Level : raid5
   Raid Devices : 5

 Avail Dev Size : 5860271024 (2794.40 GiB 3000.46 GB)
     Array Size : 11720540160 (11177.58 GiB 12001.83 GB)
  Used Dev Size : 5860270080 (2794.39 GiB 3000.46 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 32703b97:02427c1d:fe8051d6:3e1681cf

    Update Time : Wed Jul  5 22:42:13 2017
       Checksum : 9910e7d9 - correct
         Events : 0

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 1
   Array State : AAAAA ('A' == active, '.' == missing)
[email protected]:/mnt# mdadm -Q /dev/md0
/dev/md0: 11177.58GiB raid5 5 devices, 0 spares. Use mdadm --detail for more detail.
[email protected]:/mnt# mdadm --assemble /dev/md0 /dev/sd[abdef] --verbose --force
mdadm: looking for devices for /dev/md0
mdadm: /dev/sda is busy - skipping
mdadm: /dev/sdb is busy - skipping
mdadm: /dev/sdd is busy - skipping
mdadm: /dev/sde is busy - skipping
mdadm: /dev/sdf is busy - skipping
[email protected]:/mnt# mdstat
-bash: mdstat: opdracht niet gevonden
[email protected]:/mnt# cat /proc/mdstat\
> cat /proc/mdstat\^C
[email protected]:/mnt# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active (auto-read-only) raid5 sdf[4] sde[3] sdd[2] sdb[1] sda[0]
      11720540160 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]

unused devices: <none>
[email protected]:/mnt# mdadm --manage /dev/md0 --stop
mdadm: stopped /dev/md0
[email protected]:/mnt# mdadm --assemble /dev/md0 /dev/sd[abdef] --verbose --force
mdadm: looking for devices for /dev/md0
mdadm: /dev/sda is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdb is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdd is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sde is identified as a member of /dev/md0, slot 3.
mdadm: /dev/sdf is identified as a member of /dev/md0, slot 4.
mdadm: added /dev/sdb to /dev/md0 as 1
mdadm: added /dev/sdd to /dev/md0 as 2
mdadm: added /dev/sde to /dev/md0 as 3
mdadm: added /dev/sdf to /dev/md0 as 4
mdadm: added /dev/sda to /dev/md0 as 0
mdadm: /dev/md0 has been started with 5 drives.
[email protected]:/mnt# mke2fs -n /dev/md0
mke2fs 1.42.5 (29-Jul-2012)
Bestandssysteemlabel=
Soort besturingssysteem: Linux
Blokgrootte=4096 (log=2)
Fragmentgrootte=4096 (log=2)
'stride'=128 blokken, 'stripe'-breedte=512 blokken
366268416 inodes, 2930135040 blokken
146506752 blokken (5.00%) gereserveerd voor systeembeheer
Eerste gegevensblok=0
Maximum aantal bestandssysteemblokken=4294967296
89421 blokgroepen
32768 blokken per groep, 32768 fragmenten per groep
4096 inodes per groep
Superblokreservekopieën opgeslagen in blokken:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848, 512000000, 550731776, 644972544, 1934917632,
        2560000000

[email protected]:/mnt# e2fsck -b 2560000000 /dev/md0
e2fsck 1.42.5 (29-Jul-2012)
e2fsck: Ongeldig argument tijdens openen van /dev/md0

Het superblok is onleesbaar of omschrijft geen geldig ext2-bestandssysteem.
Als het apparaat juist is en werkelijk een ext2-bestandssysteem bevat
(en niet swap of UFS of iets anders), dan is het superblok beschadigd.
U kunt dan proberen een ander superblok te gebruiken, bijvoorbeeld:
    e2fsck -b 8193 <apparaat>

[email protected]:/mnt# e4fsck -b 2560000000 /dev/md0
-bash: e4fsck: opdracht niet gevonden
[email protected]:/mnt# e2fsck -b 32768 /dev/md0
e2fsck 1.42.5 (29-Jul-2012)
e2fsck: Ongeldig magisch getal in superblok tijdens openen van /dev/md0

Het superblok is onleesbaar of omschrijft geen geldig ext2-bestandssysteem.
Als het apparaat juist is en werkelijk een ext2-bestandssysteem bevat
(en niet swap of UFS of iets anders), dan is het superblok beschadigd.
U kunt dan proberen een ander superblok te gebruiken, bijvoorbeeld:
    e2fsck -b 8193 <apparaat>

[email protected]:/mnt# e2fsck -b 98304 /dev/md0
e2fsck 1.42.5 (29-Jul-2012)
Superblok heeft een ongeldig journal (inode 8).
Wissen<j>? ja
*** ext3 journal has been deleted - filesystem is now ext2 only ***

Journal-vlag in superblok is niet gezet, maar er is wel een journal inode.
Wissen<j>? geannuleerd!

DarKHole: ***** BESTANDSSYSTEEM IS VERANDERD *****
[email protected]:/mnt# mke2fs -n /dev/md0
mke2fs 1.42.5 (29-Jul-2012)
Bestandssysteemlabel=
Soort besturingssysteem: Linux
Blokgrootte=4096 (log=2)
Fragmentgrootte=4096 (log=2)
'stride'=128 blokken, 'stripe'-breedte=512 blokken
366268416 inodes, 2930135040 blokken
146506752 blokken (5.00%) gereserveerd voor systeembeheer
Eerste gegevensblok=0
Maximum aantal bestandssysteemblokken=4294967296
89421 blokgroepen
32768 blokken per groep, 32768 fragmenten per groep
4096 inodes per groep
Superblokreservekopieën opgeslagen in blokken:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848, 512000000, 550731776, 644972544, 1934917632,
        2560000000

[email protected]:/mnt# e2fsck -b 214990848 /dev/md0
e2fsck 1.42.5 (29-Jul-2012)
e2fsck: Ongeldig argument tijdens openen van /dev/md0

Het superblok is onleesbaar of omschrijft geen geldig ext2-bestandssysteem.
Als het apparaat juist is en werkelijk een ext2-bestandssysteem bevat
(en niet swap of UFS of iets anders), dan is het superblok beschadigd.
U kunt dan proberen een ander superblok te gebruiken, bijvoorbeeld:
    e2fsck -b 8193 <apparaat>

[email protected]:/mnt# e2fsck -b 7962624 /dev/md0
e2fsck 1.42.5 (29-Jul-2012)
Superblok heeft een ongeldig journal (inode 8).
Wissen<j>? ja
*** ext3 journal has been deleted - filesystem is now ext2 only ***

Journal-vlag in superblok is niet gezet, maar er is wel een journal inode.
Wissen<j>? ja
inode-bitkaart voor groep 32640 zit niet in groep  (blok 3513143824)
Herplaatsen<j>? nee
blok-bitkaart voor groep 65408 zit niet in groep  (blok 3758096896)
Herplaatsen<j>? nee
inode-bitkaart voor groep 65408 zit niet in groep  (blok 3758096896)
Herplaatsen<j>? nee
inodetabel voor groep 65408 zit niet in groep  (blok 3758096384)
WAARSCHUWING: ERNSTIG VERLIES VAN GEGEVENS IS MOGELIJK.
Herplaatsen<j>? geannuleerd!

DarKHole: ***** BESTANDSSYSTEEM IS VERANDERD *****

DarKHole: ********** WAARSCHUWING: bestandssysteem bevat nog fouten **********

[email protected]:/mnt# e2fsck -b 819200 /dev/md0
e2fsck 1.42.5 (29-Jul-2012)
e2fsck: Ongeldig magisch getal in superblok tijdens openen van /dev/md0

Het superblok is onleesbaar of omschrijft geen geldig ext2-bestandssysteem.
Als het apparaat juist is en werkelijk een ext2-bestandssysteem bevat
(en niet swap of UFS of iets anders), dan is het superblok beschadigd.
U kunt dan proberen een ander superblok te gebruiken, bijvoorbeeld:
    e2fsck -b 8193 <apparaat>

[email protected]:/mnt# e2fsck -b 1605630 /dev/md0
e2fsck 1.42.5 (29-Jul-2012)
e2fsck: Ongeldig magisch getal in superblok tijdens openen van /dev/md0

Het superblok is onleesbaar of omschrijft geen geldig ext2-bestandssysteem.
Als het apparaat juist is en werkelijk een ext2-bestandssysteem bevat
(en niet swap of UFS of iets anders), dan is het superblok beschadigd.
U kunt dan proberen een ander superblok te gebruiken, bijvoorbeeld:
    e2fsck -b 8193 <apparaat>

[email protected]:/mnt# e2fsck -b 1605632 /dev/md0
e2fsck 1.42.5 (29-Jul-2012)
e2fsck: Ongeldig magisch getal in superblok tijdens openen van /dev/md0

Het superblok is onleesbaar of omschrijft geen geldig ext2-bestandssysteem.
Als het apparaat juist is en werkelijk een ext2-bestandssysteem bevat
(en niet swap of UFS of iets anders), dan is het superblok beschadigd.
U kunt dan proberen een ander superblok te gebruiken, bijvoorbeeld:
    e2fsck -b 8193 <apparaat>

[email protected]:/mnt# e2fsck -b 32768 /dev/md0
e2fsck 1.42.5 (29-Jul-2012)
e2fsck: Ongeldig magisch getal in superblok tijdens openen van /dev/md0

Het superblok is onleesbaar of omschrijft geen geldig ext2-bestandssysteem.
Als het apparaat juist is en werkelijk een ext2-bestandssysteem bevat
(en niet swap of UFS of iets anders), dan is het superblok beschadigd.
U kunt dan proberen een ander superblok te gebruiken, bijvoorbeeld:
    e2fsck -b 8193 <apparaat>

[email protected]:/mnt# e2fsck -b 98304 /dev/md0
e2fsck 1.42.5 (29-Jul-2012)
Superblok heeft een ongeldig journal (inode 8).
Wissen<j>? ja
*** ext3 journal has been deleted - filesystem is now ext2 only ***

Journal-vlag in superblok is niet gezet, maar er is wel een journal inode.
Wissen<j>? nee
inode-bitkaart voor groep 32640 zit niet in groep  (blok 3513143824)
Herplaatsen<j>? nee
blok-bitkaart voor groep 65408 zit niet in groep  (blok 3758096896)
Herplaatsen<j>? nee
inode-bitkaart voor groep 65408 zit niet in groep  (blok 3758096896)
Herplaatsen<j>? nee
inodetabel voor groep 65408 zit niet in groep  (blok 3758096384)
WAARSCHUWING: ERNSTIG VERLIES VAN GEGEVENS IS MOGELIJK.
Herplaatsen<j>? geannuleerd!

DarKHole: ***** BESTANDSSYSTEEM IS VERANDERD *****

DarKHole: ********** WAARSCHUWING: bestandssysteem bevat nog fouten **********

[email protected]:/mnt# mkfs.ext4 -S /dev/md0
mke2fs 1.42.5 (29-Jul-2012)
Bestandssysteemlabel=
Soort besturingssysteem: Linux
Blokgrootte=4096 (log=2)
Fragmentgrootte=4096 (log=2)
'stride'=128 blokken, 'stripe'-breedte=512 blokken
366268416 inodes, 2930135040 blokken
146506752 blokken (5.00%) gereserveerd voor systeembeheer
Eerste gegevensblok=0
Maximum aantal bestandssysteemblokken=4294967296
89421 blokgroepen
32768 blokken per groep, 32768 fragmenten per groep
4096 inodes per groep
Superblokreservekopieën opgeslagen in blokken:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848, 512000000, 550731776, 644972544, 1934917632,
        2560000000

Reserveren van groepstabellen: voltooid
Aanmaken van journal wordt overgeslagen wegens optie '-S'.
Schrijven van superblokken en bestandssysteem-metagegevens: voltooid

[email protected]:/mnt# dmesg |tail
[ 2747.356515]  --- level:5 rd:5 wd:5
[ 2747.356523]  disk 0, o:1, dev:sda
[ 2747.356529]  disk 1, o:1, dev:sdb
[ 2747.356537]  disk 2, o:1, dev:sdd
[ 2747.356543]  disk 3, o:1, dev:sde
[ 2747.356551]  disk 4, o:1, dev:sdf
[ 2747.356687] md0: detected capacity change from 0 to 12001833123840
[ 2747.360382]  md0: unknown partition table
[ 4171.420730] EXT4-fs (md0): ext4_check_descriptors: Checksum for group 0 failed (54092!=34635)
[ 4171.420893] EXT4-fs (md0): group descriptors corrupted!
[email protected]:/mnt# dmesg |tail
[ 2747.356515]  --- level:5 rd:5 wd:5
[ 2747.356523]  disk 0, o:1, dev:sda
[ 2747.356529]  disk 1, o:1, dev:sdb
[ 2747.356537]  disk 2, o:1, dev:sdd
[ 2747.356543]  disk 3, o:1, dev:sde
[ 2747.356551]  disk 4, o:1, dev:sdf
[ 2747.356687] md0: detected capacity change from 0 to 12001833123840
[ 2747.360382]  md0: unknown partition table
[ 4171.420730] EXT4-fs (md0): ext4_check_descriptors: Checksum for group 0 failed (54092!=34635)
[ 4171.420893] EXT4-fs (md0): group descriptors corrupted!
[email protected]:/mnt# fsck
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
/dev/sdc1 is mounted.
e2fsck: Kan niet doorgaan.  Gestopt.


[email protected]:/mnt# mdadm --assemble /dev/md0 /dev/sd[abdef] --verbose --force
mdadm: looking for devices for /dev/md0
mdadm: /dev/sda is busy - skipping
mdadm: /dev/sdb is busy - skipping
mdadm: /dev/sdd is busy - skipping
mdadm: /dev/sde is busy - skipping
mdadm: /dev/sdf is busy - skipping
[email protected]:/mnt# dmesg |tail
[ 2747.356515]  --- level:5 rd:5 wd:5
[ 2747.356523]  disk 0, o:1, dev:sda
[ 2747.356529]  disk 1, o:1, dev:sdb
[ 2747.356537]  disk 2, o:1, dev:sdd
[ 2747.356543]  disk 3, o:1, dev:sde
[ 2747.356551]  disk 4, o:1, dev:sdf
[ 2747.356687] md0: detected capacity change from 0 to 12001833123840
[ 2747.360382]  md0: unknown partition table
[ 4171.420730] EXT4-fs (md0): ext4_check_descriptors: Checksum for group 0 failed (54092!=34635)
[ 4171.420893] EXT4-fs (md0): group descriptors corrupted!
[email protected]:/mnt# mkfs.ext4 -S /dev/md0
mke2fs 1.42.5 (29-Jul-2012)
Bestandssysteemlabel=
Soort besturingssysteem: Linux
Blokgrootte=4096 (log=2)
Fragmentgrootte=4096 (log=2)
'stride'=128 blokken, 'stripe'-breedte=512 blokken
366268416 inodes, 2930135040 blokken
146506752 blokken (5.00%) gereserveerd voor systeembeheer
Eerste gegevensblok=0
Maximum aantal bestandssysteemblokken=4294967296
89421 blokgroepen
32768 blokken per groep, 32768 fragmenten per groep
4096 inodes per groep
Superblokreservekopieën opgeslagen in blokken:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848, 512000000, 550731776, 644972544, 1934917632,
        2560000000

Reserveren van groepstabellen: voltooid
Aanmaken van journal wordt overgeslagen wegens optie '-S'.
Schrijven van superblokken en bestandssysteem-metagegevens: voltooid

[email protected]:/mnt#
Broadcast message from [email protected] (Thu Jul  6 00:00:59 2017):

The system is going down for reboot NOW!
login as: root
[email protected]'s password:
Linux DARK-VAULT 3.2.0-4-amd64 #1 SMP Debian 3.2.89-2 x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Jul  5 22:41:31 2017 from big-dark.universe
[email protected]:~# mkfs.ext4 -S /dev/md0
mke2fs 1.42.5 (29-Jul-2012)
Kan de status van /dev/md0 niet opvragen -- Bestand of map bestaat niet

Het apparaat bestaat blijkbaar niet; heeft u het juist opgegeven?
[email protected]:~# mdadm --assemble /dev/md0 /dev/sd[abdef] --verbose --force
mdadm: looking for devices for /dev/md0
mdadm: /dev/sda is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdb is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdd is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sde is identified as a member of /dev/md0, slot 3.
mdadm: /dev/sdf is identified as a member of /dev/md0, slot 4.
mdadm: added /dev/sdb to /dev/md0 as 1
mdadm: added /dev/sdd to /dev/md0 as 2
mdadm: added /dev/sde to /dev/md0 as 3
mdadm: added /dev/sdf to /dev/md0 as 4
mdadm: added /dev/sda to /dev/md0 as 0
mdadm: /dev/md0 has been started with 5 drives.
[email protected]:~# mkfs.ext4 --help
mkfs.ext4: ongeldige optie -- '-'
Gebruik:  mkfs.ext4 [-b blokgrootte] [-c|-l bestandsnaam] [-C clustergrootte]
          [-g blokken_per_groep] [-G flexgroepgrootte] [-i bytes_per_inode]
          [-I inode-grootte] [-J journal-opties] [-L label] [-N aantal_inodes]
          [-m percentage_gereserveerde_blokken] [-M laatste_aankoppelingspunt]
          [-o naam_van_aanmakende_besturingssyteem] [-O functie[,...]] [-U UUID]
          [-r bestandssysteemversie] [-t bestandssysteemsoort] [-T gebruikstype]
          [-E uitgebreide_optie[,...]] [-jnqvDFKSV]  apparaat  [aantal_blokken]
[email protected]:~# mkfs.ext4 -j /dev/md0
mke2fs 1.42.5 (29-Jul-2012)
Bestandssysteemlabel=
Soort besturingssysteem: Linux
Blokgrootte=4096 (log=2)
Fragmentgrootte=4096 (log=2)
'stride'=128 blokken, 'stripe'-breedte=512 blokken
366268416 inodes, 2930135040 blokken
146506752 blokken (5.00%) gereserveerd voor systeembeheer
Eerste gegevensblok=0
Maximum aantal bestandssysteemblokken=4294967296
89421 blokgroepen
32768 blokken per groep, 32768 fragmenten per groep
4096 inodes per groep
Superblokreservekopieën opgeslagen in blokken:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848, 512000000, 550731776, 644972544, 1934917632,
        2560000000

Reserveren van groepstabellen: voltooid
Schrijven van inodetabellen: voltooid
Aanmaken van journal (32768 blokken): voltooid
Schrijven van superblokken en bestandssysteem-metagegevens: voltooid

[email protected]:~# mkfs.ext4 -j /dev/md0

[/size]

User avatar
Jared
Forum Admin
Posts: 3517
Joined: Mon Jan 12, 2015 12:32 pm
Location: Providence, RI
Contact: Website Facebook Twitter Skype YouTube Google+

Crashed mdadm raid 5

Tue Sep 26, 2017 8:56 am

Usually, it's easiest to analyze and build a virtual RAID using software such as R-Studio or R-Explorer. But, with 5 drives you've got 120 possible drive order combinations. So it'll be quite tedious to try and brute force figure it out. Having some knowledge of filesystem structures will help a lot as even figuring out one drive's location will cut that number down a lot.

Boonstra
Data Recovery Noob
Posts: 6
Joined: Mon Sep 25, 2017 5:49 pm

Crashed mdadm raid 5

Tue Sep 26, 2017 9:20 am

I know the location of 2 out of 5 drives..

Boonstra
Data Recovery Noob
Posts: 6
Joined: Mon Sep 25, 2017 5:49 pm

Crashed mdadm raid 5

Tue Sep 26, 2017 5:28 pm

are there also Linux alternatives to R-studio and R-explorer?

User avatar
Blizzard
Experienced DR Tech
Posts: 245
Joined: Fri Jun 24, 2016 12:06 am
Location: GA - USA
Contact: Website Facebook Twitter

Crashed mdadm raid 5

Tue Sep 26, 2017 8:59 pm

Boonstra wrote:are there also Linux alternatives to R-studio and R-explorer?
R-Studio Linux

Boonstra
Data Recovery Noob
Posts: 6
Joined: Mon Sep 25, 2017 5:49 pm

Crashed mdadm raid 5

Wed Sep 27, 2017 11:23 am

What I meant. Are there other linux programs equal in function. :-)

User avatar
lcoughey
Forum Moderator
Posts: 590
Joined: Mon Jan 12, 2015 12:46 pm
Location: Ontario, Canada
Contact: Website Facebook Twitter Google+

Crashed mdadm raid 5

Wed Sep 27, 2017 12:23 pm

Boonstra wrote:What I meant. Are there other linux programs equal in function. :-)

R-Explorer is another option.

User avatar
Jared
Forum Admin
Posts: 3517
Joined: Mon Jan 12, 2015 12:32 pm
Location: Providence, RI
Contact: Website Facebook Twitter Skype YouTube Google+

Crashed mdadm raid 5

Wed Sep 27, 2017 2:01 pm

Boonstra wrote:Source of the post What I meant. Are there other linux programs equal in function.


Yes, R-Studio for Linux like Blizzard said. Even just the demo can be used to find the settings. Then, you can assemble it however you'd like.

Boonstra
Data Recovery Noob
Posts: 6
Joined: Mon Sep 25, 2017 5:49 pm

Crashed mdadm raid 5

Sun Oct 08, 2017 3:34 pm

Been out of the country for a couple of days. time to pick this up again :).

If got R-studio installed and it detects my disk and the configuration of the new setup.. but thats not the right order of disk of my old raid (before the forced build and new journal).

should i just try to force different setups in R-studio and let is scan for files?

User avatar
Jared
Forum Admin
Posts: 3517
Joined: Mon Jan 12, 2015 12:32 pm
Location: Providence, RI
Contact: Website Facebook Twitter Skype YouTube Google+

Crashed mdadm raid 5

Mon Oct 09, 2017 10:27 am

Boonstra wrote:Source of the post should i just try to force different setups in R-studio and let is scan for files?


If you don't have any knowledge of file system structures and how to analyze the layout, then yes, brute force is the general method. Just keep assembling it different ways and see what you find. If you have to scan each time though, it can get really time consuming.

Return to “RAID Data Recovery Forum”

Who is online

Users browsing this forum: No registered users and 1 guest