I tried the previous beta version and now the latest beta version.  My server is stuck at Mounting Disks, i've let it sit there for a couple hours and it never finishes mounting the disks.  After awhile the web page will timeout and I need to ssh into the server to run the powerdown command.  Attached is the log file.  Does anyone have any hints as to what might be the cause?

 

I also included the complete diagnostics after the powerdown.

 

Thanks

tower-diagnostics-20170615-0925.zip

unraidlog.txt

Thanks for creating a separate topic for this.

The diags look normal, as if from a fresh boot.

The txt file is incomplete.

Please try again.  Start array and wait like 5 min, not hours, then use command line:

 

diagnostics

 

Then post the diags that show up on the flash in the logs directory.

Here is the log after 7 minutes.

tower-diagnostics-20170615-1520.zip

You're running unRAID in a VM correct?  Which hypervisor?  Something is not right with your config.

The server does seem to complete the mount process.  Do you see shares on the network?

I run an Unraid instance in a VM.  I boot from a VHD with bzroot, bzroot-gui, bzimage on, bzmodules & bzfirmware needed to be put on the flash drive.  If I put all the bz files on the VHD it wouldn't mount either.

I have it running on real hardware.  Everything works while running 6.3.5, but when I try to run the beta, that is when the drives fail to mount.

 

The machine is 

G41MT-S2PT

with an Areca RAID controller.

7 minutes ago, robschaar said:

that is when the drives fail to mount.

 

According to the syslog all disks finished mounting, you can use mc (midnight commander) on the console/SSH to confirm, navigate to /mnt and all disks will appear, can't you see the shares on the network?

They do not show up on the network.  The webserver also times out.  It is not reporting to the webserver that it is finishing mounting the drives.  Also none of the dockers load.  

I just updated to the newest beta and tried again.  It does the same thing.  I did ssh into the server and saw the mounts are completing, but I am not able to see the shares on the network and the webservice quits working.  It just stays on showing mounting drives.  I attached the latest diagnostics.

tower-diagnostics-20170619-0851.zip

Still no idea, syslog looks normal to me, maybe redo your flash drive.

Do you have a floppy disk controller attached?  Maybe try detaching it if so.

41 minutes ago, limetech said:

Do you have a floppy disk controller attached?  Maybe try detaching it if so.

Many BIOS have floppy mentioned in several places, make sure you go through all the BIOS setup screens to make sure any floppy references are disabled.

I will try to disable the floppy drive tonight.  I formatted the flash drive and set everything to default.  It still does the same thing.  Attached is the diagnostics file.

tower-diagnostics-20170619-1202.zip

There is one strange thing in the logs, both this and the older one, disks are taking a long time to mount, over 20 seconds each, try the floppy thing to see if it makes a difference.

The motherboard has no floppy support.  I don't really know why it thinks there is one connected.

If it helps, here is what it looks like when it finishes and mounts on 6.3.5

 

 

tower-diagnostics-20170619-2025.zip

OK, so looks like the time your disks take to mount is normal, and with v6.4rc syslog looks normal up to here:

 

Jun 19 08:46:23 Tower emhttpd: shcmd (89): mkdir /mnt/user
Jun 19 08:46:23 Tower emhttpd: shcmd (90): /usr/local/sbin/shfs /mnt/user -disks 1023 2048000000 -o noatime,big_writes,allow_other  -o remember=330
Jun 19 08:46:23 Tower emhttpd: shcmd (92): /usr/local/sbin/update_cron

 

But it doesn't try to start the services, like with v6.3:

 

Jun 19 20:25:33 Tower emhttp: Starting services...

This why there's no docker, etc, as to why this is happening I have no idea.

How have you been installing the -rc releases?  via 'Update plugins' method?

Please plug your usb flash boot device into your PC, delete all the 'bz' files and then copy them from the release zip to the flash device - there should be 5 of them:

bzimage

bzroot

bzmodules

bzfirmware

bzroot-gui

'Eject' flash and see if issue persists.

Just upgraded to 6.4.0-rc19b and having the same problem.

 

Web gui stuck saying "mounting disks", nothing else really works (docker / vms), can't do anything from the web gui (install plugins or change any settings, including using the update OS to go back to 6.3.5 ).

 

diagnostics at the command line hangs...

 

syslog attached.

 

Much obliged for any assistance.

10 minutes ago, YouAreTheOneNeo said:

Just upgraded to 6.4.0-rc19b and having the same problem.

 

Not the same, you're having a kernel oops, try booting in safe mode:

 

