RAID 5 with 3 Drives 3TB each - Two drives faild and RAID faild - help recover

danieliod · 16. Juni 2016

Hello,

I recieved today notification from my OMV server that 2 drives faild.
The RAID status in the WebGUI shows "clean, FAILD" and oly drive /dev/sdd listed.

This is the info:

Code

Personalities : [raid6] [raid5] [raid4]
md127 : active raid5 sdb[3](F) sdd[2] sdc[1](F)
      5855716352 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/1] [__U]


unused devices: <none>
/dev/md127: LABEL="RAID" UUID="7fbde406-4c77-4bed-94c8-b6b045f9e757" TYPE="ext4"
/dev/sda1: UUID="c4773f30-7a51-4b82-89b2-dc1e8b25f1ff" TYPE="ext4"
/dev/sda3: LABEL="DATA" UUID="395fdb16-d339-4c6d-bbf6-6419f1aaa444" TYPE="ext4"
/dev/sda5: UUID="8cf58870-b3d3-4402-9e95-cbf71c041584" TYPE="swap"
/dev/sdd: UUID="332d8084-c2b3-a139-44a4-f8e16865cc49" UUID_SUB="d17728a0-84fe-c504-ffb0-e13849c2282d" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/sdf: UUID="332d8084-c2b3-a139-44a4-f8e16865cc49" UUID_SUB="846db758-a812-02e4-2ad6-3380f255dd97" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/sdg: UUID="332d8084-c2b3-a139-44a4-f8e16865cc49" UUID_SUB="34c4db9b-ec1b-b61b-2a46-cb372f84d784" LABEL="openmediavault:NAS" TYPE="linux_raid_member"


Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x1e011e02


   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


Disk /dev/sda: 126.0 GB, 126035288064 bytes
255 heads, 63 sectors/track, 15322 cylinders, total 246162672 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: 0x0006ad32


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    29493247    14745600   83  Linux
/dev/sda2        29495294    32567295     1536001    5  Extended
/dev/sda3        32567296   246161407   106797056   83  Linux
/dev/sda5        29495296    32567295     1536000   82  Linux swap / Solaris


Disk /dev/md127: 5996.3 GB, 5996253544448 bytes
2 heads, 4 sectors/track, 1463929088 cylinders, total 11711432704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0x00000000


Disk /dev/sdf: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sdg: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x1e011e00


   Device Boot      Start         End      Blocks   Id  System

Alles anzeigen

cat /etc/mdadm/mdadm.conf

Code

ARRAY /dev/md/NAS metadata=1.2 spares=1 name=openmediavault:NAS UUID=332d8084:c2b3a139:44a4f8e1:6865cc49

Please let me know what more info I need to provide.

Thank you

ryecoaaron · 17. Juni 2016

mdadm --stop /dev/md127
mdadm --assemble --force --verbose /dev/md127 /dev/sd[dfg]

Normally when it says failed, that is bad though. I hope you have a backup.

danieliod · 17. Juni 2016

Hi,

I shutdown my server and connected the SATA cables better, then I saw all my Drives again.
I ran both commands from above and recieved the following:

Code

mdadm: stopped /dev/md127
sudo mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcd]
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is busy - skipping
mdadm: /dev/sdc is busy - skipping
mdadm: /dev/sdd is identified as a member of /dev/md127, slot 2.
mdadm: no uptodate device for slot 0 of /dev/md127
mdadm: no uptodate device for slot 1 of /dev/md127
mdadm: added /dev/sdd to /dev/md127 as 2
mdadm: /dev/md127 assembled from 1 drive - not enough to start the array.

I have looked on the System Info and saw that suddently I have also md126 which is inactive

Code

Personalities : [raid6] [raid5] [raid4]
md127 : inactive sdd[2](S)
      2930135512 blocks super 1.2


md126 : inactive sdc[1](S) sdb[3](S)
      5860271024 blocks super 1.2


unused devices: <none>
/dev/sda1: UUID="c4773f30-7a51-4b82-89b2-dc1e8b25f1ff" TYPE="ext4"
/dev/sda3: LABEL="DATA" UUID="395fdb16-d339-4c6d-bbf6-6419f1aaa444" TYPE="ext4"
/dev/sda5: UUID="8cf58870-b3d3-4402-9e95-cbf71c041584" TYPE="swap"
/dev/sdb: UUID="332d8084-c2b3-a139-44a4-f8e16865cc49" UUID_SUB="846db758-a812-02e4-2ad6-3380f255dd97" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/sdc: UUID="332d8084-c2b3-a139-44a4-f8e16865cc49" UUID_SUB="34c4db9b-ec1b-b61b-2a46-cb372f84d784" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/sdd: UUID="332d8084-c2b3-a139-44a4-f8e16865cc49" UUID_SUB="d17728a0-84fe-c504-ffb0-e13849c2282d" LABEL="openmediavault:NAS" TYPE="linux_raid_member"


Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x1e011e00


   Device Boot      Start         End      Blocks   Id  System


Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x1e011e02


   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


