Jump to content

Kimovitzh

Members
  • Posts

    51
  • Joined

  • Last visited

Posts posted by Kimovitzh

  1. Hi.

     

    Sorry if this is a obvious question, I'm still learning.

     

    I'm trying to run a RHEL VM on my unRaid server and I've been using the RedHat template but with no luck.

    The problem is that when I start the VM, which seems to start fine, there is no VNC.

    I've used the standard template settings, and tried to change some of them, with no luck.

     

    Logical CPU's assigned: Tried from 2 to 4

    Memory assigned: 8192MB

    Disk size: 30G

    RHEL iso: rhel-server-7.6-x86_64-dvd

     

    Logs is attached.

     

    I hope that this is a noob mistake and that someone can point me to an obvious solution :)

     

    Regards

    Kim.

     

    RHEL_VM_Log.rtf

  2. How do I add more CPU cores? 

     

    I've got 8 cores and want to use 4 of them, so tried typing: <cpus v='4'/>,  but also tried: <cpus v='0,3,4,7'/>, and set the folding power to full, but it never maxes all the cores chosen, only one core is at 100% at any time.

     

     

    Skærmbillede 2017-05-21 kl. 10.07.51.png

    Skærmbillede 2017-05-21 kl. 10.08.05.png

  3. You need to start in maintenance mode and run xfs_repair on disk2.

     

    If array is set to autostart disable it by editing disk.cfg on your flash drive (in the config folder):

     

    change startArray="yes" to "no"

     

    Then:

     

    https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS

     

    This corruption is not detect on v6.1 because it uses a older xfs_repair.

     

    Some days passed by and now im in the process of a clean install, of my unpaid server. But if it happens again I'll follow you'r post.

    Thanks for the comment!

  4. Hi.

     

    I might be missing something here.

    But after update to 6.2 i also updated my ownCloud docker, when i was done updating the ownCloud docker, ownCloud became unresponsive so i thought a reboot of the server might help.

    But after the reboot i can't reach shares or the web GUI, but i can ssh into it. 

     

    Any suggestions?

     

    Regards - Kim

  5. Try FAT instead? - can try it tomorrow (it's 1.51 in the morning here  ;D)

     

    Can you relax the ram timings in the BIOS? - i'll look in to it.

     

    Have you run the 24hour memtest yet? - did it the first day and was the first on my to do.

     

    When you remove some of the ram and it "works" are you always removing the same sticks? - nope, tried almost every one of them.

  6. Something is up with you flash drive. Run chkdsk on it in a windows PC or try another.

     

    Just did it, it came back saying: Windows has checked the file system and found no problems.

    It's a completely new flashdisk, but again unRAID is doing some weird stuff when i run *8*8GB - see attachment (uptime 5mins).

    58aad7dd5ff23_Skrmbillede_2016-03-14_kl._22_53_25.png.184d6df940550c0fbd3a2581e076b30d.png

  7. What happens with these numbers is you ask for the size, and it is given in some units that may be 1024 or may be 1000, and then to make the number have fewer digits, you divide it by 1024 or 1000 and so you can wind up with a lot of different answers that all mean the same thing.

     

    Don't know what to suggest about your actual RAM hardware issue other than what Frank1940 has already said. Is your BIOS set to the default settings?

     

    BIOS is set to default, and when i boot after plugging in the ram's it recognize all of them, tried a windows install and it also works fine there, for some reason unRAID dosen't like it though.

     

    re-inserted the 8*8GB ram system boots all is fine, boots in to unRAID - and this time everything looks good. So did the diagnostics and stopped the array to shut down aaaand it's spazzing, can't shutdown, can't SSH in to it, can't do anything, did a diagnostics and it downloaded, tried again and it just hangs in the download.

     

    Don't know if the diagnostics attached will do any help, but here they are.

    tower-diagnostics-20160315-0044-ARRAY-OFF.zip

    tower-diagnostics-20160315-0043-ARRAY-ON.zip

  8. I agree with BRiT on that....

     

    On the 64GB = 65536 MB. part? I agree that 65536MB is refferd to 64GB got confused with the google conversion - see attached photo.

    But what about the Dynamix System Info that shows 66560 MB ram is installed? And what about the Not Specified = 1024 kB, Unknown part in Memory?

     

    Pointing out the obvious dosen't help, 64GB is 64GB, but some parts of the system is showing more than 64GB, it shows 66.56GB.

     

    So, what going on? I'm new at unRAID so again - the diagnostics is the diagnostics under tools in the GUI then?

    58aad7dd52839_Skrmbillede_2016-03-15_kl._00_16_59.png.58c519787358da1b3957ef449b3db177.png

  9. Units.

    Conversions.

    Learn them.

     

    wow rly? So my problem is that i did't calculate it with the kibibyte system? Well ok, i must tell my server that it's the problem, sure it will fix it right away!

     

    Ya,RLY!

     

    Your problem has nothing to do with the fact that 64GB = 65536 MB.

     

    Your problem is entirely something other than the basic scientific computing facts.

     

    So what about the 66560 MB installed ram then?

  10. I'm not sure what the original problem is. 

     

    Unless you post some diagnostics nobody can help.

     

    The symptoms aren't always the same, but sure i can post it, just from the diagnostics under tools right?

  11. SO. Back to "topic".

     

    In the Dynamix System Info it shows: 66560 MB installed, and 128GB as max (with the riser card that i don't have installed)

    Not Specified = 8192 MB, 667 MHz

    Not Specified = 8192 MB, 667 MHz

    Not Specified = 8192 MB, 667 MHz

    Not Specified = 8192 MB, 667 MHz

    Not Specified = 8192 MB, 667 MHz

    Not Specified = 8192 MB, 667 MHz

    Not Specified = 8192 MB, 667 MHz

    Not Specified = 8192 MB, 667 MHz

    Not Specified = 1024 kB, Unknown

     

    on the dashboard it says 65,536 MB (max. 64 GB).

     

    Any clue on why that is?

    Also, as i now running full 8*8GB Docker and VMs and more is not working, but replacing anyone of the 8 men sticks with a <8GB ram fixes this.

     

     

     

    58aad7dd43b96_Skrmbillede_2016-03-14_kl._22_49_02.png.c9b2aba1a36354a405b6b3963045205b.png

    58aad7dd47e54_Skrmbillede_2016-03-14_kl._22_48_39.png.29f65d1b2b9e93e49df5b7f1fcec65a5.png

  12. Units.

    Conversions.

    Learn them.

     

    wow rly? So my problem is that i did't calculate it with the kibibyte system? Well ok, i must tell my server that it's the problem, sure it will fix it right away!

     

     

  13. Because  '65,xxx'  is exactly 64K defined as a decimal number ---  which is 64  x 1024 = 65536 (K is defined as 1024 --- 2^10) 

     

    I think you probably need to run memtst which you can find as an option during the unRAID boot process.  Since you have 64 of RAM, you should run it for 24 hours minimum.

     

    Did you get RAM recommended  by the MB manufacturer?  Are all of the memory chips from the same manufacturer?  I have heard that as you install more and more memory strips on a MB, problems often surface with timing and other memory related issues.  You may have been bitten by one of them.

     

    They are all the same, 8GB 2Rx4 PC2-5300F-555-11-D0 ECC ram, from HP these ram are the original and recommended ram for this HP workstation.

    It dosen't matter witch one i pull out, just as long as the installed memory is less than the 65xxx mark, right now it's been stabel with 6*8GB + 2*2GB ( 2GB 2Rx4 PC2-5300F-555-11-D0 )

     

    I did run the Memtest that followed with unRAID the first day, with no errors.

  14. So a couple of days ago i received my RAM upgrade, 64GB of joy I installed it an went on doing other stuff.

    yesterday when i finally got the time to play with my unRAID server i saw it behaving weird, and over the last 24+ hours it has been reformatted, had new usb drive installed and so on and still - very unstable and weird behavior.

    Today i realized that on the "dashboard" in the GUI it says MAX 64GB Ram and it got 65,xxx installed - WT* - it got 8*8GB ram.

    So uncliped 2*8GB ram and ... it seems to run fine now.

     

    So what's going on? 65GB ram on 8*8GB ram sticks? And is it why unRAID is spazzing out?

     

    Server is HP xw8600 supports 8*8GB ram or 16*8GB ram with an riser.

  15. Oh wow.

     

    So tried a brand NEW SanDisk Cruzer Fit, bought only because it was recommended from LimeTech, and i get - Flash GUID: Error - contact support.

     

    It's just not my day, or maybe unRAID is just not for me  :'(

     

    Support is contacted.

     

    EDIT:

    Tried the Kingston USB that i've been running since the start of the trial period, reformatted and unRAID reinstalled all on a other mac, and it seems to work now (6.2 beta)

  16. Reformattet all the discs and the usb drive i'm trying the 6.2beta instead, only problem there is that docker and VMs are not working ..

     

    Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 48

    Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/classes/libvirt_helpers.php on line 375

    Those files are included as part of the download so it seems strange that they might be missing?    Have you tried looking at /boot/config to see if they are there?  If not then something is wrong with the way the USB stick was created so that it has not been mounted correctly.

     

    Tried to do fresh installs multiple times, and even though reboot worked the docker will not start. But it's also beta, so going to give 6.19 a try again. :)

  17. So got errors with the reg-key (i'm on trial), and when i tried to re-enter the trial key it came up with error 1 - what ever that is.

    Also, docker dosen't work, no mather how many fresh installs i tried at the end it came up with "image missing in /mnt/user/system/docker".

     

    So going back to the stable 6.19 to test my trial period, 6.2 looks promising so can't wait for it to go stable.

×
×
  • Create New...