unRAID Server Release 6.0-beta8-x86_64 Available


limetech

Recommended Posts

  • Replies 190
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

I'm not sure this is the best place to post this, but the latest effort is on V6b8, so it might be the best place to bring up this topic again.

 

I have seen posts all throughout the forum about the webgui becoming unresponsive and hanging up.  I have some information that may explain and/or help get out of this situation.  This may or may not be anything that LT can resolve.

 

This may or may to apply, but realize this: unRaid users are an impatient lot in general.  Some operations will make the webGui appear to hang, when in fact it's working.  Pounding on Refresh does not help.  I know everyone likes to pound on Refresh and everyone likes to have instant feedback, that's how you use the internet after all right?  But the webGui is a user interface that happens to use HTTP/HTML and browsers for display.  We are doing our best to make the thing "instantanenous" but this will take some time.

 

Tomm,

 

At the moments I experience the webpage unavailable that also combines with the user0 folder gone.. Could that also be a temporary thing ?

Link to comment

At the moments I experience the webpage unavailable that also combines with the user0 folder gone.. Could that also be a temporary thing ?

 

It is never normal for the webGui to "hang" and for user0 folder to disappear.  Please create a Defect report.

 

Note: there is known bug that will cause user0 to 'disappear'.  If you set up the global share include/exclude masks in such a way that no disks are selected for user shares, and user shares are enabled, then this will result.

 

For example, suppose you have disk1 and disk2.  But you set include mask to "disk3" - this will cause the bug.

Link to comment

I can not pre-formatted. I purchased the disk I added to the system. And I chose the Clear. If there is an option to format it before I'll be happy to explain. So I did all the discs that I have.

Formatting just means creating an empty file system. That is not what clear and preclear do. If you do not preclear a disk then unRAID will have to clear it so it will match parity before it can format it. While it clears the disk the array will be offline for several hours.

 

Most people use the preclear script (and everyone should) to clear and test a disk before adding it to the array. This avoids the long period with the array offline. It also provides a good test of the drive before adding it to the array. You don't want to add a bad disk to the array, and even brand new disks can be bad.

 

You really should use the preclear script. You can get it here.

Link to comment

Another log

 

Sep  8 21:04:38 HomeServer emhttp: import 24 cache device: sdh
Sep  8 21:04:38 HomeServer emhttp: import flash device: sda
Sep  8 21:04:38 HomeServer emhttp: shcmd (88): /usr/local/sbin/emhttp_event driver_loaded
Sep  8 21:04:38 HomeServer emhttp_event: driver_loaded
Sep  8 21:04:44 HomeServer emhttp: clear: disk7
Sep  8 21:04:44 HomeServer emhttp: clear: 1% complete
Sep  8 21:05:43 HomeServer emhttp: clear: 2% complete
Sep  8 21:06:49 HomeServer emhttp: clear: 3% complete
Sep  8 21:07:00 HomeServer kernel: BUG: unable to handle kernel paging request at 000000020000001c
Sep  8 21:07:00 HomeServer kernel: IP: [] find_get_entry+0x37/0x6a
Sep  8 21:07:00 HomeServer kernel: PGD 1a4d98067 PUD 0 
Sep  8 21:07:00 HomeServer kernel: Oops: 0000 [#1] SMP 
Sep  8 21:07:00 HomeServer kernel: Modules linked in: md_mod xor vhost_net vhost tun i2c_i801 ata_piix atl1c mpt2sas raid_class scsi_transport_sas [last unloaded: md_mod]
Sep  8 21:07:00 HomeServer kernel: CPU: 0 PID: 2104 Comm: emhttp Not tainted 3.16.0-unRAID #6
Sep  8 21:07:00 HomeServer kernel: Hardware name: ECS H55H-M/H55H-M, BIOS 080016  09/13/2010
Sep  8 21:07:00 HomeServer kernel: task: ffff8801a4d73f00 ti: ffff880005fb0000 task.ti: ffff880005fb0000
Sep  8 21:07:00 HomeServer kernel: RIP: e030:[]  [] find_get_entry+0x37/0x6a
Sep  8 21:07:00 HomeServer kernel: RSP: e02b:ffff880005fb3c58  EFLAGS: 00010246
Sep  8 21:07:00 HomeServer kernel: RAX: ffff88016a05a048 RBX: 000000000050bf46 RCX: 00000000fffffffa
Sep  8 21:07:00 HomeServer kernel: RDX: ffff88016a05a048 RSI: ffff88016a05a048 RDI: 0000000200000000
Sep  8 21:07:00 HomeServer kernel: RBP: ffff880005fb3c68 R08: ffff88016a059ff0 R09: ffff880005fb3c40
Sep  8 21:07:00 HomeServer kernel: R10: 000000000000000a R11: ffffffff8110359a R12: ffff8801a0cb5280
Sep  8 21:07:00 HomeServer kernel: R13: ffff880005fb3d60 R14: ffff8801a0cb5278 R15: 00000000000000d0
Sep  8 21:07:00 HomeServer kernel: FS:  00002b9d8771e700(0000) GS:ffff8801b2a00000(0000) knlGS:0000000000000000
Sep  8 21:07:00 HomeServer kernel: CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
Sep  8 21:07:00 HomeServer kernel: CR2: 000000020000001c CR3: 00000001a13d7000 CR4: 0000000000002660
Sep  8 21:07:00 HomeServer kernel: Stack:
Sep  8 21:07:00 HomeServer kernel:  000000000000000f 00000000000200d0 ffff880005fb3cb0 ffffffff810a3de0
Sep  8 21:07:00 HomeServer kernel:  ffff880005fb3cc0 000000000050bf46 ffff880005fb3e70 000000050bf46000
Sep  8 21:07:00 HomeServer kernel:  ffff880005fb3d60 0000000000001000 ffff8801a4d73f00 ffff880005fb3cc8
Sep  8 21:07:00 HomeServer kernel: Call Trace:
Sep  8 21:07:00 HomeServer kernel:  [] pagecache_get_page+0x2c/0x14c
Sep  8 21:07:00 HomeServer kernel:  [] grab_cache_page_write_begin+0x2b/0x42
Sep  8 21:07:00 HomeServer kernel:  [] block_write_begin+0x24/0x73
Sep  8 21:07:00 HomeServer kernel:  [] ? I_BDEV+0xd/0xd
Sep  8 21:07:00 HomeServer kernel:  [] blkdev_write_begin+0x1e/0x20
Sep  8 21:07:00 HomeServer kernel:  [] generic_perform_write+0xb4/0x18a
Sep  8 21:07:00 HomeServer kernel:  [] ? file_update_time+0x99/0xad
Sep  8 21:07:00 HomeServer kernel:  [] __generic_file_write_iter+0x25b/0x29b
Sep  8 21:07:00 HomeServer kernel:  [] blkdev_write_iter+0x31/0x9e
Sep  8 21:07:00 HomeServer kernel:  [] ? __fget_light+0x46/0x5b
Sep  8 21:07:00 HomeServer kernel:  [] new_sync_write+0x7b/0x9f
Sep  8 21:07:00 HomeServer kernel:  [] vfs_write+0xb5/0x169
Sep  8 21:07:00 HomeServer kernel:  [] SyS_write+0x42/0x86
Sep  8 21:07:00 HomeServer kernel:  [] system_call_fastpath+0x16/0x1b
Sep  8 21:07:00 HomeServer kernel: Code: 67 08 48 89 de 4c 89 e7 e8 01 0f 23 00 48 85 c0 48 89 c6 74 31 48 8b 38 48 85 ff 74 39 40 f6 c7 03 74 08 40 f6 c7 01 74 2d eb d7 <8b> 57 1c 85 d2 74 d0 44 8d 42 01 89 d0 f0 44 0f b1 47 1c 39 d0 
Sep  8 21:07:00 HomeServer kernel: RIP  [] find_get_entry+0x37/0x6a
Sep  8 21:07:00 HomeServer kernel:  RSP 
Sep  8 21:07:00 HomeServer kernel: CR2: 000000020000001c
Sep  8 21:07:00 HomeServer kernel: ---[ end trace 66d2bbd557c3805c ]---

Link to comment

I can not pre-formatted. I purchased the disk I added to the system. And I chose the Clear. If there is an option to format it before I'll be happy to explain. So I did all the discs that I have.

Formatting just means creating an empty file system. That is not what clear and preclear do. If you do not preclear a disk then unRAID will have to clear it so it will match parity before it can format it. While it clears the disk the array will be offline for several hours.

 

Most people use the preclear script (and everyone should) to clear and test a disk before adding it to the array. This avoids the long period with the array offline. It also provides a good test of the drive before adding it to the array. You don't want to add a bad disk to the array, and even brand new disks can be bad.

 

You really should use the preclear script. You can get it here.

 

Thanks for the information.

Seems complicated - and as you can see my English is not good.

Link to comment

Thanks for the information.

Seems complicated - and as you can see my English is not good.

 

It really isn't. You just need to know what the drive ID is, such as sdf or /dev/sdf, and UNRAID will show you that on the device list of drives outside of the array. It's just the simple measure of typing a line into a telnet window and then waiting for it to complete (up to 24 hours based on drive size).

Link to comment

suggesting he use preclear is not the correct solution here. unRAID is supposed to be able to clear a disk before being added to the array. If it errors out then there is an issue.

 

Diagnose the issue rather than a workaround.

 

I would first do a 8 hour minimum cycle of memtest to ensure the memory/motherboard settings are suitable.

 

The best way to diagnose the issue is to preclear the drive to fully diagnose the quality of the drive.

 

 

Link to comment

suggesting he use preclear is not the correct solution here. unRAID is supposed to be able to clear a disk before being added to the array. If it errors out then there is an issue.

 

Diagnose the issue rather than a workaround.

Totally agree that this should work. However, since the poster is a new user and didn't appear to be aware of this "best practice" it seemed like a good idea to let them know. The cause of this problem could in fact be a bad disk. Probably more likely than an actual issue that belongs in this release thread.
Link to comment

Was Disk 6 a replacement for a disk that was previously 500Gb?

 

The auto-expand of the filesystem on a replacement disk being disabled is detailed in the 1st post of this thread as a known issue in Beta 7 and is not fixed in Beta 8.    I think this issue is expected to be fixed in Beta 9 (but until Beta 9 is actually released we won't know for sure).

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.