Disk /dev/sda: 126.0 GB, 126035288064 bytes
255 heads, 63 sectors/track, 15322 cylinders, total 246162672 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: 0x0006ad32


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    29493247    14745600   83  Linux
/dev/sda2        29495294    32567295     1536001    5  Extended
/dev/sda3        32567296   246161407   106797056   83  Linux
/dev/sda5        29495296    32567295     1536000   82  Linux swap / Solaris

Alles anzeigen

What action should I take in order to preserve my data?

Thank you

ryecoaaron · 17. Juni 2016

mdadm --stop /dev/md126
mdadm --stop /dev/md127
mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcd]

danieliod · 17. Juni 2016

Thank you very much for the prompt reply.
It seems that one of the drives is out of date and was not captured as part of the RAID.

How to I know the progress?

Code

sudo mdadm --stop /dev/md126
[sudo] password for media:
mdadm: stopped /dev/md126
$ sudo mdadm --stop /dev/md127
mdadm: stopped /dev/md127
$ sudo mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcd]
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is identified as a member of /dev/md127, slot 0.
mdadm: /dev/sdc is identified as a member of /dev/md127, slot 1.
mdadm: /dev/sdd is identified as a member of /dev/md127, slot 2.
mdadm: forcing event count in /dev/sdc(1) from 228355 upto 228401
mdadm: added /dev/sdb to /dev/md127 as 0 (possibly out of date)
mdadm: added /dev/sdd to /dev/md127 as 2
mdadm: added /dev/sdc to /dev/md127 as 1
mdadm: /dev/md127 has been started with 2 drives (out of 3).

Alles anzeigen

updated system info:

Code

Personalities : [raid6] [raid5] [raid4]
md127 : active (auto-read-only) raid5 sdc[1] sdd[2]
      5855716352 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [_UU]


unused devices: <none>
/dev/sda1: UUID="c4773f30-7a51-4b82-89b2-dc1e8b25f1ff" TYPE="ext4"
/dev/sda3: LABEL="DATA" UUID="395fdb16-d339-4c6d-bbf6-6419f1aaa444" TYPE="ext4"
/dev/sda5: UUID="8cf58870-b3d3-4402-9e95-cbf71c041584" TYPE="swap"
/dev/sdb: UUID="332d8084-c2b3-a139-44a4-f8e16865cc49" UUID_SUB="846db758-a812-02e4-2ad6-3380f255dd97" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/sdc: UUID="332d8084-c2b3-a139-44a4-f8e16865cc49" UUID_SUB="34c4db9b-ec1b-b61b-2a46-cb372f84d784" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/sdd: UUID="332d8084-c2b3-a139-44a4-f8e16865cc49" UUID_SUB="d17728a0-84fe-c504-ffb0-e13849c2282d" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/md127: LABEL="RAID" UUID="7fbde406-4c77-4bed-94c8-b6b045f9e757" TYPE="ext4"


Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x1e011e00


   Device Boot      Start         End      Blocks   Id  System


Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x1e011e02


   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


Disk /dev/sda: 126.0 GB, 126035288064 bytes
255 heads, 63 sectors/track, 15322 cylinders, total 246162672 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: 0x0006ad32


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    29493247    14745600   83  Linux
/dev/sda2        29495294    32567295     1536001    5  Extended
/dev/sda3        32567296   246161407   106797056   83  Linux
/dev/sda5        29495296    32567295     1536000   82  Linux swap / Solaris


Disk /dev/md127: 5996.3 GB, 5996253544448 bytes
2 heads, 4 sectors/track, 1463929088 cylinders, total 11711432704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0x00000000

Alles anzeigen

ryecoaaron · 17. Juni 2016

Let the array finish building (look at cat /proc/mdstat) and then zero the out of date drive and recover the drive to the array.

danieliod · 17. Juni 2016

This means it has finished:

Code

sudo cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : active raid5 sdc[1] sdd[2]
      5855716352 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [_UU]


