Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum/Twitter feed: #armbian-rss | Logs: -> irc.armbian.com
norwich_ has joined #armbian
norwich has quit [Ping timeout: 248 seconds]
norwich_ is now known as norwich
amazingfate has joined #armbian
amazingfate_ has quit [Ping timeout: 276 seconds]
<nekomancer[m]> can't build some jammy images on aarch64. breaks as... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/99bdf21ad1aec1c627cac8f51e13c3df1fa61893)
<ArmbianHelper> ^ Error retrieving title. Check the log for more details.
<nekomancer[m]> build on impish, `./compile.sh docker BOARD=odroidn2 BRANCH=edge`
<nekomancer[m]> `RELEASE=jammy`
lemonzest has quit [Quit: WeeChat 3.4]
oida has quit [Ping timeout: 240 seconds]
amazingfate_ has joined #armbian
xoan5 has joined #armbian
amazingfate has quit [Ping timeout: 276 seconds]
xoan has quit [Ping timeout: 248 seconds]
xoan5 is now known as xoan
oida has joined #armbian
oida has quit [Client Quit]
oida has joined #armbian
archetech has joined #armbian
amazingfate has joined #armbian
amazingfate_ has quit [Ping timeout: 240 seconds]
amazingfate_ has joined #armbian
pablocastellanos has quit [Ping timeout: 248 seconds]
amazingfate has quit [Ping timeout: 276 seconds]
amazingfate has joined #armbian
amazingfate_ has quit [Ping timeout: 240 seconds]
darsie has quit [Ping timeout: 272 seconds]
pablocastellanos has joined #armbian
<Armbian-Discord> <l​anefu> Nek
<Armbian-Discord> <l​anefu> See if you can run losetup -f someimage.img
amazingfate_ has joined #armbian
<Armbian-Discord> <l​anefu> And see what errors are there and dmesg
amazingfate has quit [Ping timeout: 276 seconds]
<Armbian-Discord> <I​gorPec> nekomancer[m] your docker is not in privileged mode
<Armbian-Discord> <I​gorPec> "[ error ] Device node /dev/loop0p1 does not exist"
amazingfate_ has quit [Remote host closed the connection]
amazingfate has joined #armbian
amazingfate_ has joined #armbian
archetech has quit [Quit: Konversation terminated!]
amazingfate has quit [Ping timeout: 246 seconds]
c0rnelius has quit [Ping timeout: 260 seconds]
archetech_n2 has joined #armbian
amazingfate_ is now known as amazingfate
amazingfate_ has joined #armbian
amazingfate has quit [Ping timeout: 256 seconds]
amazingfate_ is now known as amazingfate
amazingfate_ has joined #armbian
amazingfate has quit [Ping timeout: 276 seconds]
lemonzest has joined #armbian
abws has quit [Ping timeout: 256 seconds]
amazingfate_ has quit [Read error: Connection reset by peer]
amazingfate has joined #armbian
slacker_HD has joined #armbian
archetech_n2 has quit [Quit: Konversation terminated!]
amazingfate_ has joined #armbian
amazingfate has quit [Ping timeout: 246 seconds]
marco44 has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
marco44 has joined #armbian
amazingfate_ has quit [Ping timeout: 256 seconds]
slacker_HD has quit [Quit: Connection closed]
archetech has joined #armbian
BCMM has joined #armbian
<BCMM> the hard drive in my Odroid HC2 spins up when i SSH in. it's running bullseye, and i'm reasonably sure it didn't do this when it was running buster
<BCMM> any idea why this is happening, and how to begin debugging this?
<BCMM> in particular, any information about how the MOTD is generated would be appreciated
<BCMM> i'm not by any means sure, but i suspect that whatever it's doing to discover my HDD mount and display how full it is involves actually reading the FS
<kolla> check mount, if filesystem is mounted sync
<BCMM> kolla: it is not mounted sync
indy has quit [Read error: Connection reset by peer]
indy has joined #armbian
<BCMM> hmm. i've done `echo 1 > /proc/sys/vm/block_dump`, and connecting with ssh spins up the drive without producing any dmesg output
archetech has quit [Quit: Konversation terminated!]
pablocastellanos has quit [Ping timeout: 246 seconds]
pablocastellanos has joined #armbian
<Armbian-Discord> <I​gorPec> Bcmm it is possible that df of /dev/sda is default. or was at some point. Check /etc/defauls/armbian-motd and /etc/update.motd/30*
<BCMM> just doing df shouldn't spin up the disk, as far as i can see
<BCMM> i've set `STORAGE=/dev/nope`, just for debugging, and it does seem to have stopped the behaviour
<BCMM> but i don't really understand what was causing it in the first place
archetech has joined #armbian
Net147 has quit [Quit: Quit]
indy has quit [Quit: ZNC 1.8.2 - https://znc.in]
Net147 has joined #armbian
indy has joined #armbian
<BCMM> @IgorPec oh, i bet it's because it's reading temperatures with smartctl
<BCMM> hmm, that doesn't, in isolation, seem to spin up the drive. but i've seen things that normally shouldn't cause spin-ups do it before on this controller
<BCMM> this might be an intermittent problem
<Armbian-Discord> <I​gorPec> probably temp reading, yes
<BCMM> thing is, i can run `smartctl -l scttempsts /dev/sda` without it spinning up
<BCMM> starting to think there's a difference in behaviours between it spinning down on the timer and me spinning it down manually with hdparm for testing
lemonzest has quit [Quit: WeeChat 3.4]
<[TheBug]> it could be using hdparm -H
<[TheBug]> but usually thats more specific to Hitachi drives
<[TheBug]> there is also hddtemp
<[TheBug]> it could leverage that and it could do something different
<BCMM> [TheBug]: the actual command in /etc/update-motd.d/30-armbian-sysinfo is `smartctl -l scttempsts $DISK`
<BCMM> (unfortunately i can't find any way of `resetting` things other than waiting several minutes, so i haven't yet confirmed that that's the line that's doing it)
darsie has joined #armbian
<IgorPec> i use this https://armbian.lane-fu.com/linx/8r1p05rx.txt to generate temp for all drives except one
<ArmbianHelper> ^ linx - 8r1p05rx.txt
<[TheBug]> is the drive USB or sata?
archetech has quit [Quit: Konversation terminated!]
<BCMM> mine?
<BCMM> [TheBug]: it's a SATA drive, connected to the HC2's built-in USB-SATA bridge (JMS578)
<BCMM> have just confirmed that reading the temperature with smartctl makes it spin up
<[TheBug]> so its actually USB is the answer and yes, USB controllers can do some funny things
<BCMM> yeah, this controller definitely has some weirdness
<[TheBug]> cause some times they emulate the response, others it polls for it
<[TheBug]> so you can see what you describe where maybe one call to it doesn't spin it up, but another does
<BCMM> `smartctl -l scttempsts /dev/sda` spins up the drive under some circumstance but not under others
<BCMM> i wonder if the controller internally caches the response for some period of time
<[TheBug]> that would be my guess
<BCMM> what it *looks* like is that `hdparm -y /dev/sda` puts it in a subtly different state than just waiting for it to spin down on its own does
<BCMM> but the passage of time is a confounding variable of course
<BCMM> spin up/spin down is definitely weird on this controller. setting an automatic spin down time on the drive via hdparm does nothing; you have to set it via the controller using it's firmware flashing tool...
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #armbian
lemonzest has joined #armbian
<BCMM> can't even reliably find out whether it's spinning without making it spin up :(
norwich has quit [Ping timeout: 256 seconds]
haritz has joined #armbian
norwich has joined #armbian
norwich has quit [Ping timeout: 256 seconds]
norwich has joined #armbian
norwich has quit [Ping timeout: 250 seconds]
norwich has joined #armbian
norwich has quit [Ping timeout: 256 seconds]
norwich has joined #armbian
kolla has quit [Quit: %fog relay%]
kolla has joined #armbian
norwich has quit [Ping timeout: 256 seconds]
norwich has joined #armbian
c0rnelius has joined #armbian
BCMM has quit [Read error: Connection reset by peer]
BCMM_ has joined #armbian
BCMM_ is now known as BCMM
<ArmbianHelper> ^ Pull requests · armbian/build · GitHub
alekksander has joined #armbian
clever has quit [Ping timeout: 240 seconds]
clever has joined #armbian
Lucanis has quit [Quit: Leaving]
Lucanis has joined #armbian
pablocastellanos has quit [Ping timeout: 256 seconds]
<stipa> peeps, what's good cheap quality brand for RJ45 connectors where that anchor doesn't brake easily?
<stipa> i guess there's also some kind of a material that's hard to brake
<stipa> "Retaining latch"
<BCMM> stipa: i don't know about the brand, but i've got a cable with those "boots" on which works pretty well
<BCMM> so the latch is still the same material, but it can't snag on stuff
<BCMM> https://www.cablemonkey.co.uk/cat5e-accessories/9551-rj45-boot.html like these, except the cable came with them on it
<ArmbianHelper> ^ RJ45 Boot | Cat5e Accessories
<BCMM> it makes them a tiny bit harder to unclip, but really, how often does one need to do that?
<stipa> BCMM: right, yeah, for some reason i don't have luck with those connectors
<stipa> i even have some with "boots", somehow the clips brake too, they break and end up being flush with the connector
<stipa> i'm aware there's that plastic that can be bent for eternity, i just don't know what's the material called
<stipa> i've seen some used on the housing of a casio caluclator
<stipa> where upper part and part below of the housing stay connected when the box is opened
<stipa> the ankle is of some plastic that lasts forever
<stipa> RJ45 connectors out of that material should be fine
<stipa> maybe it's NYLON
alekksander has quit [Quit: Konversation terminated!]
flyback has quit [Quit: Leaving]
flyback has joined #armbian
pablocastellanos has joined #armbian
BCMM has quit [Quit: Konversation terminated!]
mangix has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]