Jan  5 13:41:39 UnRaid kernel: BUG: unable to handle kernel NULL pointer dereference at           (null)
Jan  5 13:41:39 UnRaid kernel: IP: isci_task_abort_task+0x18/0x334 [isci]
Jan  5 13:41:39 UnRaid kernel: PGD 0 P4D 0
Jan  5 13:41:39 UnRaid kernel: Oops: 0000 [#1] PREEMPT SMP PTI
Jan  5 13:41:39 UnRaid kernel: Modules linked in: xfs md_mod ipmi_devintf bonding e1000e ptp pps_core ipmi_ssif sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ast kvm ttm i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc drm aesni_intel aes_x86_64 crypto_simd glue_helper cryptd agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops intel_cstate isci intel_uncore libsas i2c_i801 intel_rapl_perf i2c_core ahci libahci nvme scsi_transport_sas nvme_core wmi ipmi_si button [last unloaded: pps_core]
Jan  5 13:41:39 UnRaid kernel: CPU: 0 PID: 1508 Comm: kworker/u64:1 Not tainted 4.14.11-unRAID #1
Jan  5 13:41:39 UnRaid kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./EP2C602, BIOS P1.80 12/09/2013
Jan  5 13:41:39 UnRaid kernel: Workqueue: scsi_tmf_1 scmd_eh_abort_handler
Jan  5 13:41:39 UnRaid kernel: task: ffff88202de71c00 task.stack: ffffc900071c8000
Jan  5 13:41:39 UnRaid kernel: RIP: 0010:isci_task_abort_task+0x18/0x334 [isci]
Jan  5 13:41:39 UnRaid kernel: RSP: 0018:ffffc900071cbce8 EFLAGS: 00010296
Jan  5 13:41:39 UnRaid kernel: RAX: ffffffffa04e4cbb RBX: ffff8810397565a8 RCX: 0000000000000000
Jan  5 13:41:39 UnRaid kernel: RDX: ffff88103f410420 RSI: 0000000000000800 RDI: 0000000000000000
Jan  5 13:41:39 UnRaid kernel: RBP: 0000000000000000 R08: 00000000000001de R09: 0000000000000000
Jan  5 13:41:39 UnRaid kernel: R10: 000000000000000b R11: ffff88202de71cc0 R12: ffff8810398b1800
Jan  5 13:41:39 UnRaid kernel: R13: 0000000000000000 R14: 0000000000000008 R15: 0000000000000000
Jan  5 13:41:39 UnRaid kernel: FS:  0000000000000000(0000) GS:ffff88103fa00000(0000) knlGS:0000000000000000
Jan  5 13:41:39 UnRaid kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan  5 13:41:39 UnRaid kernel: CR2: 0000000000000000 CR3: 0000000001c0a003 CR4: 00000000000606f0
Jan  5 13:41:39 UnRaid kernel: Call Trace:
Jan  5 13:41:39 UnRaid kernel: ? dev_hard_start_xmit+0x8c/0xe3
Jan  5 13:41:39 UnRaid kernel: ? sch_direct_xmit+0xd0/0x165
Jan  5 13:41:39 UnRaid kernel: ? __dev_queue_xmit+0x414/0x427
Jan  5 13:41:39 UnRaid kernel: ? get_nohz_timer_target+0x18/0x8b
Jan  5 13:41:39 UnRaid kernel: ? cpuacct_charge+0x2c/0x6b
Jan  5 13:41:39 UnRaid kernel: ? dequeue_entity+0x49a/0x4bf
Jan  5 13:41:39 UnRaid kernel: ? pick_next_task_fair+0x227/0x3d9
Jan  5 13:41:39 UnRaid kernel: ? put_prev_entity+0x21/0x2d9
Jan  5 13:41:39 UnRaid kernel: sas_eh_abort_handler+0x2a/0x3c [libsas]
Jan  5 13:41:39 UnRaid kernel: scmd_eh_abort_handler+0x35/0x8f
Jan  5 13:41:39 UnRaid kernel: process_one_work+0x146/0x239
Jan  5 13:41:39 UnRaid kernel: ? rescuer_thread+0x258/0x258
Jan  5 13:41:39 UnRaid kernel: worker_thread+0x1c3/0x292
Jan  5 13:41:39 UnRaid kernel: kthread+0x10f/0x117
Jan  5 13:41:39 UnRaid kernel: ? kthread_create_on_node+0x3a/0x3a
Jan  5 13:41:39 UnRaid kernel: ? call_usermodehelper_exec_async+0x113/0x11a
Jan  5 13:41:39 UnRaid kernel: ret_from_fork+0x1f/0x30
Jan  5 13:41:39 UnRaid kernel: Code: e8 5d 41 5c 41 5d c3 b8 05 00 00 00 c3 b8 05 00 00 00 c3 41 57 41 56 41 55 41 54 55 48 89 fd 53 4c 8d 75 08 48 81 ec 68 01 00 00 <48> 8b 07 c7 44 24 10 00 00 00 00 c7 44 24 18 00 00 00 00 48 8b
Jan  5 13:41:39 UnRaid kernel: RIP: isci_task_abort_task+0x18/0x334 [isci] RSP: ffffc900071cbce8
Jan  5 13:41:39 UnRaid kernel: CR2: 0000000000000000
Jan  5 13:41:39 UnRaid kernel: ---[ end trace c7b7723f0c050cf6 ]---

 

The system boots fine in safe mode - excuse my ignorance but what's a kernel oops?

 

I still haven't started the array. I'll need to do a parity check because the only way i could get the system to shutdown was a hard reset, the powerdown script hung, and even the poweroff command hung. didn't know what else to try ¯\_(ツ)_/¯

 

any idea what could be causing the issue?

 

Cheers,

 

PJ

30 minutes ago, YouAreTheOneNeo said:

any idea what could be causing the issue?

If it works in safe mode it's probably a plugin, remove them all and install one by one.