Perhaps I should just ask the question. I am dealing with a hard drive that is a bit older hdd/sdd couple gigs takes in the data as the sdd and then writes it to the hdd or dumps etc. Interestingly the hard drive clogs every time I try to download the whole Monero block chain.

My drive tree dose not even show the SSD as a separate drive in the tree.

It's one large drive and a swap.

But Ive crashed this box twice trying to mine. Its not a decent miner I run a meetup and we want to mine with it to show people.

So any help would be great.

are you trying to mine with p2pool?

No

No

wtf

lag sorry

then you don't need to download the chain for mining

if you do want to DL the chain you should use the SSD

it is ~10x faster than the HDD

Oh ok. the SSD is not big enough

Its like 10G SSD

how much space do you have available?

oh

1tb

which OS are you using?

its one of those old 1tb 10g ssd 990 HDD

ah manjaro couldn't tell you the version OTT

how much RAM do you have?

Could you link me to the docs that let me mine without downloading the whole. 3799

swap is 83842

the mining software is xmrig

you would be mining to a pool

Just to be clear the step that crashes my little laptop is downloading Monerod

you do have to have a wallet address to mine to

Again I just have a laptop and I help with a crypto meetup. So I figured Monero was a good choice to show people mining.

I setup the client so I think so.

guess you could DL the monero GUI and from the option use a remote node instead of downloading the chain

3799 RAM?

you need at least 4GB RAM to mine

I don't use the GUI so....

Im not using the GUI either I am using terminal

I have never used a remote node either

Can you guys link to docs on how to use a remote node.

if your computer crashes already during sync it might be too weak to mine

that's why I wanted to ask you how much RAM you have

Hmm could be I might be able to get some more RAM

Like I said this is a old laptop I take to a meetup

hi o/

i would like to ask for recommendations for an error i'm getting.

trying to send some xmr using cli wallet + local full monerod (i tried with gui and feather + remote nodes, still same problems)

both monerod and cli shows errors. monerod gives "Bad key image!" and wallet says "transaction <XXXXXXXXX> was rejected by daemon Reason: invalid input"

i'm using the latest v0.18.1.0 version, i synced it with this version, didn't upgrade or use any previous database file etc.

Looks to me like there is some data corruption in the wallet file regarding outputs. I would probably try to rescan, or build a second version of the wallet using seed and restore height to see what results

So first attempt in the CLI would be "rescan_spent"

rbrunner: yup, this may be the 7th-8th time i tried by now

You mean "rescan_spent" does not rectify the problem? First escalation would be "rescan_bc soft". Did you try that already?

i'll try rescan_bc soft

i imagine this'll take some time

Depending on the wallet's birthday, yes

it's not so recent, i also confirmed all the data scanning from 0 height 2-3 times.

But anyway, cleanest way with a crystall-clear result would indeed be to make a brand-new wallet file with the help of the seed. Just to check what results, for beginning. You can still decide how to proceed after that of course.

With a new filename so not to loose your current wallet file of course

i built up the wallet from scratch a couple of times by now. like i said in some instances from the 0 height in spite of waiting time. results is the same.

so i do have couple of differently named wallets for the same wallet just to check :)

Alright ... then I am out of ideas. Sounds very strange. I mean, if you restore from seed, you get what's recorded in the blockchain, and *that* for damned sure should not contain any contradictions, bad key images or such, one would think!

yeap, thanks for bearing with me.

But if really something is wrong with at least one of your outputs, and nothing helps, maybe you should try to "evacuate" your wallet

You should be able to transfer out any output that is ok one by one using "sweep_single"

And what is left is then ... a mystery.

sweep_all gives the exact same error

i'll try sweep single

Yes, of course, because that would include the bad output(s) ...

With "sweep_single" you can pick them one by one

i see, it may help. i'll try as soon as rescan_bc soft finished

also i was trying with sweep_all anyway, trying to transfer arbitrary amounts gives "Error: internal error: Known ring does not include the spent output:"

Really strange

with others' suggestions, i also tried by deleting ringdb files

yeah, somehow this wallet is "bugged" at the core..

Maybe not problable, but in theory also the blockchain file of your local daemon could have some problems. Did you already try a remote daemon for a change?

sounds like an error worth pinning down

rbrunner: yeah i tried remote nodes for couple of times even starting from scratch, creating the wallet from seeds etc.

like i mentioned i tried with both gui and feather

if there's a "bad keyimage" would it also interfere with signing key images?

my local nodes is running nothing but monerod, files are on an almost brand new ssd etc.

it might be worth asking in -dev?

Seems to be 2 places where that exception gets thrown in the repo and maybe luigi or moneromoo will see it and know what's up

yeah lemme join -dev

also a straight up github issue might be something to do. restoring from seed not helping is concerning (in the end it could just be stupidity though... hopefully)

i'll try to export any information for the -dev team if this is not an isolated and broken for only one time case. if it is, there may be nothing to do with this particular wallet.