Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

mdadm oddities on my raid 5


  • Please log in to reply
3 replies to this topic

#1 Gilligan8

Gilligan8

  • Members
  • 59 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:11 AM

Posted 21 October 2010 - 11:52 AM

When I run mdadm --detail on my raid 5 everything looks fine except for the last device.

sudo mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90.03
  Creation Time : Fri Sep 19 13:36:00 2008
     Raid Level : raid5
     Array Size : 1465151808 (1397.28 GiB 1500.32 GB)
  Used Dev Size : 488383936 (465.76 GiB 500.11 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Thu Oct 21 11:45:08 2010
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           UUID : 74d12e38:4e365617:337bb8aa:cdc2baf6 (local to host TheSun)
         Events : 0.2737608

    Number   Major   Minor   RaidDevice State
       0       8       17        0      active sync   /dev/sdb1
       1       8       65        1      active sync   /dev/sde1
       2       8       49        2      active sync   /dev/sdd1
       3       8        1        3      active sync

The screen cap isn't truncated... the last device has no block id... it should be /dev/sda1.

Everything is working fine... this just makes me uneasy.

Anyone else ever seen this? Do I need to be concerned?

Thanks,
Gilligan

BC AdBot (Login to Remove)

 


#2 Gilligan8

Gilligan8
  • Topic Starter

  • Members
  • 59 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:11 AM

Posted 23 October 2010 - 12:30 PM

Beuller Beuller?

No opinions on this?

#3 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:06:11 AM

Posted 23 October 2010 - 02:16 PM

Is that drive damaged at all? Does it show up in the hardware/RAID Configuration settings on the RAID Chip?

#4 Gilligan8

Gilligan8
  • Topic Starter

  • Members
  • 59 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:11 AM

Posted 23 October 2010 - 04:42 PM

The array works just fine and all drives are functioning.... I noticed it because another drive had died and I had to replace it.

I haven't looked in the controller's bios but it does show up in fdisk -l




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users