unused devices: <none>

ryecoaaron · 17. Juni 2016

Yes.

dd if=/dev/zero of=/dev/sdb bs=512 count=10000
mdadm --zero-superblock /dev/sdb
Then use recover in raid tab.

danieliod · 18. Juni 2016

Hi,

I have followed the steps and in step 2 recieved the below outcome.
Is it ok? Can i start RAID Recovery now?

Code

sudo dd if=/dev/zero of=/dev/sdb bs=512 count=10000
[sudo] password for media:
10000+0 records in
10000+0 records out
5120000 bytes (5.1 MB) copied, 4.99599 s, 1.0 MB/s
$ sudo mdadm --zero-superblock /dev/sdb
mdadm: Unrecognised md component device - /dev/sdb
$ sudo mdadm --zero-superblock /dev/sdb
mdadm: Unrecognised md component device - /dev/sdb

ryecoaaron · 19. Juni 2016

That is expected in the second step. It is a "just in case" step. Proceed to the next step.

danieliod · 20. Juni 2016

Hi,

From some reason during the RAID Repair my Server shutdown.
When it boot up again, it ave an error regardign the RAID filesystem and ask for Manual intervantion.

I executed:

Code

fsck.ext4 /dev/md127

when it finished it gave a warninig that there still File system issues.
I ran it again and it gave the same error, I restarted and run it again and still the same error.
Now every time I want to restart the server I need to press Contorl+D.

How do perform a file system check that will solve the issue?
This is my boot log:

Code

