Got a problem with NAS 542 raid 5 volume down

Options
13»

All Replies

  • Axberg
    Axberg Posts: 14  Freshman Member
    Options
    Yes to the first and No to the second question.

    Here are a some part of the dmesg.

     17.231207] sd 1:0:0:0: [sda] Attached SCSI disk
    [   17.237977] UBI error: ubi_read_volume_table: the layout volume was not found
    [   17.239947] sd 3:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB)
    [   17.239955] sd 3:0:0:0: [sdc] 4096-byte physical blocks
    [   17.240107] sd 3:0:0:0: [sdc] Write Protect is off
    [   17.240115] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
    [   17.240179] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [   17.246780]  sdb: sdb1 sdb2 sdb3
    [   17.275269] UBI error: ubi_attach_mtd_dev: failed to attach mtd2, error -22
    [   17.282302] UBI error: ubi_init: cannot attach mtd2

    22.550744] md: bind<sdb1>
    [   22.553795] md: bind<sdc1>
    [   22.556943] md: bind<sda1>
    [   22.563329] bio: create slab <bio-1> at 1
    [   22.567642] md/raid1:md0: active with 3 out of 4 mirrors
    [   22.573053] md0: detected capacity change from 0 to 2045706240
    [   22.604688] md: md1 stopped.
    [   22.614237] md: bind<sda2>
    [   22.617448] md: bind<sdc2>
    [   22.620470] md: bind<sdb2>
    [   22.627298] md/raid1:md1: active with 3 out of 4 mirrors
    [   22.632704] md1: detected capacity change from 0 to 2046754816
    [   22.864462]  md1: unknown partition table
    [   22.916251] Adding 1998780k swap on /dev/md1.  Priority:-1 extents:1 across:1998780k
    [   22.940683]  md0: unknown partition table
    [   23.049808] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
    [   25.296612] PHY: comcerto-0:04 - Link is Up - 1000/Full
    [   25.301883] pfe_eth_adjust_link: PHY: comcerto-0:04, phy->link: 1
    [   26.893824] EXT4-fs (md0): re-mounted. Opts: (null)
    [   26.920670] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem
    [   26.931369] EXT4-fs (loop0): mounted filesystem without journal. Opts: (null)
    [   27.051251] UBI: attaching mtd3 to ubi3
    [   27.124264] UBI: scanning is finished
    [   27.139964] UBI: attached mtd3 (name "config", size 10 MiB) to ubi3
    [   27.146257] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
    [   27.153095] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
    [   27.159831] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
    [   27.166730] UBI: good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
    [   27.172579] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
    [   27.179741] UBI: max/mean erase counter: 11/7, WL threshold: 4096, image sequence number: 506468069
    [   27.188816] UBI: available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 40
    [   27.197916] UBI: background thread "ubi_bgt3d" started, PID 1209
    [   27.336899] UBIFS: mounted UBI device 3, volume 0, name "ubi_config"
    [   27.343277] UBIFS: file system size:   3428352 bytes (3348 KiB, 3 MiB, 27 LEBs)
    [   27.350618] UBIFS: journal size:       1015809 bytes (992 KiB, 0 MiB, 6 LEBs)
    [   27.357779] UBIFS: media format:       w4/r0 (latest is w4/r0)
    [   27.363627] UBIFS: default compressor: lzo
    [   27.367738] UBIFS: reserved for root:  161928 bytes (158 KiB)
    [   27.571525] NTFS driver 2.1.30 [Flags: R/O MODULE].
    [   27.587374] tntfs: module license 'Commercial. For support email ntfs-support@tuxera.com.' taints kernel.
    [   27.597005] Disabling lock debugging due to kernel taint
    [   27.610215] Tuxera NTFS driver 3014.4.29 [Flags: R/W MODULE].
    [   27.629916] PPP generic driver version 2.4.2
    [   27.654186] PPP MPPE Compression module registered
    [   27.679288] PPP Deflate Compression module registered
    [   27.689135] NET: Registered protocol family 24
    [   27.706257] PPP BSD Compression module registered
    [   28.020730] elp_register_ocf: Comcerto 2000 ELP Crypto Offload Engine
    [   28.027173] m86xxx_elp: Registering  key des/3des aes md5 sha1 sha2_256 sha2_384 sha2_512 sha256_hmac null
    [   30.366394] egiga1: no IPv6 routers present
    [   30.626392] egiga0: no IPv6 routers present
    [   39.642350] md: md2 stopped.
    [   39.671165] md: bind<sdc3>
    [   39.674250] md: bind<sdb3>
    [   39.677405] md: bind<sda3>
    [   39.684171] md/raid:md2: device sda3 operational as raid disk 1
    [   39.690133] md/raid:md2: device sdb3 operational as raid disk 3
    [   39.696070] md/raid:md2: device sdc3 operational as raid disk 2
    [   39.703076] md/raid:md2: allocated 4220kB
    [   39.707188] md/raid:md2: raid level 5 active with 3 out of 4 devices, algorithm 2
    [   39.714690] RAID conf printout:
    [   39.714695]  --- level:5 rd:4 wd:3
    [   39.714702]  disk 1, o:1, dev:sda3
    [   39.714708]  disk 2, o:1, dev:sdc3
    [   39.714713]  disk 3, o:1, dev:sdb3
    [   39.714810] md2: detected capacity change from 0 to 11989668593664
    [   39.977748]  md2: unknown partition table
    [   40.073467] ADDRCONF(NETDEV_CHANGE): egiga0: link becomes ready
    [   41.134359] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: usrquota,data=ordered,barrier=1
    [   41.387414] EXT4-fs (dm-0): ext4_check_descriptors: Inode table for group 0 not in group (block 67108904)!
    [   41.397119] EXT4-fs (dm-0): group descriptors corrupted!

  • Mijzelf
    Mijzelf Posts: 2,605  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    <div>[&nbsp; &nbsp;41.387414] EXT4-fs (dm-0): ext4_check_descriptors: Inode table for group 0 not in group (block 67108904)!</div><div>[&nbsp; &nbsp;41.397119] EXT4-fs (dm-0): group descriptors corrupted!</div>
    That is the same error as you had on dm-1, aka /dev/vg_c1b2735e/lv_168e8bf4. So you can rapair it the same way for dm-0, aka /dev/vg_c1b2735e/vg_info_area.

    e2fsck /dev/vg_c1b2735e/vg_info_area
    reboot

  • Axberg
    Axberg Posts: 14  Freshman Member
    Options
    Hi Mijzelf

    It seemed to work, I would very much like to thank you for all the help you have given me, you are simply a superstar
  • TomasMalina
    TomasMalina Posts: 33  Freshman Member
    First Anniversary 10 Comments Friend Collector
    Options

    Hi, I just came to say thank you, I've also had a problem like this, only I didn't actually have a faulty disk at all, nevertheless the logical volumes on my NAS542 were down. Following the steps here helped (after running e2fsck, it took about 5 days to rebuild the raid, but now it's working again). Cheers!

Consumer Product Help Center