[quote=“Dubinator;2309”]Hi Guys, Having issue with booting. see below
After this black screen nothing happening, any ideas?
Thanks
ребята, проблема с загрузкой. Смотри ниже
После этого черноый экранн. ничего не происходит, помогите!?
[/quote]
В ФАКе описано. Монитор подключили к встроенной видяхе. После старта Х-ов изображение выводится на другую видеокарту. Надо монитор подключать к карте, воткнутой в первый х16 порт.
No joy here. First tried the dd command, seemed to work fine. But the GAMING 7 mobo only sees one boot option - the UEFI partition. There is no #2.
Attempt #2, reloaded the zip, tried the dd command with bs=1024. Same result.
So I installed the HDD RAW COPY tool on a windoze box, downloaded and unzipped again. Ran the tool. All steps completed normally. EJECTED it, tried to boot the mining rig- same exact problem, it sees one partition, the EUFI.
I might try other imaging tools but I suspect since dd and HDD RAW IMAGER have identical results, no matter what I try, all this mobo will see is the UEFI.
I don’t see the legacy settings you were describing, but I don’t think they are an issue since it sees the USB stick just fine. It only ever sees the one partition however.
(From myself) “No joy here. First tried the dd command, seemed to work fine. But the GAMING 7 mobo only sees one boot option - the UEFI partition. There is no #2.”
To assist others who might have this issue- the Gigabyte GAMING mobo buried the CSM option under “Windows 10 Options”. Which seems like a poor choice, since I needed acces to that, to allow UBUNTU to boot? They should have had ENABLE CSM and UEFI options at the BOOT MENU level, not buried under windows 10 options. Why would someone trying to boot UBUNTU look under there? Goofballs.
Anyhow, now there is some joy. My HIVE is buzzing. It’s at the RIG ID prompt. Things are looking much better,
I only hope I don’t have to monkey with the bios every time I want to switch from ETHOS to HIVE?
мать Asrock H110 Pro BTC+ после ребута не грузитсяhttp://forum.hiveos.farm/uploads/editor/dg/we9ba0fc9vfz.jpg
грузится с 5 раза
Okej guys i have problem after hive its going to black screen. MotherBoard is GA-H110-D3A. I try boot from usb&ssd, Try every grapich too see screen, try to get on vnc, but nothing. I try this too:
Read this https://www.gigabyte.com/microsite/462/mining.html
and execute steps 1,3-6 as wrote at link and don’t execute (or reverse as wrote) step 2
When i try to boot from internal grapich then it stucks after yellow screen, when it say that i need to use external grapich not internal on motherboard…
Grapich cards are: 570 4gb sapphire elpida
Got a Biostar TB250 12 GPU board with 12 106-100 Gpu.
For some reason the OS will not really boot . Boots to the emergency mode.
Any solutions for that ?
@Dalis
Try to download and install 0.5-32 image with subsequent updating to the latest.
I’m guess maybe some issue with linux kernel (4.13 in new image and 4.10 on previous 0.5.xx HiveOS releases ) or something else …
Everything is working initially when booting from USB, but after hitting the re-boot button from the hiveos.farm online panel, my USB becomes so corrupt or something that bios doesn’t even detect a USB installed and the machine restarts to the BIOS screen.
So, I’d love to try and put this on an SSD, which I have, the only problem is that it gets stuck in emergency mode. Is this same problem @Dalis was having? Perhaps I should try an older image on the SSD like @HaloGenius suggested, but not sure if it’s exact same problem.
FYI, I’ve flashed the same hiveOS image that works on USB, onto my SSD multiple times, with multiple utility programs and always get the exact same result, boots into emergency mode.
For what it’s worth, here are a couple photos. The first is the screen it gets stuck on, the second is I figured out some commands and found the only time I see errors listed in the logs.https://forum.hiveos.farm/uploads/editor/6k/fxli0ek7eqk0.jpg
https://forum.hiveos.farm/uploads/editor/y4/2yrwcur5g12a.jpg
Thanks for any help you guys can give me.
@flatlander84
Yes it’s seems problem like Dalis has.
I’m noticed users has some unexplored problem with new flashed image v0.5-45
Thanks again for the response @HaloGenius. I’ll try the older version when I get home later and report back here.
Indeed, @HaloGenius, that was the problem and the solution. It was solved by putting the image of the previous OS version onto the SSD and then it worked like a champ.
Hopefully this helps some other users too. Thanks again for the help!
What is the problem?
hello
I have a problem,
I try to install but my pc can not run img file? what can i do ?
how can i resolve this problem as i want to use but i cant i try 3 diferent burner program
Two different problems, I don’t want to spam both sections, so mods if you must, please delete my other thread:
Problem 1:
I used the built in flash bios function of hiveos to flash an MSI rx570. It failed to flash the bios I selected, but once I checked the “overwrite security” check box it flashed successfully.
It asked me to reboot, I did, and now the miner hangs on the intro hive screen. “a start job is running for HiveOS” ~27s.
before that; drm:amdgput_device_init [amdgpu]] *error hw_init of IP block <gfx_v8_)> failed -22
Problem 2:
4GB rx560 and 4GB 1050ti give a not enough GPU memory in ETH+DCR Claymore. I believe this started happening after I updated to 0.5-.51 today. Is there a way to roll back OS?
Any ideas?
I’ve flashed the iso to a usb, but no mater what the boot settings are in the bios hiveOS will not boot
5.51 only boots into bios
5.32 boots to blank screen with only a caret
strange… it works when I wrote the .img with startup writer in ubuntu but not when I wrote with disks or with dd from the cl
The Problem is that HiveOS shutdown is a simple shutdown
and does not really looking for if services are finished and
write their data back. So if you have a slow device the write
back process is not finished and it end in corruped partition.
I guess the shutdown script has to be a bit more “sensitive”. 
The magic is to have a script wich checks all of the important
“service status” and after all services are finished do the reset
or shutdown.
