00:04:46 <Nails> 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.
00:06:11 <Nails> My drive tree dose not even show the SSD as a separate drive in the tree.
00:06:27 <Nails> It's one large drive and a swap.
00:07:16 <Nails> 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.
00:07:23 <Nails> So any help would be great.
00:07:56 <nioc> are you trying to mine with p2pool?
00:09:10 <Nails> No
00:09:10 <Nails> No
00:09:12 <Nails> wtf
00:09:17 <Nails> lag sorry
00:09:37 <nioc> then you don't need to download the chain for mining
00:09:57 <nioc> if you do want to DL the chain you should use the SSD
00:10:09 <nioc> it is ~10x faster than the HDD
00:10:13 <Nails> Oh ok. the SSD is not big enough
00:10:22 <Nails> Its like 10G SSD
00:10:29 <nioc> how much space do you have available?
00:10:34 <nioc> oh
00:10:35 <Nails> 1tb
00:10:44 <selsta> which OS are you using?
00:11:01 <Nails> its one of those old 1tb 10g ssd 990 HDD
00:11:41 <Nails> ah manjaro couldn't tell you the version OTT
00:12:30 <selsta> how much RAM do you have?
00:14:21 <Nails> Could you link me to the docs that let me mine without downloading the whole. 3799
00:14:36 <Nails> swap is 83842
00:16:29 <nioc> the mining software is xmrig
00:16:38 <nioc> you would be mining to a pool
00:16:44 <Nails> Just to be clear the step that crashes my little laptop is downloading Monerod
00:17:12 <nioc> you do have to have a wallet address to mine to
00:17:57 <Nails> 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.
00:18:04 <Nails> I setup the client so I think so.
00:19:46 <nioc> guess you could DL the monero GUI and from the option use a remote node instead of downloading the chain
00:20:01 <selsta> 3799 RAM?
00:20:10 <selsta> you need at least 4GB RAM to mine
00:20:10 <nioc> I don't use the GUI so....
00:20:57 <Nails> Im not using the GUI either I am using terminal
00:22:10 <nioc> I have never used a remote node either
00:30:19 <Nails> Can you guys link to docs on how to use a remote node.
00:34:56 <selsta> if your computer crashes already during sync it might be too weak to mine
00:35:09 <selsta> that's why I wanted to ask you how much RAM you have
00:47:00 <Nails> Hmm could be I might be able to get some more RAM
00:47:13 <Nails> Like I said this is a old laptop I take to  a meetup
05:48:49 <elucidator> hi o/
05:49:13 <elucidator> i would like to ask for recommendations for an error i'm getting.
05:50:06 <elucidator> trying to send some xmr using cli wallet + local full monerod (i tried with gui and feather + remote nodes, still same problems)
05:51:37 <elucidator> both monerod and cli shows errors. monerod gives "Bad key image!" and wallet says "transaction <XXXXXXXXX> was rejected by daemon Reason: invalid input"
05:52:23 <elucidator> 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.
05:54:33 <rbrunner> 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
05:55:42 <rbrunner> So first attempt in the CLI would be "rescan_spent"
05:57:10 <elucidator> rbrunner: yup, this may be the 7th-8th time i tried by now
05:57:51 <rbrunner> You mean "rescan_spent" does not rectify the problem? First escalation would be "rescan_bc soft". Did you try that already?
05:58:36 <elucidator> i'll try rescan_bc soft 
05:59:16 <elucidator> i imagine this'll take some time
05:59:27 <rbrunner> Depending on the wallet's birthday, yes
06:00:19 <elucidator> it's not so recent, i also confirmed all the data scanning from 0 height 2-3 times.
06:01:23 <rbrunner> 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.
06:02:03 <rbrunner> With a new filename so not to loose your current wallet file of course
06:03:32 <elucidator> 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.
06:04:14 <elucidator> so i do have couple of differently named wallets for the same wallet just to check :)
06:05:20 <rbrunner> 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!
06:06:20 <elucidator> yeap, thanks for bearing with me. 
06:06:32 <rbrunner> But if really something is wrong with at least one of your outputs, and nothing helps, maybe you should try to "evacuate" your wallet
06:06:53 <rbrunner> You should be able to transfer out any output that is ok one by one using "sweep_single"
06:07:24 <rbrunner> And what is left is then ... a mystery.
06:07:43 <elucidator> sweep_all gives the exact same error
06:07:51 <elucidator> i'll try sweep single
06:07:59 <rbrunner> Yes, of course, because that would include the bad output(s) ...
06:08:14 <rbrunner> With "sweep_single" you can pick them one by one
06:08:49 <elucidator>  i see, it may help. i'll try as soon as rescan_bc soft finished
06:09:45 <elucidator> 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:"
06:10:34 <rbrunner> Really strange
06:10:39 <elucidator> with others' suggestions, i also tried by deleting ringdb files
06:11:03 <elucidator> yeah, somehow this wallet is "bugged" at the core..
06:21:47 <rbrunner> 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?
07:05:38 <badjabber> sounds like an error worth pinning down
07:09:51 <elucidator> rbrunner: yeah i tried remote nodes for couple of times even starting from scratch, creating the wallet from seeds etc.
07:10:08 <elucidator> like i mentioned i tried with both gui and feather
07:10:59 <badjabber> if there's a "bad keyimage" would it also interfere with signing key images?
07:11:01 <elucidator> my local nodes is running nothing but monerod, files are on an almost brand new ssd etc. 
07:45:54 <badjabber> it might be worth asking in -dev?
07:52:23 <badjabber> 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
08:03:05 <elucidator> yeah lemme join -dev
08:11:10 <badjabber> 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)
08:28:39 <elucidator> 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.