Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Sat Nov 18, 2017 3:59 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 3 posts ] 
Author Message
 Post subject: data raid passsed out
PostPosted: Mon May 25, 2015 11:15 am 
Offline
Total Newbie

Joined: Mon May 25, 2015 11:14 am
Posts: 2
Hey there

the topic says it all, i guess. but let me post some more details. The point is: I dont know where to start. For me its sounds, as if something is totally wrong with my device-configuration The missing raid is /dev/md2. And from the output (see below) i guess, this was a RAID Type 0 with the devices /dev/sda and /dev/sda6. You also can see this from the size of those disks - both are 2 TByte.

First i tried to re-assamble with mdadm --assemble --scan -v

Code:
mdadm: looking for devices for /dev/md0
mdadm: cannot open device /dev/md/1: Device or resource busy
mdadm: /dev/md/1 has wrong uuid.
mdadm: cannot open device /dev/md/10: Device or resource busy
mdadm: /dev/md/10 has wrong uuid.
mdadm: cannot open device /dev/md/0: Device or resource busy
mdadm: /dev/md/0 has wrong uuid.
mdadm: cannot open device /dev/sda6: Device or resource busy
mdadm: /dev/sda6 has wrong uuid.
mdadm: cannot open device /dev/sda5: Device or resource busy
mdadm: /dev/sda5 has wrong uuid.
mdadm: no recogniseable superblock on /dev/sda4
mdadm: /dev/sda4 has wrong uuid.
mdadm: no recogniseable superblock on /dev/sda3
mdadm: /dev/sda3 has wrong uuid.
mdadm: cannot open device /dev/sda2: Device or resource busy
mdadm: /dev/sda2 has wrong uuid.
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: /dev/sda1 has wrong uuid.
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: /dev/sda has wrong uuid.
mdadm: no recogniseable superblock on /dev/mtdblock0
mdadm: /dev/mtdblock0 has wrong uuid.
mdadm: looking for devices for /dev/md/1
mdadm: cannot open device /dev/md/1: Device or resource busy
mdadm: /dev/md/1 has wrong uuid.
mdadm: cannot open device /dev/md/10: Device or resource busy
mdadm: /dev/md/10 has wrong uuid.
mdadm: cannot open device /dev/md/0: Device or resource busy
mdadm: /dev/md/0 has wrong uuid.
mdadm: cannot open device /dev/sda6: Device or resource busy
mdadm: /dev/sda6 has wrong uuid.
mdadm: cannot open device /dev/sda5: Device or resource busy
mdadm: /dev/sda5 has wrong uuid.
mdadm: no RAID superblock on /dev/sda4
mdadm: /dev/sda4 has wrong uuid.
mdadm: no RAID superblock on /dev/sda3
mdadm: /dev/sda3 has wrong uuid.
mdadm: cannot open device /dev/sda2: Device or resource busy
mdadm: /dev/sda2 has wrong uuid.
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: /dev/sda1 has wrong uuid.
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: /dev/sda has wrong uuid.
mdadm: no RAID superblock on /dev/mtdblock0
mdadm: /dev/mtdblock0 has wrong uuid.
mdadm: looking for devices for /dev/md/10
mdadm: cannot open device /dev/md/1: Device or resource busy
mdadm: /dev/md/1 has wrong uuid.
mdadm: cannot open device /dev/md/10: Device or resource busy
mdadm: /dev/md/10 has wrong uuid.
mdadm: cannot open device /dev/md/0: Device or resource busy
mdadm: /dev/md/0 has wrong uuid.
mdadm: cannot open device /dev/sda6: Device or resource busy
mdadm: /dev/sda6 has wrong uuid.
mdadm: cannot open device /dev/sda5: Device or resource busy
mdadm: /dev/sda5 has wrong uuid.
mdadm: no RAID superblock on /dev/sda4
mdadm: /dev/sda4 has wrong uuid.
mdadm: no RAID superblock on /dev/sda3
mdadm: /dev/sda3 has wrong uuid.
mdadm: cannot open device /dev/sda2: Device or resource busy
mdadm: /dev/sda2 has wrong uuid.
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: /dev/sda1 has wrong uuid.
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: /dev/sda has wrong uuid.
mdadm: no RAID superblock on /dev/mtdblock0
mdadm: /dev/mtdblock0 has wrong uuid.
mdadm: looking for devices for /dev/md/2
mdadm: cannot open device /dev/md/1: Device or resource busy
mdadm: /dev/md/1 has wrong uuid.
mdadm: cannot open device /dev/md/10: Device or resource busy
mdadm: /dev/md/10 has wrong uuid.
mdadm: cannot open device /dev/md/0: Device or resource busy
mdadm: /dev/md/0 has wrong uuid.
mdadm: cannot open device /dev/sda6: Device or resource busy
mdadm: /dev/sda6 has wrong uuid.
mdadm: cannot open device /dev/sda5: Device or resource busy
mdadm: /dev/sda5 has wrong uuid.
mdadm: no RAID superblock on /dev/sda4
mdadm: /dev/sda4 has wrong uuid.
mdadm: no RAID superblock on /dev/sda3
mdadm: /dev/sda3 has wrong uuid.
mdadm: cannot open device /dev/sda2: Device or resource busy
mdadm: /dev/sda2 has wrong uuid.
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: /dev/sda1 has wrong uuid.
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: /dev/sda has wrong uuid.
mdadm: no RAID superblock on /dev/mtdblock0
mdadm: /dev/mtdblock0 has wrong uuid.



After that I tried to re-create the missing array with
Code:
mdadm --create /dev/md2 --level=0 --raid-devices=2 /dev/sda /dev/sda6


This led to
Code:
mdadm: device /dev/sda not suitable for any style of array


This is what df -h says:

Code:
Filesystem                Size      Used Available Use% Mounted on
/dev/md1                  4.7G      1.0G      3.4G  23% /
udev                     10.0M     96.0k      9.9M   1% /dev
/dev/ram1                15.0M    152.0k     14.9M   1% /mnt/ram
/dev/md0                969.2M     34.4M    934.8M   4% /boot


OK, and this is the output from mdadm --examine ---scan:

Code:
ARRAY /dev/md0 UUID=1429ac05:cbb1977f:cbc1d7a5:4c16e0a4
ARRAY /dev/md/1 metadata=1.2 UUID=361e44d3:7bce6cc5:bf9b9fa2:4ce69378 name=UNINSPECT-EMC36:1
ARRAY /dev/md/10 metadata=1.2 UUID=1bd863a5:6549c88c:f31d19ad:34769ef5 name=UNINSPECT-EMC36:10
ARRAY /dev/md/2 metadata=1.2 UUID=41e67f06:3b93cda0:46ac3bd7:96702dae name=UNINSPECT-EMC36:2

Here we have /proc/mdstat:
Code:
md2 : inactive sda6[1](S)
      1938311476 blocks super 1.2

md1 : active raid1 sda2[1]
      4999156 blocks super 1.2 [2/1] [_U]

md10 : active raid1 sda5[1]
      1000436 blocks super 1.2 [2/1] [_U]

md0 : active raid1 sda1[1]
      1000384 blocks [2/1] [_U]

unused devices: <none>


and now fdisk -l for /dev/sda and /dev/sda6

Code:
Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1      243202  1953514583+ ee EFI GPT
Disk /dev/sda6: 1984.8 GB, 1984832000000 bytes
255 heads, 63 sectors/track, 241308 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sda6 doesn't contain a valid partition table


and mdadm --examine for those devices:

Code:
/dev/sda:
        mdadm: No md superblock detected on /dev/sda.
/dev/sda6:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 41e67f06:3b93cda0:46ac3bd7:96702dae
           Name : UNINSPECT-EMC36:2
  Creation Time : Thu Oct 18 01:43:39 2012
     Raid Level : raid0
   Raid Devices : 2

 Avail Dev Size : 3876622952 (1848.52 GiB 1984.83 GB)
  Used Dev Size : 0
    Data Offset : 2048 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 1dd1c5c5:220d14bf:5b0b1fc5:dbcc3f9c

    Update Time : Thu Oct 18 01:43:39 2012
       Checksum : 5d34dcac - correct
         Events : 0

     Chunk Size : 512K

   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)



This is the part of /var/log/messages for my /dev/sda:
Code:
May 25 10:44:36 WXL kernel: md: unbind<sda6>
May 25 10:44:36 WXL kernel: md: export_rdev(sda6)
May 25 11:00:05 WXL kernel: Kernel command line: console=ttyS0,115200 root=/dev/sda2 rw initrd=0x00800040,12M panic=5 BOOTVER=0.21 mtdparts=nand_mtd:0x1000000(boot),0xfe800000(rootfs),0x800000(reserve)
May 25 11:00:05 WXL kernel: sd 1:0:0:0: [sda] Sector size 0 reported, assuming 512.
May 25 11:00:05 WXL kernel: sd 1:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
May 25 11:00:05 WXL kernel: sd 1:0:0:0: [sda] 0-byte physical blocks
May 25 11:00:05 WXL kernel: sd 1:0:0:0: [sda] Write Protect is off
May 25 11:00:05 WXL kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 25 11:00:05 WXL kernel: sd 1:0:0:0: [sda] Sector size 0 reported, assuming 512.
May 25 11:00:05 WXL kernel:  sda: sda1 sda2 sda3 sda4 sda5 sda6
May 25 11:00:05 WXL kernel: sd 1:0:0:0: [sda] Sector size 0 reported, assuming 512.
May 25 11:00:05 WXL kernel: sd 1:0:0:0: [sda] Attached SCSI disk
May 25 11:00:06 WXL kernel: md: bind<sda1>
May 25 11:00:06 WXL kernel: md: bind<sda5>
May 25 11:00:06 WXL kernel: md: bind<sda2>
May 25 11:00:11 WXL kernel: md: bind<sda6>


Top
   
PostPosted: Tue May 26, 2015 6:57 am 
Offline
Moderator

Joined: Mon Apr 26, 2010 10:24 am
Posts: 2691
Quote:
mdadm --create /dev/md2 --level=0 --raid-devices=2 /dev/sda /dev/sda6


sda is a disk
sda6 is a partition on sda
your sdb is missing


Top
   
PostPosted: Tue May 26, 2015 7:24 am 
Offline
Total Newbie

Joined: Mon May 25, 2015 11:14 am
Posts: 2
But I have to physical drives, 2 TByte each. How can sda6 with 2 TByte be a partition on a disk, that shows 2 TByte for itself assuming, that this sda also should hold another partition with another 2 TByte.

Do I misunderstand the conecpt of devices in Linux?


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 3 posts ] 

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 7 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Powered by phpBB® Forum Software © phpBB Limited