Mon Jun 20 23:03:11 2016: Setting parameters of disc:  /dev/sdc.
Mon Jun 20 23:03:11 2016:   /dev/sdd.
Mon Jun 20 23:03:11 2016:   /dev/sdb.
Mon Jun 20 23:03:11 2016: Setting preliminary keymap...done.
Mon Jun 20 23:03:11 2016: Activating swap...done.
Mon Jun 20 23:03:11 2016: Checking root file system...fsck from util-linux 2.20.1
Mon Jun 20 23:03:11 2016: /dev/sda1: clean, 328381/922080 files, 2346894/3686400 blocks
Mon Jun 20 23:03:11 2016: done.
Mon Jun 20 23:03:11 2016: Generating udev events for MD arrays...done.
Mon Jun 20 23:03:11 2016: Loading kernel module fuse.
Mon Jun 20 23:03:11 2016: Loading kernel module loop.
Mon Jun 20 23:03:11 2016: Cleaning up temporary files... /tmp.
Mon Jun 20 23:03:11 2016: Setting up LVM Volume Groups...  No volume groups found
Mon Jun 20 23:03:11 2016:   No volume groups found
Mon Jun 20 23:03:11 2016: done.
Mon Jun 20 23:03:11 2016: Activating lvm and md swap...done.
Mon Jun 20 23:03:11 2016: Checking file systems...fsck from util-linux 2.20.1
Mon Jun 20 23:03:11 2016: DATA: clean, 134869/6676480 files, 5910886/26699264 blocks
Mon Jun 20 23:03:11 2016: RAID contains a file system with errors, check forced.
Mon Jun 20 23:03:13 2016: \002'..' in /lost+found/#101924880 (101924880) is <The NULL inode> (0), should be /lost+found (11).
Mon Jun 20 23:05:58 2016: 
Mon Jun 20 23:05:58 2016: 
Mon Jun 20 23:05:58 2016: RAID: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Mon Jun 20 23:05:58 2016: 
Mon Jun 20 23:05:59 2016: fsck died with exit status 4
Mon Jun 20 23:05:59 2016: failed (code 4).
Mon Jun 20 23:05:59 2016: File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... failed!
Mon Jun 20 23:05:59 2016: A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... (warning).
Mon Jun 20 23:05:59 2016: Give root password for maintenance
Mon Jun 20 23:05:59 2016: (or type Control-D to continue): 
Mon Jun 20 23:06:01 2016: Mounting local filesystems...ntfs-3g: Failed to access volume '/dev/disk/by-uuid/4CE6FD69E6FD5424': No such file or directory
Mon Jun 20 23:06:01 2016: 
Mon Jun 20 23:06:01 2016: ntfs-3g 2012.1.15AR.5 external FUSE 29 - Third Generation NTFS Driver
Mon Jun 20 23:06:01 2016: 
Mon Jun 20 23:06:01 2016: 
Mon Jun 20 23:06:01 2016: Copyright (C) 2005-2007 Yura Pakhuchiy
Mon Jun 20 23:06:01 2016: Copyright (C) 2006-2009 Szabolcs Szakacsits
Mon Jun 20 23:06:01 2016: Copyright (C) 2007-2011 Jean-Pierre Andre
Mon Jun 20 23:06:01 2016: Copyright (C) 2009 Erik Larsson
Mon Jun 20 23:06:01 2016: 
Mon Jun 20 23:06:01 2016: Usage:    ntfs-3g [-o option[,...]] <device|image_file> <mount_point>
Mon Jun 20 23:06:01 2016: 
Mon Jun 20 23:06:01 2016: Options:  ro (read-only mount), remove_hiberfile, uid=, gid=,
Mon Jun 20 23:06:01 2016:           umask=, fmask=, dmask=, streams_interface=.
Mon Jun 20 23:06:01 2016:           Please see the details in the manual (type: man ntfs-3g).
Mon Jun 20 23:06:01 2016: 
Mon Jun 20 23:06:01 2016: Example: ntfs-3g /dev/sda1 /mnt/windows
Mon Jun 20 23:06:01 2016: 
Mon Jun 20 23:06:01 2016: News, support and information:  http://tuxera.com
Mon Jun 20 23:06:01 2016: failed.
Mon Jun 20 23:06:01 2016: Activating swapfile swap...done.
Mon Jun 20 23:06:01 2016: Cleaning up temporary files....
Mon Jun 20 23:06:01 2016: Setting kernel variables ...done.
Mon Jun 20 23:06:01 2016: Cleaning up...done.
Mon Jun 20 23:06:01 2016: Setting up resolvconf.../etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf
Mon Jun 20 23:06:01 2016: done.
Mon Jun 20 23:06:01 2016: Configuring network interfaces.../etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf
Mon Jun 20 23:06:02 2016: done.
Mon Jun 20 23:06:02 2016: Starting rpcbind daemon....
Mon Jun 20 23:06:02 2016: Starting NFS common utilities: statd idmapd.
Mon Jun 20 23:06:02 2016: Cleaning up temporary files....
Mon Jun 20 23:06:02 2016: Setting console screen modes.
Mon Jun 20 23:06:02 2016: ^[[9;30]^[[14;30]Skipping font and keymap setup (handled by console-setup).
Mon Jun 20 23:06:02 2016: Setting up console font and keymap...done.
Mon Jun 20 23:06:02 2016: Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix.
Mon Jun 20 23:06:02 2016: Checking quotas...done.
Mon Jun 20 23:06:02 2016: Turning on quotas...done.
Mon Jun 20 23:06:02 2016: INIT: Entering runlevel: 2
Mon Jun 20 23:06:02 2016: Using makefile-style concurrent boot in runlevel 2.
Mon Jun 20 23:06:02 2016: Starting rpcbind daemon...Already running..
Mon Jun 20 23:06:02 2016: Starting NFS common utilities: statd idmapd.
Mon Jun 20 23:06:02 2016: Starting watchdog keepalive daemon: wd_keepalive.
Mon Jun 20 23:06:02 2016: Starting Jdownloader daemon: 
Mon Jun 20 23:06:02 2016: Started Jdownloader daemon
Mon Jun 20 23:06:02 2016: Starting enhanced syslogd: rsyslogd.
Mon Jun 20 23:06:02 2016: Starting anac(h)ronistic cron: anacron.
Mon Jun 20 23:06:02 2016: Starting Docker: docker.
Mon Jun 20 23:06:02 2016: Starting MD monitoring service: mdadm --monitor.
Mon Jun 20 23:06:03 2016: Starting ACPI services....
Mon Jun 20 23:06:03 2016: Starting periodic command scheduler: cron.
Mon Jun 20 23:06:03 2016: Starting bittorrent daemon: transmission-daemon.
Mon Jun 20 23:06:03 2016: Starting couchpotato
Mon Jun 20 23:06:03 2016: Loading cpufreq kernel modules...done (acpi-cpufreq).
Mon Jun 20 23:06:03 2016: Starting system message bus: dbus.
Mon Jun 20 23:06:03 2016: Starting RRDtool data caching daemon: rrdcached.
Mon Jun 20 23:06:03 2016: Starting ddclient....
Mon Jun 20 23:06:03 2016: Starting Samba daemons: nmbd smbd.
Mon Jun 20 23:06:04 2016: Starting AutoSub
Mon Jun 20 23:06:04 2016: AutoSub: Initializing variables and loading config
Mon Jun 20 23:06:04 2016: AutoSub: Starting as a daemon
Mon Jun 20 23:06:04 2016: AutoSub: Disabling console output for daemon.
Mon Jun 20 23:06:04 2016: AutoSub: Starting output to log. Bye!
Mon Jun 20 23:06:04 2016: CPUFreq Utilities: Setting conservative CPUFreq governor...CPU0...CPU1...CPU2...CPU3...done.
Mon Jun 20 23:06:04 2016: Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Mon Jun 20 23:06:04 2016: Starting statistics collection and monitoring daemon: collectd.
Mon Jun 20 23:06:04 2016: Starting nginx: nginx.
Mon Jun 20 23:06:04 2016: Starting NTP server: ntpd.
Mon Jun 20 23:06:04 2016: Starting OpenBSD Secure Shell server: sshd.
Mon Jun 20 23:06:05 2016: Starting VirtualBox kernel modules ...done.
Mon Jun 20 23:06:05 2016: Starting Tvheadend: tvheadend.
Mon Jun 20 23:06:05 2016: Starting SABnzbd
Mon Jun 20 23:06:05 2016: Starting Plex Media Server: done
Mon Jun 20 23:06:05 2016: Starting VirtualBox web service ...done.
Mon Jun 20 23:06:05 2016: Starting OpenMediaVault engine daemon: omv-engined.
Mon Jun 20 23:06:05 2016: Starting MySQL database server: mysqld ..
Mon Jun 20 23:06:05 2016: Checking for tables which need an upgrade, are corrupt or were 
Mon Jun 20 23:06:05 2016: not closed cleanly..
Mon Jun 20 23:06:06 2016: Starting SickBeard
Mon Jun 20 23:06:06 2016: Starting NUT - power devices information server and drivers:  driver(s). upsd.
Mon Jun 20 23:06:06 2016: Starting NUT - power device monitor and shutdown controller: nut-client.
Mon Jun 20 23:06:06 2016: Starting Postfix Mail Transport Agent: postfix.

Alles anzeigen

This is the checkfs log:

Code

Log of fsck -C -R -A -a
Mon Jun 20 23:03:11 2016


fsck from util-linux 2.20.1
DATA: clean, 134869/6676480 files, 5910886/26699264 blocks
RAID contains a file system with errors, check forced.
RAID: '..' in /lost+found/#101924880 (101924880) is <The NULL inode> (0), shoul$


RAID: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)
fsck died with exit status 4


Mon Jun 20 23:05:59 2016
----------------

Alles anzeigen

I also get SpareEvent emails:

Code

A SparesMissing event had been detected on md device /dev/md127.

One more thing, how do I recover data from lost+found, I can't even access the folder.

Thank you

ryecoaaron · 21. Juni 2016

fsck.ext4 -f /dev/md127

danieliod · 21. Juni 2016

The results are still the same, there are 2 issues which couldn't be resolved.

What else can I try?

Sent from my iPhone using Tapatalk

ryecoaaron · 21. Juni 2016

Boot systemrescuecd to try and fix it. It has much newer versions of filesystem utilities.

danieliod · 21. Juni 2016

Hi,

I'm not familiar with this tool, should I downoload: SystemRescueCD 4.7.3 from https://sourceforge.net/projects/systemrescuecd/
and boot it from USB?

Is there any specific tool recommended?

ryecoaaron · 21. Juni 2016

systemrescuecd is something I have been using for years and it is great. Write it to a usb stick with linux live usb creator.

No tools. just the same fsck.ext4 command. The fsck libraries are much newer and might be able to fix your problem.

danieliod · 22. Juni 2016

Hi, I boot with system rescue cd and ran the fsck command. It also didn't fix the issue. Any other options I can try?

Sent from my iPhone using Tapatalk

danieliod · 22. Juni 2016

I made it, thanks to this: http://bitc.bme.emory.edu/~lzhou/blogs/?p=70

ryecoaaron · 23. Juni 2016

The -y flag just answers yes to every question. Were you answering no when running the command I gave you?

danieliod · 23. Juni 2016

Apparently there were 2 folders sized 0. This caused the fsck to fail because they were not correctly. By tweaking the folders with chown and chmod I could create and remove a folder in them and size became valid. Then ran fsck again and FS repaired.

I still have an issue now with a message regarding Spare drive

Sent from my iPhone using Tapatalk

Jetzt mitmachen!