Welcome! Log In Create A New Profile

Advanced

maybe a raid got corrupted?

Posted by Carlo 
maybe a raid got corrupted?
December 08, 2019 09:32AM
hi all
i've just finished formatting my nsa box, but i can't access the 2nd hard disk:
before it was accessible on /srv/devfoofoofoo/

now this is all i can master:

FDISK
Disk /dev/mtdblock0: 1 MiB, 1048576 bytes, 2048 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 /dev/mtdblock1: 512 KiB, 524288 bytes, 1024 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 /dev/mtdblock2: 512 KiB, 524288 bytes, 1024 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 /dev/mtdblock3: 512 KiB, 524288 bytes, 1024 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 /dev/mtdblock4: 10 MiB, 10485760 bytes, 20480 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 /dev/mtdblock6: 47.8 MiB, 50069504 bytes, 97792 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 /dev/mtdblock7: 10 MiB, 10485760 bytes, 20480 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 /dev/mtdblock8: 47.8 MiB, 50069504 bytes, 97792 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 /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Disk model: WDC WD3200KS-00P
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd632e2ad

Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1        2048 625141759 625139712 298.1G 83 Linux


Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EFRX-68E
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D1070018-0D36-4566-AF9E-C1DC8C69E518

Device      Start        End    Sectors  Size Type
/dev/sdb1    2048     999423     997376  487M Linux swap
/dev/sdb2  999424 5860532223 5859532800  2.7T Microsoft basic data


Disk /dev/md0: 2.7 TiB, 3000079745024 bytes, 5859530752 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

LSBLK
root@openmediavault:~# lsblk
NAME      MAJ:MIN RM   SIZE RO TYPE   MOUNTPOINT
sda         8:0    0 298.1G  0 disk   
└─sda1      8:1    0 298.1G  0 part   /
sdb         8:16   0   2.7T  0 disk   
├─sdb1      8:17   0   487M  0 part   /srv/dev-disk-by-id-ata-WDC_WD30EFRX-68EUZ
└─sdb2      8:18   0   2.7T  0 part   
  └─md0     9:0    0   2.7T  0 linear 
mtdblock0  31:0    0     1M  0 disk   
mtdblock1  31:1    0   512K  0 disk   
mtdblock2  31:2    0   512K  0 disk   
mtdblock3  31:3    0   512K  0 disk   
mtdblock4  31:4    0    10M  0 disk   
mtdblock5  31:5    0    10M  0 disk   
mtdblock6  31:6    0  47.8M  0 disk   
mtdblock7  31:7    0    10M  0 disk   
mtdblock8  31:8    0  47.8M  0 disk

cat /proc/mdstat
cat /proc/mdstat 
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] 
md0 : active linear sdb2[0]
      2929765376 blocks super 1.2 0k rounding

MDADM
mdadm --examine /dev/sdb0
mdadm: cannot open /dev/sdb0: No such file or director

mdadm --examine /dev/sdb1
mdadm: No md superblock detected on /dev/sdb1.

mdadm --examine /dev/sdb2
/dev/sdb2:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : ae0b0151:4a62050e:e73ef040:35ee8f4e
           Name : NSA325-v2:0
  Creation Time : Thu Jul 23 00:53:39 2015
     Raid Level : linear
   Raid Devices : 1

 Avail Dev Size : 5859530752 (2794.04 GiB 3000.08 GB)
  Used Dev Size : 0
    Data Offset : 2048 sectors
   Super Offset : 8 sectors
   Unused Space : before=1968 sectors, after=0 sectors
          State : clean
    Device UUID : 3eea33c8:e21226cb:66ec754c:06b06634

    Update Time : Thu Jul 23 00:53:39 2015
       Checksum : 5e28e2e5 - correct
         Events : 0

       Rounding : 0K

   Device Role : Active device 0
   Array State : A ('A' == active, '.' == missing, 'R' == replacing)

MOUNT
mount /dev/sdb2 /mnt
mount: /mnt: unknown filesystem type 'linux_raid_member'.
root@openmediavault:/#

i have no idea what swap is doing on /dev/sdb1
i have no idea why /dev/sdb2 is called linux raid member and microsoft basic data at the very same time

does anyone know whether there's an almost painless way to mount my /dev/sdb?



Edited 1 time(s). Last edit at 12/14/2019 11:52AM by Carlo.
Re: maybe a raid got corrupted?
December 25, 2019 02:41AM
I am only guessing here, did you have raid set up before you set up your nsa box?
raid usually has 2 equal drives set up. mine has 2- 5tb drives on a pogoplug but it all kinda works the same for this purpose.


first you might try:
nano /etc/fstab
add:
/dev/md0                                           /mnt      auto   rw,relatime,data=ordered       0      0
save then

mount /dev/md0 /mnt

you should at least get to your data.
let us know how it goes:)

learning is living! Echowarrior108



device pogoplug-pro v3

Debian GNU/Linux bullseye/sid \n \l
Linux version 4.14.180-oxnas-tld-1 (root@tldDebian) (gcc version 8.3.0 (Debian 8.3.0-6) ) #1 SMP PREEMPT Fri Nov 15 04:12:45 PST 2019
Re: maybe a raid got corrupted?
December 25, 2019 05:59AM
Oh, mounting md0 works

No idea why a raid is there, besides its involving just one partition..
Can I disassemble a raid without formatting?
Re: maybe a raid got corrupted?
December 25, 2019 03:46PM
The best thing you could do at this point is find a way to mount and back up all the data to a separate drive before attempting to remove raid configuration.I am no expert on raid other than having installed it but from what I read it can be taken out but most every forum insists on creating a backup first. more to come as its Christmas:) Merry Christmas!

learning is living! Echowarrior108



device pogoplug-pro v3

Debian GNU/Linux bullseye/sid \n \l
Linux version 4.14.180-oxnas-tld-1 (root@tldDebian) (gcc version 8.3.0 (Debian 8.3.0-6) ) #1 SMP PREEMPT Fri Nov 15 04:12:45 PST 2019
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: