Pages:
Author

Topic: [BOUNTY] - 0.04 BTC - Help me solve my smOS problem! (Read 1185 times)

member
Activity: 116
Merit: 10
Problem Identified!

I regret not being as thorough as I could have in my initial post about my setup.

I have been powering the motherboard/cpu and the risers with a 750w evga PSU, then running the cards' main power connection off of a server PSU.

As soon as I remove the server PSUs from the equation and run a rig solely on a single ATX PSU everything works fine!

Now, I have multiple server PSUs, and the problem persists across those....

so now my question is why does smOS hang when using the server PSUs?

I'd hate to have to replace them all....

This is my first time using server PSUs, is how I set them up incorrect?

looks like you need to synchronize your power up sequence properly.

I have many rigs with server psu and all is fine.

for dual atx psu, you need the addon adapter.

for dual server psu, i use a special Y power cord that basically powers both server psu at the same time (without using addon adapter).

i must admit that i dont have a mixed server psu and atx psu rig though.... like in your case.

I actually got the idea to mix the server PSUs with ATX PSUs from yun9999's thread here: https://bitcointalksearch.org/topic/data-center-mining-garage-and-man-mining-cave-part-2-1806061

He claims to have used them prior to getting PICOs from Finksy. I did not think the power up sequence would matter with the server PSUs since they are always "on".

Dual ATX I have done before with an adapter, but I'd like to take advantage of all these platinum server PSUs I bought  Roll Eyes



legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Problem Identified!

I regret not being as thorough as I could have in my initial post about my setup.

I have been powering the motherboard/cpu and the risers with a 750w evga PSU, then running the cards' main power connection off of a server PSU.

As soon as I remove the server PSUs from the equation and run a rig solely on a single ATX PSU everything works fine!

Now, I have multiple server PSUs, and the problem persists across those....

so now my question is why does smOS hang when using the server PSUs?

I'd hate to have to replace them all....

This is my first time using server PSUs, is how I set them up incorrect?

looks like you need to synchronize your power up sequence properly.

I have many rigs with server psu and all is fine.

for dual atx psu, you need the addon adapter.

for dual server psu, i use a special Y power cord that basically powers both server psu at the same time (without using addon adapter).

i must admit that i dont have a mixed server psu and atx psu rig though.... like in your case.
newbie
Activity: 1
Merit: 0
I am having similar error during booting, and it happen quite a lot
since I am pretty new at this maybe I am doing something wrong.

running simplemining on

ASUS PRIME H270-PLUS
Intel G3950
8gb crucial
16gb usb sandisk
GPUs is a mess, 4x MSI RX580, 1x PowerColor RX580 and 1 XFX 570
EVGA SuperNova 1000PS (full load it shows to be pulling out 880W from the wall)

https://i.imgur.com/3Ep3Bn4.jpg

And also I am having this at random, I tried disabling the GPUs and it keep popping up

https://i.imgur.com/PSC37aR.jpg

the rig is rebooting a lot, that is super annoying
member
Activity: 116
Merit: 10
Problem Identified!

I regret not being as thorough as I could have in my initial post about my setup.

I have been powering the motherboard/cpu and the risers with a 750w evga PSU, then running the cards' main power connection off of a server PSU.

As soon as I remove the server PSUs from the equation and run a rig solely on a single ATX PSU everything works fine!

Now, I have multiple server PSUs, and the problem persists across those....

so now my question is why does smOS hang when using the server PSUs?

I'd hate to have to replace them all....

This is my first time using server PSUs, is how I set them up incorrect?

You could remove the ATX psu and only use the server's one with a Pico PSU.

see => https://bitcointalksearch.org/topic/server-psu-powered-gpu-rig-packages-picos-risers-adapter-cables-etc-1864539

That was my original plan, but Finksy has not had stock for awhile =/

At this point I might switch to using two ATX PSUs just because I can get them shipped quickly, then scale with Server PSUs later. But Ideally I would find out why my combination of the two are not working...
legendary
Activity: 1638
Merit: 1005
Problem Identified!

I regret not being as thorough as I could have in my initial post about my setup.

I have been powering the motherboard/cpu and the risers with a 750w evga PSU, then running the cards' main power connection off of a server PSU.

As soon as I remove the server PSUs from the equation and run a rig solely on a single ATX PSU everything works fine!

Now, I have multiple server PSUs, and the problem persists across those....

so now my question is why does smOS hang when using the server PSUs?

I'd hate to have to replace them all....

This is my first time using server PSUs, is how I set them up incorrect?

You could remove the ATX psu and only use the server's one with a Pico PSU.

see => https://bitcointalksearch.org/topic/server-psu-powered-gpu-rig-packages-picos-risers-adapter-cables-etc-1864539
member
Activity: 116
Merit: 10
Problem Identified!

I regret not being as thorough as I could have in my initial post about my setup.

I have been powering the motherboard/cpu and the risers with a 750w evga PSU, then running the cards' main power connection off of a server PSU.

As soon as I remove the server PSUs from the equation and run a rig solely on a single ATX PSU everything works fine!

Now, I have multiple server PSUs, and the problem persists across those....

so now my question is why does smOS hang when using the server PSUs?

I'd hate to have to replace them all....

This is my first time using server PSUs, is how I set them up incorrect?
member
Activity: 116
Merit: 10
What is this "command halt"? Obviously I only see the config.txt when I plug into windows, so I assume I need to use this command to see the syslinux folder? (doesn't make sense to me, but my linux experience is limited)

My fault, I didn't undestand you were using simpleminer OS. If using "original" smOS-linux you can access all the system data, including a folder called syslinux where the live.cfg is located. Unfortunately  I don't have a windows machine right now, I will install it on virtualbox later and will update this post if I can find anything usefull

ah okay, thanks!

I just tried the other smOS image, and as expected received the same result.
member
Activity: 110
Merit: 94
What is this "command halt"? Obviously I only see the config.txt when I plug into windows, so I assume I need to use this command to see the syslinux folder? (doesn't make sense to me, but my linux experience is limited)

My fault, I didn't undestand you were using simpleminer OS. If using "original" smOS-linux you can access all the system data, including a folder called syslinux where the live.cfg is located. Unfortunately  I don't have a windows machine right now, I will install it on virtualbox later and will update this post if I can find anything usefull

EDIT: I'm glad you found out the source of your problems, I'm writing what I've discovered anyway. You could not see any folder because while writing simpleminer to USB thumb, the drive get partitioned: first partition of 10MB with the configuration file and the second of about 7GB with OS data. That's why you couldn't see any folder inside, Windows is a bit "stupid" and is unable to read multiple partition on USB thumbs. Plugging the drive to a Linux machine will show you both partitions. BUT the "structure" of the second partition is completely different from the original smOS I have, I call this original because it's a 2013 project and simpleminer was born last year. I'm starting to think I blundered and these are completely different products  Undecided
member
Activity: 116
Merit: 10
I appreciate all the replies!

Unfortunately this does not appear to be an issue with the amount of cards. I experience this problem with even just one card plugged in. I have also run into this issue with just about any combination of riser/GPU/mobo etc..... I have a lot of hardware here, and have built multiple systems (same specs) and they all get the same result. About 80% of the time it boots to that output I linked in my original post, otherwise it boots and starts mining normally.

I am using the smOS image labeled: simpleminer-RX-v1093-4.11.rc8-16.60-enableexe0ANDips0.imgc

I have not tried: simpleminer-RX-v1093-4.11.rc8-16.60-enablerc60.imgc

...which @citronick recommended. I'd image if the imagine I'm using causes this exact issue then I would have read someone else running in to it, but I will nevertheless try it out.

I also had not previously seen the solution mentioned by @LordStapy concerning the live.cfg file. Again, I do not think my issue pertains ot multiple cards running, but I'll give it a shot as well and return with my results.

EDIT: can anyonehelp me with better directions on how to do this:

"1. You have problem with more then 3,4,5 cards, or you cant boot SMOS. This is solution. Turn off your rig by command halt. After your rig turns off, plugout USB. When you plugout USB, plugin USB on windows machine. Open SMOS label, and goes to the syslinux folder. You will see file named live.cfg, delete it. And DOWNLOAD it file from here (DOWNLOAD name is linked), extract it, and put it in the folder. "

What is this "command halt"? Obviously I only see the config.txt when I plug into windows, so I assume I need to use this command to see the syslinux folder? (doesn't make sense to me, but my linux experience is limited)
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
Im starting to lean towards memory now:

you only have 4Gb, and either drive is 16Gb, which you really wanna have for that much for virtual memory as well.....

take some ram from another rig for a test;  bump it up to 6 or 8Gb... worth a try.

Phil is onto something as well.   PRoblem arise with GPU density.   6 is the tipping point.  7+ is where the most problems arise.
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
if everything fails.....

i think you have bad case of corrupted smos in your usb stick

download the latest \RX image from smos website

For MSI Gaming M5 ... use this one:  https://simplemining.net/download/simpleminer-RX-v1093-4.11.rc8-16.60-enablerc60.imgc

ensure your M5 has latest BIOS update and also 4G enabled.

and use hddraw to clone that image to your thumbdrive

16gb usb3 for speed, is preferred

let it download all the necessary patches and upgrades

good luck
member
Activity: 63
Merit: 10
try replacing pci-e slot...in example, my 6. card only works without issues in my 5th pci-e slot while all others work whereever I put them

my issues is weird because I have 6 identical rx570 pulse
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
Run your  7x  card rig  with  4x cards

 when it works post a screen shot of it
go to five cards  
and if the five card  works go to six.



.. I have found  four  and five cards  are really stable
and that six and up suck at stability.



Time and time again  there are posts about bad 6 ,7 ,8  card rigs.

I don't want your bounty.  I am just tired of reading about bad six and seven card rigs.

My rigs never boot on smos  they just run.  6 or 7 weeks at a time if not more.

Why is that  I do 3,4,5 card builds and don't clock the fuck out of the gear.

I bet your  each of your 7 card rigs boot  2 or 3 times a week or more.





member
Activity: 110
Merit: 94
Have you tried booting the rig with 3 or less cards? If it works maybe that's your issue, smOS could have problems  booting with more than 3 cards.
It seems the solution is replacing the live.cfg in the syslinux folder of your USB.

Take a look at https://www.smos-linux.org/tips/#9 here you can find an alternate live.cfg file
member
Activity: 116
Merit: 10
What type of storage device are you running this on?   Any chance of some sectors beginning to fail?  Remember, they will typically be destroying the areas where data is stored and read all the time.

It's my first instinct....

I did actually find I was running into issues with some of my SSDs, but I switched to a USB and still have the problem above with both.
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
What type of storage device are you running this on?   Any chance of some sectors beginning to fail?  Remember, they will typically be destroying the areas where data is stored and read all the time.

It's my first instinct....
member
Activity: 116
Merit: 10
Do you have Z170 version of SMOS?
simplemining.net/download/simpleminer-RX-v1093-4.11.rc8-16.60-enableexe0ANDips0.imgc

I do!

edit: smOS does auto-update, and I've seen at least a couple rigs update once or twice. But if the updates caused issues I'm sure I'd see others with my same problem. I am definitely not the only one running these boards/cards in smOS.
newbie
Activity: 45
Merit: 0
Do you have Z170 version of SMOS?
simplemining.net/download/simpleminer-RX-v1093-4.11.rc8-16.60-enableexe0ANDips0.imgc
member
Activity: 116
Merit: 10
Try those settings:
1) Make sure you're running the latest BIOS!
2) Enable 4G
3) Set PCIe support to "Auto" - DO NOT MANUALLY SET TO GEN1. THIS CAUSES MAJOR ISSUES
4) Enable onboard graphics startup as first! I believe this is changing "PEG" to "IGD" or something in the Advanced BIOS
5) Plug your monitor into the ONBOARD graphics

I should have mentioned this, but I did set them all up like this. I also have had 7 cards mining on one board, although only for a few minutes before I restarted the rig to continue troubleshooting.
member
Activity: 63
Merit: 10
Try those settings:
1) Make sure you're running the latest BIOS!
2) Enable 4G
3) Set PCIe support to "Auto" - DO NOT MANUALLY SET TO GEN1. THIS CAUSES MAJOR ISSUES
4) Enable onboard graphics startup as first! I believe this is changing "PEG" to "IGD" or something in the Advanced BIOS
5) Plug your monitor into the ONBOARD graphics
Pages:
Jump to: