LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
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!

Notices


Reply
  Search this Thread
Old 08-13-2013, 03:53 PM   #16
PeteLindsey
LQ Newbie
 
Registered: Aug 2013
Posts: 15

Original Poster
Rep: Reputation: Disabled

yeah blockdev shows same for sda , sdb and sdd

interesting note, i just used pvcreate on the drive and it had not problems, I then used vgcreate and created a test volume no problems, I am really at a loss for what problem mdadm sees with the drive.....
 
Old 08-13-2013, 03:58 PM   #17
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 2,445

Rep: Reputation: Disabled
Did you try running blockdev on the partition device /dev/sdb1 rather than the whole disk? Does the output from blockdev --report /dev/sdb1 match that from blockdev --report /dev/sda1?

Have you tried (carefully) hot-unplugging the drive and re-inserting it? If there's a problem with one of the device nodes, the kernel (and/or udev) should recreate them after a hotplug event.
 
Old 08-13-2013, 04:02 PM   #18
PeteLindsey
LQ Newbie
 
Registered: Aug 2013
Posts: 15

Original Poster
Rep: Reputation: Disabled
I haven't tried hot plugging, but I did run blockdev against the drive and the partition and they match exactly
I did see a note about mdadm and not using the last 256 blocks, however I am not seeing the problems they were seeing...
Is there a way to just copy the GPT label off one drive to another, if it is a corrupt partition or some such I should be able to copy the data off the "failed" drive... Perhaps side stepping whatever the actual problem is.

If you think hot plugging the drive has a genuine chance of giving s different result I will try it. I am only leary because I could accidentally affect one of the 2 remaining drives.

Regards,
 
Old 08-13-2013, 04:10 PM   #19
PeteLindsey
LQ Newbie
 
Registered: Aug 2013
Posts: 15

Original Poster
Rep: Reputation: Disabled
and the plot thickens!!!
Code:
mdadm  --create /dev/md2 --force --level=linear --raid-devices=1 /dev/sdb1
mdadm: array /dev/md2 started.
so how do we explain this?!?!? Obviously mdadm doesn't have a complete problem with /dev/sdb1
 
Old 08-13-2013, 04:18 PM   #20
PeteLindsey
LQ Newbie
 
Registered: Aug 2013
Posts: 15

Original Poster
Rep: Reputation: Disabled
and now using md2 --
Code:
mdadm --detail /dev/md2
/dev/md2:
        Version : 00.90.03
  Creation Time : Tue Aug 13 16:13:18 2013
     Raid Level : linear
     Array Size : 3907017472 (3726.02 GiB 4000.79 GB)
   Raid Devices : 1
  Total Devices : 1
Preferred Minor : 2
    Persistence : Superblock is persistent

    Update Time : Tue Aug 13 16:13:18 2013
          State : clean
 Active Devices : 1
Working Devices : 1
 Failed Devices : 0
  Spare Devices : 0

       Rounding : 64K

           UUID : 1801270c:d40f5667:5f680476:bcde8e3b
         Events : 0.1

    Number   Major   Minor   RaidDevice State
       0       8       17        0      active sync   /dev/sdb1
we see the drive is 3907017472, when the drive that is needed has to be at least 3907017344 (which it is)
so why when I try adding the md device i still get the size error??

Code:
 mdadm --add /dev/md1 /dev/md2
mdadm: /dev/md2 not large enough to join array
 mdadm --add --force /dev/md1 /dev/md2
mdadm: set device faulty failed for /dev/md2:  No such device
It would appear that the --force command ONLY applies to pre-existing drives and the "no such device" is an error because it has never been a part of the set...
 
Old 08-13-2013, 04:26 PM   #21
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 2,445

Rep: Reputation: Disabled
It suddenly occurred to me that if you're running a prehistoric version of parted, perhaps the mdadm tool isn't exactly recent either.

Can you confirm that your version of mdadm is newer than the version in this bug report?
 
Old 08-13-2013, 04:32 PM   #22
PeteLindsey
LQ Newbie
 
Registered: Aug 2013
Posts: 15

Original Poster
Rep: Reputation: Disabled
Sounds like exactly what I am seeing... My version 2.6.4 which I believe is older than the listed bug version (2.6.7 I am guessing) on that bug report. I am stuck with openfiler, and I am a very LIGHT user of linux... I cannot see a way to update mdadm to a newer version... can you help me with updating this or perhaps there is a work around?
 
Old 08-13-2013, 04:39 PM   #23
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 2,445

Rep: Reputation: Disabled
If you can get your hands on a later version of mdadm, compiled against the same library versions as found in Openfiler, you can just copy it with scp to basically any directory on your system and run it from there.

Another option would be to boot the system from a Live CD, use the mdadm tool on that CD to add /dev/sdb1 to the array, and then reboot back to Openfiler.

Which version of Openfiler are you running?
 
Old 08-13-2013, 04:48 PM   #24
PeteLindsey
LQ Newbie
 
Registered: Aug 2013
Posts: 15

Original Poster
Rep: Reputation: Disabled
the kernel is 2.6.29.6-0.24.smp.gcc3.4.x86.i686 , I believe it is version 2.3, but now that I go looking for the version, I can't seem to find it anywhere that makes sense. Based on the update log, the system updated from 2.2 to 2.3 in december 2012. When I do a "update" it tells me that it has nothing to update.
 
Old 08-13-2013, 04:56 PM   #25
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 2,445

Rep: Reputation: Disabled
The most recent update to version 2.3 was in February 2009.

You should probably consider upgrading to version 2.99, which was released in April 2011. Not much seems to have happened since then.
 
Old 08-13-2013, 04:58 PM   #26
PeteLindsey
LQ Newbie
 
Registered: Aug 2013
Posts: 15

Original Poster
Rep: Reputation: Disabled
well, I am sure that will be ugly, I think I will investigate the option of using the systemrescue option. I really have appreciated all the help, I will post my results as soon as I can.

Regards,
 
  


Reply


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
MDADM Raid 5 Array - OS Drive Failure. Help Urgently Needed. wazz72 Linux - Server 10 06-09-2011 06:40 PM
RAID mdadm cant add disks to array vockleya Linux - Software 4 09-13-2010 05:37 PM
Add disk to raid1 array in imsm container with mdadm (not losing data). 82801ER ICH5R moon300 Linux - General 7 01-06-2010 03:39 PM
Mdadm: reporting 2 drive failures in RAID5 array wolfywolf Linux - Software 3 04-26-2009 11:54 AM
mdadm raid 5 and failing drive doesn't drop out of array elpresidente44 Linux - Server 1 05-24-2008 07:38 PM


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

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