Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Solved] Unable to start array with a Parity-Check

Featured Replies

Hi,

 

After a shutdown, added a new HDD my unRaid server and enabled "Intel VT-D Tech" in BIOS it won't start my array. It freezes/restarts when it does a Parity-Check for around 10min.

I ran a Pre-Clear on the new HDD for 1h and that worked.

I can start the array in Maintenance Mode but as soon as I run a Parity-Check it freezes/restarts.

It doesn't matter if I start unRaid in Safe Mode or not.

 

Any advice? 

 

Thank you!

IMG_20170925_210736.jpg

Screenshot_2.jpg

Screenshot_3.jpg

Edited by Muff
edit title

  • Community Expert

Try the Safe Mode option at boot time.  (You need a monitor and keyboard to make this selection.)

  • Author
5 minutes ago, Frank1940 said:

Try the Safe Mode option at boot time.  (You need a monitor and keyboard to make this selection.)

 

Hi,

 

Yes, I did that but it behaved the same.

Right now I've  changed the parity disk with the new HDD (from 4TB to 6TB) and it's reconstructing the array as we speak. It's at 3.2% but I'm now sure if it "broke" now or not.

It sep 25 22:50 and the last entry in the Log was:

Sep 25 22:01:43 Muff kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000048
Sep 25 22:01:43 Muff kernel: IP: [<ffffffff81382a02>] generic_make_request_checks+0x31d/0x358
Sep 25 22:01:43 Muff kernel: PGD 0 
Sep 25 22:01:43 Muff kernel: 
Sep 25 22:01:43 Muff kernel: Oops: 0000 [#3] PREEMPT SMP
Sep 25 22:01:43 Muff kernel: Modules linked in: md_mod bonding e1000e igb ptp pps_core i2c_algo_bit mxm_wmi x86_pkg_temp_thermal coretemp kvm_intel i2c_i801 ahci i2c_smbus kvm i2c_core libahci cdc_acm video wmi backlight [last unloaded: md_mod]
Sep 25 22:01:43 Muff kernel: CPU: 2 PID: 11788 Comm: unraidd Tainted: G D 4.9.30-unRAID #1
Sep 25 22:01:43 Muff kernel: Hardware name: MSI MS-7A58/Z270 XPOWER GAMING TITANIUM (MS-7A58), BIOS 1.30 07/04/2017
Sep 25 22:01:43 Muff kernel: task: ffff88102776a7c0 task.stack: ffffc900083ac000
Sep 25 22:01:43 Muff kernel: RIP: 0010:[<ffffffff81382a02>] [<ffffffff81382a02>] generic_make_request_checks+0x31d/0x358
Sep 25 22:01:43 Muff kernel: RSP: 0000:ffffc900083afcb8 EFLAGS: 00010206
Sep 25 22:01:43 Muff kernel: RAX: 0000000000000008 RBX: ffff880ff805d4d8 RCX: 0000000000000008
Sep 25 22:01:43 Muff kernel: RDX: ffff88102dc297a0 RSI: ffff880ff807e000 RDI: ffff88100b569d40
Sep 25 22:01:43 Muff kernel: RBP: ffffc900083afd00 R08: 000000000000000a R09: 0000000000000002
Sep 25 22:01:43 Muff kernel: R10: ffffc900083afd68 R11: 0000000000002800 R12: ffff880ff805d4d8
Sep 25 22:01:43 Muff kernel: R13: ffff8810146e0000 R14: ffff880ff805d4d8 R15: ffff881025515168
Sep 25 22:01:43 Muff kernel: FS: 0000000000000000(0000) GS:ffff88106ec80000(0000) knlGS:0000000000000000
Sep 25 22:01:43 Muff kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 25 22:01:43 Muff kernel: CR2: 0000000000000048 CR3: 0000000001c09000 CR4: 00000000003406e0
Sep 25 22:01:43 Muff kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 25 22:01:43 Muff kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 25 22:01:43 Muff kernel: Stack:
Sep 25 22:01:43 Muff kernel: ffffffff8137e3e4 ffff880ff805d1f0 0000000000000002 ffff880ff807e000
Sep 25 22:01:43 Muff kernel: ffff880ff805d4d8 0000000000000002 00000000ffffffff ffff880ff805d4d8
Sep 25 22:01:43 Muff kernel: ffff881025515168 ffffc900083afd50 ffffffff81383e03 0000000100000000
Sep 25 22:01:43 Muff kernel: Call Trace:
Sep 25 22:01:43 Muff kernel: [<ffffffff8137e3e4>] ? xor_avx_2+0x1b9/0x1c0
Sep 25 22:01:43 Muff kernel: [<ffffffff81383e03>] generic_make_request+0x28/0x21b
Sep 25 22:01:43 Muff kernel: [<ffffffffa003d68a>] handle_stripe+0x10b9/0x1229 [md_mod]
Sep 25 22:01:43 Muff kernel: [<ffffffffa003d68a>] ? handle_stripe+0x10b9/0x1229 [md_mod]
Sep 25 22:01:43 Muff kernel: [<ffffffff8107409b>] ? put_prev_entity+0x39/0x5f0
Sep 25 22:01:43 Muff kernel: [<ffffffffa003d8a9>] unraidd+0xaf/0xff [md_mod]
Sep 25 22:01:43 Muff kernel: [<ffffffffa0038189>] md_thread+0xbb/0xcf [md_mod]
Sep 25 22:01:43 Muff kernel: [<ffffffffa0038189>] ? md_thread+0xbb/0xcf [md_mod]
Sep 25 22:01:43 Muff kernel: [<ffffffff8107c0fd>] ? wake_up_bit+0x25/0x25
Sep 25 22:01:43 Muff kernel: [<ffffffffa00380ce>] ? md_open+0x31/0x31 [md_mod]
Sep 25 22:01:43 Muff kernel: [<ffffffff81063939>] kthread+0xdb/0xe3
Sep 25 22:01:43 Muff kernel: [<ffffffff8106385e>] ? kthread_park+0x52/0x52
Sep 25 22:01:43 Muff kernel: [<ffffffff8167f785>] ret_from_fork+0x25/0x30
Sep 25 22:01:43 Muff kernel: Code: e4 08 48 0f 44 fb e8 75 6b 04 00 e8 47 80 d0 ff 44 88 f0 83 f0 01 eb 3f b8 a1 ff ff ff e9 9a fd ff ff 49 8b 54 24 08 48 8b 52 08 <48> 8b 52 48 48 c1 fa 09 0f 84 5c fd ff ff 89 c1 48 39 ca 0f 82 
Sep 25 22:01:43 Muff kernel: RIP [<ffffffff81382a02>] generic_make_request_checks+0x31d/0x358
Sep 25 22:01:43 Muff kernel: RSP <ffffc900083afcb8>
Sep 25 22:01:43 Muff kernel: CR2: 0000000000000048
Sep 25 22:01:43 Muff kernel: ---[ end trace b4ba5be2a4aa8a6f ]---

I'm thinking of leaving it under the night.

  • Author

This is what I got in the morning:
IMG_20170926_095036.thumb.jpg.1f5536c1c7ff905b0e981a9a6f843030.jpg

 

I've made a ticket to the unRaid support

Obvious question:
Have you tried DISabling "Intel VT-D Tech"?


 

The whole diagnostic might help but just more of the Syslog you posted if you are unable to get the whole diagnostic.  But first I would try what SnickySnacks suggested first.

  • Author
On 2017-09-27 at 3:50 AM, BobPhoenix said:

The whole diagnostic might help but just more of the Syslog you posted if you are unable to get the whole diagnostic.  But first I would try what SnickySnacks suggested first.

 

On 2017-09-26 at 6:59 PM, SnickySnacks said:

Obvious question:
Have you tried DISabling "Intel VT-D Tech"?


 

 

It seems to have worked...

1, I disabled Intel VT-D

2, Start the array and let it rebuild.

3, Enable Intel VT-D

4, Start the array

 

Really strange...

 

Thank you all for you help!

If the problem is with Intel VT-D, I'd be concerned about keeping it enabled as it may cause other issues later.

The fact that the issue appeared during the rebuild doesn't mean that it's gone away now, just that whatever you're doing now isn't triggering it.


At the very least, I'd keep it in mind if you run into similar issues down the line as it will likely be the culprit.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.