March 23, 201610 yr If I try and select 6 as the disk limit before starting my array emhttp crashes and refuses to reload even when trying to manaully run it from the command line using nohup /usr/local/sbin/emhttp & root@Tower:~# tail -10 /var/log/syslog Mar 24 03:58:27 Tower kernel: md: import disk4: [8,96] (sdg) WDC_WD40EFRX-68WT0N0_WD-WCC4E6HFDN53 size: 3907018532 Mar 24 03:58:27 Tower emhttp: Error: cache: SanDisk_SDSSDHP128G_132033402829 already assigned Mar 24 03:58:27 Tower emhttp: import 6 cache device: no device Mar 24 03:58:27 Tower kernel: mdcmd (6): import 5 8,64 125034808 SanDisk_SDSSDHP128G_132033402829 Mar 24 03:58:27 Tower kernel: md: import disk5: [8,64] (sde) SanDisk_SDSSDHP128G_132033402829 size: 125034808 Mar 24 03:58:27 Tower kernel: md: disk5 new disk Mar 24 03:58:27 Tower emhttp: import flash device: sda Mar 24 03:58:27 Tower emhttp: rdevLastIO.5 not found Mar 24 03:58:27 Tower kernel: emhttp[12250]: segfault at 0 ip 00002b8ac5fbd527 sp 00007ffcbfe7b230 error 4 in libc-2.17.so[2b8ac5f82000+1bf000] I'm running UNRAID 6.1.9 I found a thread similar to my issue but it's from 2012 about the old version so I'm not too sure if it's related.
March 23, 201610 yr Community Expert If I try and select 6 as the disk limit before starting my array emhttp crashes and refuses to reload even when trying to manaully run it from the command line using nohup /usr/local/sbin/emhttp & The emhttp process cannot be restarted (and has not been since v5) - getting a segfault is expectred behaviour if you try.
March 23, 201610 yr Author That's a weird design, is you're expected to restart the whole server if the Web Gui goes down? Also I get the segfault BEFORE trying to restart, that's what causes it to crash.
March 26, 201610 yr Author It seems this is a common issue https://lime-technology.com/forum/index.php?topic=46219.0
March 26, 201610 yr Community Expert It seems this is a common issue https://lime-technology.com/forum/index.php?topic=46219.0 I would not say it was a common issue - just that there have been some other similar reports! The fix normally seems to use a different browser. It appears Chrome in particular is likely to upset the GUI - although I have no idea why.
March 26, 201610 yr Author I've found thread after thread of this so it's at least not an isolated incident and seems to go back as far as v4 of the web ui.
Archived
This topic is now archived and is closed to further replies.