Jump to content
Sign in to follow this  
Falcon

Expanding crashed, Not possible to get system online again.

4 posts in this topic Last Reply

Recommended Posts

I have change the disk 1 and started a rebuild and expand of the disk. During the first minute the log said that it was a lot of read errors from the Parity disk. The parity disk went offline and rebuild and expand stopped.

 

I stopped the server and fixed the loose cable and restarted the server.

 

Now I have a config I can not get fix and get into shape.

 

1. I can not restart the rebuild and expand, because the parity disk is disabled

2. I can not format the disk 1, because the disk is in a rebuild state.

3. I can not change to the old disk 1 because the disk size is smaller 500GB

4. I can not unassigns the disk and start recalculation on parity disk.

 

The disk 1 is an dedicated disk for Crashplan backup, so it is a backup for other machines.

 

It is ok to loose the data on the disk 1, but it would be nice to rebuild the disk. but I think it is to late to save the data, since the other disk has had some writes without the Parity disk being online.

 

Some of the bootlog:

 

Dec 20 19:14:28 Fileserver emhttp: Start array...

Dec 20 19:14:28 Fileserver kernel: mdcmd (73): start STOPPED

Dec 20 19:14:28 Fileserver kernel: unraid: allocating 129220K for 1280 stripes (24 disks)

Dec 20 19:14:28 Fileserver kernel: md1: running, size: 976762552 blocks

Dec 20 19:14:28 Fileserver kernel: md2: running, size: 976762552 blocks

Dec 20 19:14:28 Fileserver kernel: md3: running, size: 976762552 blocks

Dec 20 19:14:28 Fileserver kernel: md4: running, size: 976762552 blocks

Dec 20 19:14:28 Fileserver kernel: md5: running, size: 1953514552 blocks

Dec 20 19:14:28 Fileserver kernel: md6: running, size: 976762552 blocks

Dec 20 19:14:28 Fileserver kernel: md7: running, size: 1953514552 blocks

Dec 20 19:14:28 Fileserver kernel: md8: running, size: 312571192 blocks

Dec 20 19:14:28 Fileserver kernel: md9: running, size: 488386552 blocks

Dec 20 19:14:28 Fileserver kernel: md10: running, size: 1953514552 blocks

Dec 20 19:14:28 Fileserver kernel: md11: running, size: 488386552 blocks

Dec 20 19:14:28 Fileserver kernel: md12: running, size: 2930266532 blocks

Dec 20 19:14:28 Fileserver kernel: md13: running, size: 976762552 blocks

Dec 20 19:14:28 Fileserver kernel: md14: running, size: 2930266532 blocks

Dec 20 19:14:28 Fileserver kernel: md15: running, size: 2930266532 blocks

Dec 20 19:14:28 Fileserver kernel: md16: running, size: 1465138552 blocks

Dec 20 19:14:28 Fileserver kernel: md17: running, size: 976762552 blocks

Dec 20 19:14:28 Fileserver kernel: md18: running, size: 976762552 blocks

Dec 20 19:14:28 Fileserver kernel: md19: running, size: 2930266532 blocks

Dec 20 19:14:28 Fileserver kernel: md20: running, size: 3907018532 blocks

Dec 20 19:14:28 Fileserver kernel: md21: running, size: 488386552 blocks

Dec 20 19:14:28 Fileserver kernel: md22: running, size: 1953514552 blocks

Dec 20 19:14:28 Fileserver kernel: md23: running, size: 976762552 blocks

Dec 20 19:14:28 Fileserver emhttp: shcmd (30): udevadm settle

Dec 20 19:14:28 Fileserver emhttp: Mounting disks...

Dec 20 19:14:28 Fileserver emhttp: shcmd (31): /sbin/btrfs device scan |& logger

Dec 20 19:14:28 Fileserver kernel: Buffer I/O error on dev md1, logical block 244190608, async page read

Dec 20 19:14:28 Fileserver kernel: Buffer I/O error on dev md1, logical block 244190636, async page read

Dec 20 19:14:28 Fileserver kernel: Buffer I/O error on dev md1, logical block 0, async page read

Dec 20 19:14:28 Fileserver kernel: Buffer I/O error on dev md1, logical block 1, async page read

Dec 20 19:14:28 Fileserver kernel: Buffer I/O error on dev md1, logical block 244190637, async page read

Dec 20 19:14:28 Fileserver kernel: Buffer I/O error on dev md1, logical block 244190637, async page read

Dec 20 19:14:28 Fileserver kernel: Buffer I/O error on dev md1, logical block 244190637, async page read

Dec 20 19:14:28 Fileserver kernel: Buffer I/O error on dev md1, logical block 244190637, async page read

Dec 20 19:14:28 Fileserver kernel: Buffer I/O error on dev md1, logical block 244190637, async page read

Dec 20 19:14:28 Fileserver kernel: Buffer I/O error on dev md1, logical block 244190637, async page read

Dec 20 19:14:29 Fileserver logger: Scanning for Btrfs filesystems

Dec 20 19:14:29 Fileserver emhttp: shcmd (32): mkdir -p /mnt/disk1

Dec 20 19:14:29 Fileserver emhttp: shcmd (33): set -o pipefail ; mount -t xfs -o noatime,nodiratime /dev/md1 /mnt/disk1 |& logger

Dec 20 19:14:29 Fileserver kernel: XFS (md1): SB validate failed with error -5.

Dec 20 19:14:29 Fileserver logger: mount: /dev/md1: can't read superblock

Dec 20 19:14:29 Fileserver emhttp: shcmd: shcmd (33): exit status: 32

Dec 20 19:14:29 Fileserver emhttp: mount error: No file system (32)

Dec 20 19:14:29 Fileserver emhttp: shcmd (34): rmdir /mnt/disk1

Dec 20 19:14:29 Fileserver emhttp: shcmd (35): mkdir -p /mnt/disk2

Dec 20 19:14:29 Fileserver emhttp: shcmd (36): set -o pipefail ; mount -t xfs -o noatime,nodiratime /dev/md2 /mnt/disk2 |& logger

Dec 20 19:14:29 Fileserver kernel: md: handle_flush: unit=1 and parity both disabled!

Dec 20 19:14:29 Fileserver kernel: XFS (md2): Mounting V5 Filesystem

Dec 20 19:14:29 Fileserver kernel: XFS (md2): Ending clean mount

Dec 20 19:14:29 Fileserver emhttp: shcmd (37): xfs_growfs /mnt/disk2 |& logger

Dec 20 19:14:29 Fileserver logger: meta-data=/dev/md2              isize=512    agcount=4, agsize=61047660 blks

Dec 20 19:14:29 Fileserver logger:          =                      sectsz=512  attr=2, projid32bit=1

Dec 20 19:14:29 Fileserver logger:          =                      crc=1        finobt=1

Dec 20 19:14:29 Fileserver logger: data    =                      bsize=4096  blocks=244190638, imaxpct=25

Dec 20 19:14:29 Fileserver logger:          =                      sunit=0      swidth=0 blks

Dec 20 19:14:29 Fileserver logger: naming  =version 2              bsize=4096  ascii-ci=0 ftype=1

Dec 20 19:14:29 Fileserver logger: log      =internal              bsize=4096  blocks=119233, version=2

Dec 20 19:14:29 Fileserver logger:          =                      sectsz=512  sunit=0 blks, lazy-count=1

Dec 20 19:14:29 Fileserver logger: realtime =none                  extsz=4096  blocks=0, rtextents=0

Dec 20 19:14:29 Fileserver emhttp: shcmd (38): mkdir -p /mnt/disk3

Dec 20 19:14:29 Fileserver emhttp: shcmd (39): set -o pipefail ; mount -t xfs -o noatime,nodiratime /dev/md3 /mnt/disk3 |& logger

Dec 20 19:14:29 Fileserver kernel: XFS (md3): Mounting V5 Filesystem

Dec 20 19:14:30 Fileserver emhttp: shcmd (40): xfs_growfs /mnt/disk3 |& logger

Dec 20 19:14:30 Fileserver kernel: XFS (md3): Ending clean mount

Unraid.png.8b58771e4fe6d44ec1aa7d1b4b2525de.png

Share this post


Link to post

Tools - New Config with the original disk1. When you do New Config you will have to reassign all your drives. Be very sure you do not assign a data disk to the parity slot. When you start the array parity will be rebuilt, then you will be back where you were before you replaced disk1 and can try it again making sure all your connections are good.

Share this post


Link to post

Tools - New Config with the original disk1. When you do New Config you will have to reassign all your drives. Be very sure you do not assign a data disk to the parity slot. When you start the array parity will be rebuilt, then you will be back where you were before you replaced disk1 and can try it again making sure all your connections are good.

 

Thanks for the help, everything is now in order.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this