September 24, 20169 yr unRAID OS Version: 6.2 Description: unRAID crashes if starting array with cache device only How to reproduce: start array with a cache device only Expected results: should not be able to start array Actual results: after pressing start webGUI crashes Other information: found by Dimtar on this thread I reproduced this on my test server, relevant syslog snippet: Sep 24 16:19:29 Test kernel: md: unRAID driver 2.6.6 installed Sep 24 16:19:29 Test emhttp: Pro key detected, GUID: 0..A FILE: /boot/config/Pro.key Sep 24 16:19:29 Test emhttp: Device inventory: Sep 24 16:19:29 Test emhttp: shcmd (92): udevadm settle Sep 24 16:19:29 Test emhttp: Kingston_DT_Micro_001A4D5D52A8BC60A915055A-0:0 (sda) 7678048 Sep 24 16:19:29 Test emhttp: Samsung_SSD_950_PRO_256GB_S2GLNCAGB29334T (nvme0n1) 250059064 Sep 24 16:19:29 Test emhttp: TOSHIBA-RD400_563S108ETPEV (nvme1n1) 250059064 Sep 24 16:19:29 Test kernel: mdcmd (1): import 0 Sep 24 16:19:29 Test kernel: mdcmd (2): import 1 Sep 24 16:19:29 Test kernel: mdcmd (3): import 2 Sep 24 16:19:29 Test kernel: mdcmd (4): import 3 Sep 24 16:19:29 Test kernel: mdcmd (5): import 4 Sep 24 16:19:29 Test kernel: mdcmd (6): import 5 Sep 24 16:19:29 Test kernel: mdcmd (7): import 6 Sep 24 16:19:29 Test kernel: mdcmd (: import 7 Sep 24 16:19:29 Test kernel: mdcmd (9): import 8 Sep 24 16:19:29 Test kernel: mdcmd (10): import 9 Sep 24 16:19:29 Test kernel: mdcmd (11): import 10 Sep 24 16:19:29 Test kernel: mdcmd (12): import 11 Sep 24 16:19:29 Test kernel: mdcmd (13): import 12 Sep 24 16:19:29 Test kernel: mdcmd (14): import 13 Sep 24 16:19:29 Test kernel: mdcmd (15): import 14 Sep 24 16:19:29 Test kernel: mdcmd (16): import 15 Sep 24 16:19:29 Test kernel: mdcmd (17): import 16 Sep 24 16:19:29 Test kernel: mdcmd (18): import 17 Sep 24 16:19:29 Test kernel: mdcmd (19): import 18 Sep 24 16:19:29 Test kernel: mdcmd (20): import 19 Sep 24 16:19:29 Test kernel: mdcmd (21): import 20 Sep 24 16:19:29 Test kernel: mdcmd (22): import 21 Sep 24 16:19:29 Test kernel: mdcmd (23): import 22 Sep 24 16:19:29 Test kernel: mdcmd (24): import 23 Sep 24 16:19:29 Test kernel: mdcmd (25): import 24 Sep 24 16:19:29 Test kernel: mdcmd (26): import 25 Sep 24 16:19:29 Test kernel: mdcmd (27): import 26 Sep 24 16:19:29 Test kernel: mdcmd (28): import 27 Sep 24 16:19:29 Test kernel: mdcmd (29): import 28 Sep 24 16:19:29 Test kernel: mdcmd (30): import 29 Sep 24 16:19:29 Test emhttp: import 30 cache device: nvme0n1 Sep 24 16:19:29 Test emhttp: import flash device: sda Sep 24 16:19:32 Test kernel: mdcmd (31): set md_num_stripes 4096 Sep 24 16:19:32 Test kernel: mdcmd (32): set md_sync_window 2048 Sep 24 16:19:32 Test kernel: mdcmd (33): set md_sync_thresh 192 Sep 24 16:19:32 Test kernel: mdcmd (34): set md_write_method Sep 24 16:19:32 Test kernel: mdcmd (35): start STOPPED Sep 24 16:19:32 Test kernel: ------------[ cut here ]------------ Sep 24 16:19:32 Test kernel: kernel BUG at drivers/md/unraid.c:2035! Sep 24 16:19:32 Test kernel: invalid opcode: 0000 [#1] PREEMPT SMP Sep 24 16:19:32 Test kernel: Modules linked in: md_mod igb ptp pps_core x86_pkg_temp_thermal coretemp fbcon bitblit fbcon_rotate fbcon_ccw fbcon_ud fbcon_cw softcursor font ahci kvm_intel kvm ast i2c_algo_bit libahci drm_kms_helper cfbfillrect cfbimgblt cfbcopyarea ttm drm i2c_i801 agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops fb nvme fbdev i2c_core ipmi_si [last unloaded: md_mod] Sep 24 16:19:32 Test kernel: CPU: 0 PID: 11494 Comm: emhttp Not tainted 4.4.19-unRAID #1 Sep 24 16:19:32 Test kernel: Hardware name: Supermicro Super Server/X11SSM-F, BIOS 1.0b 12/29/2015 Sep 24 16:19:32 Test kernel: task: ffff880074190d00 ti: ffff880462ef8000 task.ti: ffff880462ef8000 Sep 24 16:19:32 Test kernel: RIP: 0010:[<ffffffffa044ee23>] [<ffffffffa044ee23>] unraid_run+0x43/0x363 [md_mod] Sep 24 16:19:32 Test kernel: RSP: 0018:ffff880462efbbd8 EFLAGS: 00010246 Sep 24 16:19:32 Test kernel: RAX: ffff8800734ab400 RBX: ffff880462e6c000 RCX: 0000000000000002 Sep 24 16:19:32 Test kernel: RDX: 00000000001e3900 RSI: 00000000001e3900 RDI: ffff8800734ab800 Sep 24 16:19:32 Test kernel: RBP: ffff880462efbc18 R08: 0000000000000050 R09: 0000000000000007 Sep 24 16:19:32 Test kernel: R10: ffffffffa0451058 R11: 0000000000000007 R12: ffffffffa0450fc8 Sep 24 16:19:32 Test kernel: R13: ffff880462e6e850 R14: ffff8800734ab400 R15: ffff880462e6c120 Sep 24 16:19:32 Test kernel: FS: 00002acec9100040(0000) GS:ffff880477800000(0000) knlGS:0000000000000000 Sep 24 16:19:32 Test kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 24 16:19:32 Test kernel: CR2: 0000000000655568 CR3: 00000004500a5000 CR4: 00000000003406f0 Sep 24 16:19:32 Test kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Sep 24 16:19:32 Test kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Sep 24 16:19:32 Test kernel: Stack: Sep 24 16:19:32 Test kernel: ffff880462efbbe0 ffff880462efbc18 ffffffffa044a88a ffff880462e6c000 Sep 24 16:19:32 Test kernel: ffffffffa0450fc8 ffff880462e6e850 ffff880462e6e850 ffff880462e6c120 Sep 24 16:19:32 Test kernel: ffff880462efbe30 ffffffffa044b987 ffff880462efbc60 ffffffff81125340 Sep 24 16:19:32 Test kernel: Call Trace: Sep 24 16:19:32 Test kernel: [<ffffffffa044a88a>] ? get_token+0x4b/0x7f [md_mod] Sep 24 16:19:32 Test kernel: [<ffffffffa044b987>] md_proc_write+0x10c9/0x1648 [md_mod] Sep 24 16:19:32 Test kernel: [<ffffffff81125340>] ? single_open+0x59/0x86 Sep 24 16:19:32 Test kernel: [<ffffffffa0449294>] ? md_proc_open+0x15/0x17 [md_mod] Sep 24 16:19:32 Test kernel: [<ffffffff8114c0ab>] ? proc_reg_open+0xcd/0xe2 Sep 24 16:19:32 Test kernel: [<ffffffff8112228f>] ? mntput_no_expire+0x27/0x176 Sep 24 16:19:32 Test kernel: [<ffffffff81122406>] ? mntput+0x28/0x2a Sep 24 16:19:32 Test kernel: [<ffffffff81111541>] ? path_put+0x19/0x1c Sep 24 16:19:32 Test kernel: [<ffffffff811117a7>] ? terminate_walk+0x52/0x82 Sep 24 16:19:32 Test kernel: [<ffffffff81114faa>] ? path_openat+0xae4/0xc45 Sep 24 16:19:32 Test kernel: [<ffffffff8111607a>] ? do_filp_open+0x85/0x9e Sep 24 16:19:32 Test kernel: [<ffffffff8114bece>] proc_reg_write+0x43/0x62 Sep 24 16:19:32 Test kernel: [<ffffffff8114be8b>] ? proc_reg_poll+0x55/0x55 Sep 24 16:19:32 Test kernel: [<ffffffff81109cfc>] __vfs_write+0x21/0xb9 Sep 24 16:19:32 Test kernel: [<ffffffff81120486>] ? __alloc_fd+0x150/0x160 Sep 24 16:19:32 Test kernel: [<ffffffff8111ff5a>] ? __fget+0x72/0x7e Sep 24 16:19:32 Test kernel: [<ffffffff8107759d>] ? percpu_down_read+0xe/0x37 Sep 24 16:19:32 Test kernel: [<ffffffff8110a2f6>] vfs_write+0xbc/0x160 Sep 24 16:19:32 Test kernel: [<ffffffff8110aa43>] SyS_write+0x49/0x84 Sep 24 16:19:32 Test kernel: [<ffffffff81620a2e>] entry_SYSCALL_64_fastpath+0x12/0x6d Sep 24 16:19:32 Test kernel: Code: 18 48 8b 3d b0 fa 5d e1 e8 38 83 ca e0 48 85 c0 48 89 03 0f 84 e8 02 00 00 48 89 58 08 8b 4b 38 49 89 c6 83 f9 02 89 48 10 7f 02 <0f> 0b 8d 79 fe 31 c0 41 b8 1d 00 00 00 45 31 d2 8d 50 01 39 c7 Sep 24 16:19:32 Test kernel: RIP [<ffffffffa044ee23>] unraid_run+0x43/0x363 [md_mod] Sep 24 16:19:32 Test kernel: RSP <ffff880462efbbd8> Sep 24 16:19:32 Test kernel: ---[ end trace 401d4ef23675d8b5 ]--- Sep 24 16:20:48 Test login[11574]: invalid password for 'UNKNOWN' on '/dev/tty1' Sep 24 16:20:51 Test login[11574]: ROOT LOGIN on '/dev/tty1'
September 24, 20169 yr I might be missing something, but how would you start an array with no disks in the array? the cache disk it not an array drive
September 24, 20169 yr Author I might be missing something, but how would you start an array with no disks in the array? the cache disk it not an array drive That's why you should not be able to start it, and you are in v6.2
September 24, 20169 yr Oh, I read it wrong. I thought you WERE wanting to start array. You are correct it should not even try to start the array if no array disk is configured
Archived
This topic is now archived and is closed to further replies.