I have the NSA 325 V2 and placed raid1 on disk1 while disk2 had not yet a volume

1235

All Replies

  • Mijzelf
    Mijzelf Posts: 2,816  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    And what is the output of e2fsck?
  • Carlusha99
    Carlusha99 Posts: 39  Freshman Member
    Mijzelf:

     # e2fsck.new -f /dev/sdc
    e2fsck 1.41.14 (22-Dec-2010)
    e2fsck.new: Superblock invalid, trying backup blocks...
    e2fsck.new: Bad magic number in super-block while trying to open /dev/sdc

    The superblock could not be read or does not describe a correct ext2
    filesystem.  If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>

     e2fsck.new -b 8193 /dev/sdc
    e2fsck 1.41.14 (22-Dec-2010)
    e2fsck.new: Bad magic number in super-block while trying to open /dev/sdc

    The superblock could not be read or does not describe a correct ext2
    filesystem.  If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>




  • Mijzelf
    Mijzelf Posts: 2,816  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    Ok. So e2fsck thinks there is no ext filesystem starting at zero. So let's try to assemble the array, and e2fsck that.
    <div>mdadm --assemble /dev/md3 /dev/sdc --run</div><div>e2fsck.net -f /dev/md3</div>
    (BTW, the difference between this array and the original one is that this one has plenty of room after the filesystem)
  • Carlusha99
    Carlusha99 Posts: 39  Freshman Member
    ~ # mdadm --assemble /dev/md3 /dev/sdc -- rune2fsck.net -f /dev/md3
    mdadm: /dev/md3 has been started with 1 drive (out of 2).



  • Mijzelf
    Mijzelf Posts: 2,816  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    edited June 2019
    Oops. sorry, this stupid forum glued my two command together. It was
    mdadm --assemble /dev/md3 /dev/sdc --run<br>e2fsck.new -f /dev/md3
    apparently mdadm wasn't upset about the extra arguments, according to it's output. So time for the 2nd command.
    If that succeeds you can mount the disk
    <div>mkdir /mnt/mountpoint</div><div><br></div><div>mount /dev/md3 /mnt/mountpoint</div>

  • Carlusha99
    Carlusha99 Posts: 39  Freshman Member
    ~ # mkdir /mnt/mountpoint
    ~ # mount /dev/md3 /mnt/mountpoint
    mount: wrong fs type, bad option, bad superblock on /dev/md3,
           missing codepage or helper program, or other error
           In some cases useful info is found in syslog - try
           dmesg | tail  or so


  • Carlusha99
    Carlusha99 Posts: 39  Freshman Member
    Mijzelf: after the assemble command this is the picture in the NAS. (see attachment)
    So maybe i should restart the NAS to get back the situation before the assembling.

  • Mijzelf
    Mijzelf Posts: 2,816  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    Did you run e2fsck on md3?

    About that extra disk in the GUI, I wouldn't bother. The GUI is not designed to show 3 internal disks. And I think this thing is assumed internal because it's an assembled raid array.
    Have you checked if the firmware already mounted md3?
    cat /proc/mounts

  • Carlusha99
    Carlusha99 Posts: 39  Freshman Member
    Mijzelf: This is the result:

    ~ # cat /proc/mounts
    rootfs / rootfs rw 0 0
    /proc /proc proc rw,relatime 0 0
    /sys /sys sysfs rw,relatime 0 0
    none /proc/bus/usb usbfs rw,relatime 0 0
    devpts /dev/pts devpts rw,relatime,mode=600 0 0
    /dev/mtdblock8 /zyxel/mnt/nand yaffs2 ro,relatime 0 0
    /dev/sda1 /zyxel/mnt/sysdisk ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /ram_bin ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /usr ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /lib/security ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /lib/modules ext2 ro,relatime,errors=continue 0 0
    /dev/ram0 /tmp/tmpfs tmpfs rw,relatime,size=5120k 0 0
    /dev/ram0 /usr/local/etc tmpfs rw,relatime,size=5120k 0 0
    /dev/ram0 /usr/local/var tmpfs rw,relatime,size=5120k 0 0
    /dev/mtdblock4 /etc/zyxel yaffs2 rw,relatime 0 0
    /dev/md1 /i-data/3cc8587e ext4 rw,noatime,barrier=0,data=writeback,usrquota 0 0
    /dev/md1 /usr/local/apache/web_framework/data/cache ext4 rw,noatime,barrier=0,
    data=writeback,usrquota 0 0
    /dev/mtdblock4 /usr/local/apache/web_framework/data/config yaffs2 rw,relatime 0                                 0
    /dev/md1 /usr/local/apache/htdocs/adv,/res/imdb_poster ext4 rw,noatime,barrier=0,                            ,data=writeback,usrquota 0 0
    /dev/md1 /usr/local/zy-pkgs ext4 rw,noatime,barrier=0,data=writeback,usrquota 0                                 0
    /dev/md1 /etc/zyxel/zy-pkgs ext4 rw,noatime,barrier=0,data=writeback,usrquota 0                                 0
    /dev/md1 /usr/local/apache/htdocs/adv,/pkg ext4 rw,noatime,barrier=0,data=writeb                               ack,usrquota 0 0

    I can't see a md3
  • Carlusha99
    Carlusha99 Posts: 39  Freshman Member
    Mijzelf:

    I have done e2fsck on /dev/md3
    ~ # e2fsck.new /dev/md3
    e2fsck 1.41.14 (22-Dec-2010)
    The filesystem size (according to the superblock) is 244061232 blocks
    The physical size of the device is 244061198 blocks
    Either the superblock or the partition table is likely to be corrupt!
    Abort<y>? no

    /dev/md3 contains a file system with errors, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    /dev/md3: 93128/61022208 files (6.8% non-contiguous), 141480464/244061232 blocks

    ~ # mkdir /mnt/mountpoint
    mkdir: can't create directory '/mnt/mountpoint': File exists
    ~ # mount /dev/md3 /mnt/mountpoint
    mount: wrong fs type, bad option, bad superblock on /dev/md3,
           missing codepage or helper program, or other error
           In some cases useful info is found in syslog - try
           dmesg | tail  or so



Categories

Consumer Product Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）