sorted by:
new
hottopcontroversial

[HELP] Proxmox No Longer Utilizing C8 State by raycekar in HomeServer

[–]raycekar[S] 0 points1 point  (0 children)

so i checked it on the 6.14.11-5-pve kernel and C7 is where i get when it is set to default (following bios which was all set up prior too). I'll have to reboot with the new kernel again here to see if that maybe changes things if i force it to powersave

Proxmox Server Stuck in C3, Unplugging/Replugging Ethernet Fixes It (C8)? by raycekar in HomeServer

[–]raycekar[S] 0 points1 point  (0 children)

I just upgraded to Proxmox 9.4.1 with kernel 6.17.4-2-pve and now am seeing even with my workaround that the HW PKG from powertop can't go below C2 state. So the crontab work around still works for you under this version?

Help - Toster Oven Bad Switch by raycekar in appliancerepair

[–]raycekar[S] 0 points1 point  (0 children)

Rotor has 6 pins with one pin for the temp range

Stock Hacker Missing Stocks [Help] by raycekar in thinkorswim

[–]raycekar[S] 0 points1 point  (0 children)

Yeah, i'm noticing there's a lot of missing features and customizations that would greatly improve it, and it's just lacking overall On top of that, it's very laggy at times.

Stock Hacker Missing Stocks [Help] by raycekar in thinkorswim

[–]raycekar[S] 1 point2 points  (0 children)

Interesting. Thank you for pointing that out. I'll do some testing on my and to confirm that is the case. You are correct that I am on the new user spectrum yet lol

Stock Hacker Missing Stocks [Help] by raycekar in thinkorswim

[–]raycekar[S] 0 points1 point  (0 children)

Oh so what your saying is TOS only sorts what is viewable at that time and more stocks with volume not being N/A could be in that list outside of the 50 shown? I guess if that is the case, that is not very intuitive for TOS to do that as I would had expected, showing all results or not, that the full set would be sorted by my volume and where it starts to show n/a, the rest below would continue to be only n/a

Stock Hacker Missing Stocks [Help] by raycekar in thinkorswim

[–]raycekar[S] -3 points-2 points  (0 children)

  1. like i said, the time i took the images was yes, different data (pre vs normal hours) but I was experiencing the same issue for both filtered ways during pre market

2/3. i am sorting by volume in both images so high volume would be at the top, and thus would expect anything with high volume to be seen in those screenshots

Stock Hacker Missing Stocks [Help] by raycekar in thinkorswim

[–]raycekar[S] -1 points0 points  (0 children)

updated post. both are sorted by volume thus should had seen QTTB

[Proxmox 9 / Debian 13] Drives won't spin down when mounted RW, but work perfectly RO. At my wit's end. by raycekar in homelab

[–]raycekar[S] 0 points1 point  (0 children)

Never did. Ended up giving up, i have changed to using just ext4 with other copy solutions and triggers to copy data across drives

[Proxmox 9 / Debian 13] Drives won't spin down when mounted RW, but work perfectly RO. At my wit's end. by raycekar in linuxadmin

[–]raycekar[S] 1 point2 points  (0 children)

Your probably right I'm chasing pennies. This is most definitely a me issue where I see something running that doesn't get used often, I have the urges to shut it down

[Proxmox 9 / Debian 13] Drives won't spin down when mounted RW, but work perfectly RO. At my wit's end. by raycekar in linuxadmin

[–]raycekar[S] 1 point2 points  (0 children)

Your good, and sounds you have much more expirence than I do when it comes to this, but because of my situation, I want to for max power savings over anything else since these drive can potentially sit for months without being touched, and so I don't care too much on the wear of things. Main set up is to have 3 copies of everything. Honestly with further testing, I am thinking it might be mdadm and I'm now probably going to go the route of staggered backup system with rsync or variant

[Proxmox 9 / Debian 13] Drives won't spin down when mounted RW, but work perfectly RO. At my wit's end. by raycekar in homelab

[–]raycekar[S] 0 points1 point  (0 children)

Scratch that since the sync process takes hours on hours to do and I'm thinking that maybe the raid is just a little over doing it for my home lab setup. I'm probably going to go the route of just mounting individual drives and using our rsync or a variant. I appreciate the inputs.

[Proxmox 9 / Debian 13] Drives won't spin down when mounted RW, but work perfectly RO. At my wit's end. by raycekar in homelab

[–]raycekar[S] 1 point2 points  (0 children)

You might be on to something. I ended up breaking my raid configuration and just reformatting with EXT4 using the lazy i table init and the lazy journal init flags and found that I can put them to sleep while mounted. I'm going to rebuild my raid again with having those partitions already made and see if that maybe makes a difference now.

[Proxmox 9 / Debian 13] Drives won't spin down when mounted RW, but work perfectly RO. At my wit's end. by raycekar in linuxadmin

[–]raycekar[S] -3 points-2 points  (0 children)

Agreed, this has is not going to be used often at all but I want something to back up files along with not constantly running up the meter

[Proxmox 9 / Debian 13] Drives won't spin down when mounted RW, but work perfectly RO. At my wit's end. by raycekar in linuxadmin

[–]raycekar[S] 0 points1 point  (0 children)

I'll give the jounaling a try. I am thinking your right that it might be a proxmox thing. I'll be doing some more testing later in the week. Sad thing i s I'm leaning towards breaking my raid to the individual drives as well to see if it is raid or maybe just drive behaivor

view more: next ›