Jump to content

New Initial Parity Rebuild is stuck


MrLinux

Recommended Posts

Hi All. New to unRAID, sorry in advance if I don't have the terminology right.

 

Setup

unRAID v 6.9b25

AMD 3700x, 32GB RAM

I started with a 1.5TB drive and added about 500GB of data on it

My new drive came in (12TB) and got it assigned as a parity drive. I'm still waiting for additional drives to come later.

 

Issue

When getting the new Parity drive setup, it appears to be stuck (only Elapsed time is changing)

Elapsed time:1 day, 1 hour, 10 minutes

Current position:8.25 TB (68.7 %)

Estimated speed:134.7 MB/sec

Estimated finish:7 hours, 44 minutes

 

This hasn't moved for at least 30min (since I noticed it).

 

Any ideas if this is normal and I should just wait or are there other actions I should take? I'm not doing anything on it at the moment. I did start a SpeedDisk benchmark after noticing this issue just to see if the disks are working and it appears to be moving. Also /var/log/syslog doesn't have any activity.

 

Attachments

image.thumb.png.0fbefb9b5b92ba0ba16c1e6d2f4c3145.png

 

image.thumb.png.8a55d76d36b279879cbb1364b2c9d634.png

 

image.thumb.png.15ad51195dae1c7bb37d8ec0890f1240.png

 

 

unraid-diagnostics-20200912-1042.zip

 

 

Edited by MrLinux
Link to comment

It's fine, sync finished successfully:

 

Sep 12 10:10:05 unraid kernel: md: sync done. time=88414sec
Sep 12 10:10:05 unraid kernel: md: recovery thread: exit status: 0

 

Strange the GUI was stuck, you do have something spamming your logs, no idea what these are about:

 

Sep 10 20:47:40 unraid kernel: traps: node[14845] trap invalid opcode ip:560d6ce0270f sp:7ffc308bd0e8 error:0 in node[560d6cdfe000+77b000]
Sep 10 20:47:41 unraid kernel: traps: node[15235] trap invalid opcode ip:5564cbf2c70f sp:7ffccd709a38 error:0 in node[5564cbf28000+77b000]
Sep 10 20:47:42 unraid kernel: traps: node[15587] trap invalid opcode ip:5646aceda70f sp:7ffe15854878 error:0 in node[5646aced6000+77b000]
Sep 10 20:47:44 unraid kernel: traps: node[16105] trap invalid opcode ip:55f17924770f sp:7fff2b8b0ea8 error:0 in node[55f179243000+77b000]

 

 

Link to comment
It's fine, sync finished successfully:

 

Sep 12 10:10:05 unraid kernel: md: sync done. time=88414secSep 12 10:10:05 unraid kernel: md: recovery thread: exit status: 0

 

Strange the GUI was stuck, you do have something spamming your logs, no idea what these are about:

 

 

Sep 10 20:47:40 unraid kernel: traps: node[14845] trap invalid opcode ip:560d6ce0270f sp:7ffc308bd0e8 error:0 in node[560d6cdfe000+77b000]Sep 10 20:47:41 unraid kernel: traps: node[15235] trap invalid opcode ip:5564cbf2c70f sp:7ffccd709a38 error:0 in node[5564cbf28000+77b000]Sep 10 20:47:42 unraid kernel: traps: node[15587] trap invalid opcode ip:5646aceda70f sp:7ffe15854878 error:0 in node[5646aced6000+77b000]Sep 10 20:47:44 unraid kernel: traps: node[16105] trap invalid opcode ip:55f17924770f sp:7fff2b8b0ea8 error:0 in node[55f179243000+77b000]

 

 

 

Thanks for looking into it and confirming it was just a GUI issue. The spam was from a docker container. It was fixed after restarting it.

 

 

Sent from my iPhone using Tapatalk

Link to comment

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.

×
×
  • Create New...