· 6 years ago · Apr 26, 2019, 12:50 PM
1shenmue-mint ~ # mdadm --verbose --create --raid-devices=3 --level=raid0 /dev/md0 /dev/sdb /dev/sdc /dev/sdd
2mdadm: chunk size defaults to 512K
3mdadm: /dev/sdb appears to be part of a raid array:
4 level=raid0 devices=3 ctime=Fri Apr 26 13:01:32 2019
5mdadm: partition table exists on /dev/sdb but will be lost or
6 meaningless after creating array
7mdadm: /dev/sdc appears to be part of a raid array:
8 level=raid0 devices=3 ctime=Fri Apr 26 13:01:32 2019
9mdadm: partition table exists on /dev/sdc but will be lost or
10 meaningless after creating array
11mdadm: /dev/sdd appears to be part of a raid array:
12 level=raid0 devices=3 ctime=Fri Apr 26 13:01:32 2019
13mdadm: partition table exists on /dev/sdd but will be lost or
14 meaningless after creating array
15Continue creating array? н
16Continue creating array? (y/n) y
17mdadm: Defaulting to version 1.2 metadata
18mdadm: array /dev/md0 started.
19shenmue-mint ~ # mount /dev/md0 /raid
20mount: wrong fs type, bad option, bad superblock on /dev/md0,
21 missing codepage or helper program, or other error
22
23 In some cases useful info is found in syslog - try
24 dmesg | tail or so.
25shenmue-mint ~ # dmesg | tail
26[10485.745651] perf: interrupt took too long (3148 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
27[10496.597005] blk_update_request: I/O error, dev fd0, sector 0
28[10496.597011] floppy: error -5 while reading block 0
29[10508.864410] blk_update_request: I/O error, dev fd0, sector 0
30[10508.864416] floppy: error -5 while reading block 0
31[10591.739324] sdb: sdb1
32[10592.224035] sdc: sdc1
33[10592.226143] sdc: sdc1
34[10592.698993] sdd: sdd1
35[10592.722793] md0: detected capacity change from 0 to 3000208195584
36shenmue-mint ~ # fsck /dev/md0
37fsck из util-linux 2.27.1
38e2fsck 1.42.13 (17-May-2015)
39ext2fs_open2: Bad magic number in super-block
40fsck.ext2: Superblock invalid, trying backup blocks...
41fsck.ext2: Bad magic number in super-block при попытке открыть /dev/md0
42
43The superблок could not be read or does not describe a valid ext2/ext3/ext4
44ФС. If the уÑтройÑтво is valid and it really contains an ext2/ext3/ext4
45ФС (and not swap or ufs or something else), then the superблок
46is corrupt, and you might try running e2fsck with an alternate superблок:
47 e2fsck -b 8193 <уÑтройÑтво>
48 or
49 e2fsck -b 32768 <уÑтройÑтво>
50
51shenmue-mint ~ # e2fsck -b 32768 /dev/md0
52e2fsck 1.42.13 (17-May-2015)
53e2fsck: Bad magic number in super-block при попытке открыть /dev/md0
54
55The superблок could not be read or does not describe a valid ext2/ext3/ext4
56ФС. If the уÑтройÑтво is valid and it really contains an ext2/ext3/ext4
57ФС (and not swap or ufs or something else), then the superблок
58is corrupt, and you might try running e2fsck with an alternate superблок:
59 e2fsck -b 8193 <уÑтройÑтво>
60 or
61 e2fsck -b 32768 <уÑтройÑтво>
62
63shenmue-mint ~ #