Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 10-18-2011, 11:27 AM   #1
LQ Newbie
Registered: Nov 2010
Posts: 6

Rep: Reputation: 0
raid superblocks errors

I noticed I was missing some files when I was looking on my server by FTP, so I went on my ssh and saw that the files were there but they were marked purple and all permissions and ownership were marked with ?.

I the tryed to make a cp command and got some input output error.

so I searched the web for answers and found someone having same problem. Unmounted my raid (or tryed to) I tryed running fsck /dev/md0 and it say something about superblock error, I read on about the problem he had and he said yes to all of them, so I started too after saying yes to about 15 of them, and saw it was counting up on sectors, and I mostlikely got more than a million sectors, so I said no and got returned to terminal.

after trying some more and get the same like results, also trying to mount my raid again and failed, came by where it said my raid still mounted (or so it claims).
I was looking for another solution.

I found something and tryed cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdc1[0] sdf1[4] sde1[1](F)
5860503552 blocks super 1.0 level 5, 4096k chunk, algorithm 0 [4/2] [U__U]
bitmap: 233/466 pages [932KB], 2048KB chunk

unused devices: <none>
and noticed its missing a harddisk "sdd1"
I then tryed some fsck /dev/sdc-f (one at the time)
sdd came up differently than the others.
fsck 1.41.1 (01-Sep-2008)
e2fsck 1.41.1 (01-Sep-2008)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdd

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
This is where I stopped.
How do I get my raid back so it works and all the files mostly intact?
Is /dev/sdd1 totally dead so I need to buy a new harddisk?

edit: just noticed that sde is failed and sdd is just gone, so I got 2 harddisk out of 4 harddisks in a raid 5 dead. anyway to maybe get it to work again with data?

Last edited by Friis; 10-18-2011 at 03:18 PM.
Old 10-18-2011, 04:54 PM   #2
LQ Newbie
Registered: May 2010
Location: Austin, TX
Distribution: openSUSE
Posts: 8

Rep: Reputation: 0
The fact that two disks went bad close to each other makes me think it might be the IO hardware rather than the disks themselves. This isn't cause for much hope, since a failing IO will often spew garbage/corrupt the disks (ruining the RAID5), but you could try to replace the IO sub-system (new card) or install the disks into a new machine (make sure you install in the same order as before) and then rebuild the RAID array.

Probably a long shot.
Old 10-19-2011, 01:24 PM   #3
LQ Newbie
Registered: Nov 2010
Posts: 6

Original Poster
Rep: Reputation: 0
my harddisks are on my motherboard and running software raid
how do I test the harddisks to see if its working or not working (on the current IO)?

I tryed to run smartctl -H /dev/"device"
smartctl 5.39 2008-10-24 22:33 [i686-suse-linux-gnu] (openSUSE RPM)
Copyright (C) 2002-8 by Bruce Allen,

SMART overall-health self-assessment test result: PASSED
so my harddisks are fine?

fsck on devices saying
fsck 1.41.1 (01-Sep-2008)
e2fsck 1.41.1 (01-Sep-2008)
fsck.ext2: device or resource busy while trying to open /dev/sdc (edited this line since some was in danish)
Filesystem mounted or opened exclusively by another program?
Old 10-19-2011, 05:36 PM   #4
LQ Newbie
Registered: May 2010
Location: Austin, TX
Distribution: openSUSE
Posts: 8

Rep: Reputation: 0
If you have unused space on the disks, another partition, or some area you can write to, that would be helpful to do some basic tests. Problem is you can't write to the RAID area of any one disk without first assembling the array. This wouldn't be dispositive in any case as the problem may be with sectors rather than something central, like the drive motor or actuators.

Otherwise, nothing great comes to mind. With software RAID, you should be able to take the disks and see if you can re-assemble on another machine. Just make sure to write down which drive is which (SDA, SDB, etc.) and what the SATA port order is so you can keep them in the same order. (Not strictly necessary, but makes things easier.)

There may be easier paths to take, but that would be my next step if I really needed to get at the data.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Recovering mdadm superblocks deck- Linux - General 4 10-25-2010 08:53 PM
Superblocks - MD0 or SDA1? joneslja Linux - Newbie 1 08-11-2010 09:25 AM
[SOLVED] Where is the backup superblocks? miceagol Linux - Software 11 03-09-2010 03:54 PM
SATA RAID 0 errors on bootup -- invalid raid superblock vonst Slackware 3 07-04-2006 03:55 PM
Starting RAID devs - Superblocks NOT read... tahiche Linux - Software 2 09-03-2005 04:25 PM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 11:17 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration