mbryanr

Members
  • Posts

    1294
  • Joined

  • Last visited

Posts posted by mbryanr

  1.  

    GUI freezing is a known issue. Wait long enough and it should return on its own.

    Agreed, although there can be other causes.  Looking through the above syslog, a parity check was started.  Same situation I had.  Eventually the GUI returns.  I was impatient and attempted a emhttp restart only to get the same segfault as expected.

    http://lime-technology.com/forum/index.php?topic=19560.msg188745#msg188745

    I did a full <clean> powerdown, restart and everything was back to normal.  I restarted my monthly parity check...and just let it run until it was complete.

  2. This is weird (Red-->expected, but Blue should be the same size??)

     

     

     

    Jul 17 07:58:32 EpicStorage kernel: mdcmd (1): import 0 8,48 2930266532 ST3000DM001-9YN166_S1F0J0RN

    Jul 17 07:58:32 EpicStorage kernel: md: import disk0: [8,48] (sdd) ST3000DM001-9YN166_S1F0J0RN size: 2930266532

    Jul 17 07:58:32 EpicStorage kernel: mdcmd (2): import 1 8,16 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY2537879

    Jul 17 07:58:32 EpicStorage kernel: md: import disk1: [8,16] (sdb) WDC_WD20EARS-00S8B1_WD-WCAVY2537879 size: 1953514552

    Jul 17 07:58:32 EpicStorage kernel: mdcmd (3): import 2 8,32 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY2480277

    Jul 17 07:58:32 EpicStorage emhttp: shcmd (18): /usr/local/sbin/emhttp_event driver_loaded

    Jul 17 07:58:32 EpicStorage kernel: md: import disk2: [8,32] (sdc) WDC_WD20EARS-00S8B1_WD-WCAVY2480277 size: 1953514552

    Jul 17 07:58:32 EpicStorage kernel: mdcmd (4): import 3 8,64 976762552 SAMSUNG_HD103UJ_S13PJ90QB21621

    Jul 17 07:58:32 EpicStorage kernel: md: import disk3: [8,64] (sde) SAMSUNG_HD103UJ_S13PJ90QB21621 size: 976762552

    Jul 17 07:58:32 EpicStorage kernel: mdcmd (5): import 4 8,80 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZ20193091

    Jul 17 07:58:32 EpicStorage kernel: md: import disk4: [8,80] (sdf) WDC_WD20EARS-00MVWB0_WD-WMAZ20193091 size: 1953514552

    Jul 17 07:58:32 EpicStorage kernel: mdcmd (6): import 5 8,112 2147483612 ST3000DM001-9YN166_S1F0HRT4

    Jul 17 07:58:32 EpicStorage kernel: md: import disk5: [8,112] (sdh) ST3000DM001-9YN166_S1F0HRT4 size: 2147483612

     

    Edit: I can't see the screenshot from work.

  3. I never tested sufficiently <and wasn't aware of it at the time>, but I suspect it was the stop/restart bug that was causing the mover not to use the share initially with 4.7; but the mover would use the new disk without the stop/restart if the top level folder was created.

     

    You may be right that this may be a new bug with v5.  I previously instructed another user to manually create the folder, and the mover started working correctly...

  4. I had a similar experience with a parity check and emhttp hanging (with SimpleFeatures with cache_dir, apcupsd, powerdown, stats, disk health, email notify, active streams, system info, and activity monitor plugins installed)

     

    Other than a syslog, there isn't much to do except reboot. I used to have some success with the killall emhttp command on 4.7, but can only get a segfault (which Tom mentions will happen)

    http://lime-technology.com/forum/index.php?topic=13187.msg182915#msg182915

     

    http://lime-technology.com/forum/index.php?topic=19560.msg188745#msg188745

     

    I don't know under which conditions, other than heavy I/O that will cause emhttp to hang. I don't believe it is directly related to 5RC, as I have had it happen on 4.7..  It does come back eventually.  One of the items that is on Tom's roadmap for..v5.1?

  5. Nice work Influencer. :-)  Hopefully,once these stable versions get widely used, the users can help even more with forum questions and git stuff.... and take some of the workload off you. Again, nice work. Outside of SimpleFeatures, these three were plugins that were widely used. And getting buggy... Giving the whole plugin system a questionable start. Thanks for picking up the coding on these.

     

     

    Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

  6. I didn't find a specific reference to the Areca 1300...but it uses the mvsas driver (same as the Supermicro MV8 that many use) and others are using the Areca 1200 in unRAID

    http://lime-technology.com/forum/index.php?topic=7150.msg69515#msg69515

    Your syslog looks good.

     

    Edit: Don't know what improvements you would get, but looks like it uses another driver as well.  Don't know if it is included in the unRAID kernel

    http://www.areca.com.tw/support/s_linux/nonraid_linux.htm

  7. Looks good as far as compatibility. 

     

    I'd suggest this case for when you catch the bug to expand further...

    http://www.newegg.com/Product/Product.aspx?Item=N82E16811103030

    It has been as low as $45.

     

    I got the Azza 910 for $45, see they have upped their prices since then. :(

    http://www.newegg.com/Product/Product.aspx?Item=N82E16811517007&Tpk=Azza%20Helios

     

    Also one of Raj's recommended boards is $44.99 (including $20 mail in rebate) (only 5 on-board slots..but plenty of expansion slots)

    http://www.newegg.com/Product/Product.aspx?Item=N82E16813135272

    Both will allow up to (3) 5x3 drive cages.  Both include a 4x3 cage. 

    You'll catch UCD and want trayless cages once you get the bug and some extra cash.

    I like your choice in memory, start with a single stick of 4GB...you can always add another.

    Enjoy!

     

     

    Edit:

    Newegg Comparison