Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Forums Feed: #armbian-rss | This channel is logged -> irc.armbian.com
IgorPec has quit [Read error: Connection reset by peer]
IgorPec has joined #armbian
IgorPec has joined #armbian
IgorPec has quit [Changing host]
NeuroScr has quit [Quit: NeuroScr]
ScrumpyJack has quit [Ping timeout: 264 seconds]
ScrumpyJack has joined #armbian
archetech has joined #armbian
_whitelogger has joined #armbian
sassinak-work has quit [Ping timeout: 260 seconds]
sassinak-work has joined #armbian
<IgorPec>
Tony_mac32: hi
macc24 has joined #armbian
<Werner>
npi-a64-only-audio-usb.patch and board-h6-orangepi-lite2-fix-missing-all.patch fail to apply. Dont know why yet.
<IgorPec>
I think we should open a Jira with a topic "Cleanup sunxi patch mess" :) you are welcome to do that
<IgorPec>
not sure if we can do much prior to this release
<Werner>
I do not have a Lite2 which may be broken due to this
<IgorPec>
aha, i will check it late. lite2 in fact have some issues ... must go now, later in the evening
<Werner>
Not that much important though. It is dev branch
<IgorPec>
aha, then later later ;)
<Werner>
Yep. Have fun
<IgorPec>
tnx, u2
<Werner>
ty
Strykar has quit [Ping timeout: 240 seconds]
Strykar has joined #armbian
dddddd has joined #armbian
macc24 has quit [Quit: WeeChat 2.8]
macc24 has joined #armbian
macc24 has quit [Ping timeout: 272 seconds]
macc24 has joined #armbian
Tenkawa has joined #armbian
ichernev has joined #armbian
<ichernev>
hello. I'm having some issues with Helios4 running ubuntu 18.04 with armbian kernel. For some reason my raid10 raid says all devices are busy, and it can't assemble them
<ichernev>
plntyk, I don't know how to change the kernel command line
<ichernev>
I tried less /proc/kmsg but I think it hung...
<ichernev>
plntyk, well, the problem is that I get this device busy, and I can't figure out why. lsof doesn't show anything, fuser doesn't show anything...
<ichernev>
plntyk, I did dmesg -n 8 (9 was not supported), and it didn't really help (no more logs in dmesg when I try to assemble the raid)
<plntyk>
the kernel cmdline is probably set in u-boot bootloader configuration file / environment variable so you have to edit that
<plntyk>
dont know if Helios4 supports a user editable text-based bootscript in /boot
<ichernev>
under /boot/armbianEnv.txt there is verbosity=1. If I change it to 8, do I need to rebuild /boot/boot.cmd?
macc24 has quit [Ping timeout: 258 seconds]
<ichernev>
so /boot/armbianEnv.txt is "sourced" in /boot/boot.cmd, which contains setenv bootargs which loglevel=${verbosity}. I just need to recompile it then
<plntyk>
yes
<ichernev>
hm 'mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr' was listed at the end of boot.cmd, but it doesn't fetch the new value from armbianEnv.txt. boot.cmd says explicitly not to modify it directly ...
<ichernev>
armbianEnv.txt is the current values of a working system (if I understand correctly), not the proper place to change values for boot.cmd. Anyway. I modified the file that should not be modified and I have verbosity=12 now
<ichernev>
https://termbin.com/h4v5 -- this is (part of) dmesg. It has a few errors around sata, not sure how critical they are
<Tenkawa>
what is on sdb?
<Tenkawa>
theres an io error on it too
<Tenkawa>
or is that the sata drive?
<ichernev>
it has 4 sata devices (sda-sdd), they are supposed to run in raid. The / is on mmc, so it is not critical for boot, but my mdadm assemble gives "DEVICE BUSY"
<Tenkawa>
can they be polled individually?
<ichernev>
Tenkawa, I don't understand the question. What command should I run to poll them? I do have /dev/sda /dev/sdb .. devices. I can run smartctl commands on them, and they respond well. The LEDs flash when polled...
<Tenkawa>
what about fdisk -l /dev/sda
<Tenkawa>
does it come back at least to a prompt
<Tenkawa>
(there may be no table on the drive but this will check communications)
<Tenkawa>
I'll brb.. I need to go outside for 5 minutes and plug up lawnmower battery
<ichernev>
they are part of raid array, so no partitions, but it find basic info: https://termbin.com/hcne
<Tenkawa>
I know that however fdisk -l still sends a call to the controller and drive to make sure its readable
<Tenkawa>
if you dont even get feedback at the os level the raid isnt going tp matter anyway
<Tenkawa>
er to
<Tenkawa>
for this test
Hokedli has joined #armbian
<Tenkawa>
afk again.. brb (doing a lot of stuff today while our weather is half way decent)
<ichernev>
Tenkawa, well, I can dd if=/dev/sdX and read as much as I want to, so in that regard they are accessible
<Tenkawa>
back
<Tenkawa>
thats good
<Tenkawa>
so you have "direct" access
<Tenkawa>
hmm
<Tenkawa>
let me look up something
<[TheBug]>
Helios4 is Marvel much like ESPRESSOBin
<Tenkawa>
hmm.. do you have smartctl installed?
<[TheBug]>
your using onboard SATA channels or have you added additional via a card?
<ichernev>
this is smartctl on all devices. I ran short tests and they are all good
<[TheBug]>
^^
<ichernev>
[TheBug], what do you mean? It is marvel 380, and it is helio4, yes
<[TheBug]>
so are you using the built on 4 ports onlyu
<[TheBug]>
or did you add another sata via mPCIe
<[TheBug]>
I can't remember if they provided a mPCIe there
<[TheBug]>
or used it for the 4 ports they supply
<ichernev>
[TheBug], ah, sorry. I'm using "onboard" -- the ones that came in with the board. I'm not sure how the board itself is configured, but there is a mainline DTS for inspiration :)
<[TheBug]>
k just checking because for my ESPRESSOBin's I use a 4 port sata card in mPCIe
<Tenkawa>
hmmm thats not good that they wont even register
<[TheBug]>
which I think Helios uses similar just on board using the mpcie lanes
<[TheBug]>
Do you have any patition table on the drives your using?
<[TheBug]>
when you first assembled the raid10
<[TheBug]>
did you do it on direct device
<[TheBug]>
or on paritions?
<ichernev>
[TheBug], I used whole devices. I read it is the "best" way? ... :-/
<[TheBug]>
or is this the first time trying to assemble?
<[TheBug]>
thats fine
<[TheBug]>
just trying to get a better idea of y our setup
<ichernev>
Tenkawa, what do you mean "wont even register". Register where
<Tenkawa>
actually using partitions is
<[TheBug]>
can you pastebin the command your running that returns the error?
<Tenkawa>
line 324 of your smartctl is one example
<ichernev>
Tenkawa, that is weird, they are relatively new model. 8GB Seagate Skyhawk
<[TheBug]>
when your do a cat /proc/mdstat
<[TheBug]>
what do you see?
<[TheBug]>
it sounds to me like it already auto assembled
<[TheBug]>
most of time mdadm runs on boot and auto assembles
<[TheBug]>
so unless you did something to cause it not to during boot you may be fighting a game you already won
<ichernev>
I was running this setup for 1.2 years, whithout any issues. One day I receive an email that it is degraded (one disk out), but when I logged in I saw the "missing" drive. For some reason it had a different name (sde), but it is all configured with UUID (I hope). And now after a reboot it can't attach any drives -- they are all busy
<[TheBug]>
the new name means it likely lost connectivity to the drive for some reason like hot-swap
<ichernev>
yes, I checked :) it is detail -- I've run it. I had a long conversation in the ubuntu channel, but when they figured I was running armbian kernel they got kind of angry :|
archetech has quit [Quit: Leaving]
<[TheBug]>
um has nothing to do with kernel
<[TheBug]>
things are just out of whack and you will need to speed time on it
<[TheBug]>
you will need to stop the mdadm raid
<[TheBug]>
you will need to examine the drives to make sure they are still in sync
<[TheBug]>
then you will want to likely force assemble the raid again
<[TheBug]>
you will probably want to follow similar case
<[TheBug]>
stop the raid
<[TheBug]>
examine drives
<[TheBug]>
then force re-assemble if you need
redentor has joined #armbian
<ichernev>
[TheBug], ok, that explains most of it. So should I let mdadm figure out the "test", or I need to test the drives myself? It would make sense that mdadm can do that
<[TheBug]>
not sure what you mean by test, I didn't use that word, I said examine which is a function of the tool also described in that reference
<ichernev>
I've run examine -- they all look "good"
<ichernev>
let me paste it again (it was at the top)
<[TheBug]>
Either: A. drive is dead, B. SATA cable is bad
<[TheBug]>
those are my primary though
<[TheBug]>
thought*
<[TheBug]>
the last would be C. sata controller has issues, but lets hope not that
<[TheBug]>
[ 5609.510650] md/raid10:md0: Disk failure on sdd, disabling device.
<[TheBug]>
md/raid10:md0: Operation continuing on 3 devices.
<[TheBug]>
it even says
<[TheBug]>
if you have another drive I would just throw it in and try to rebuild
<[TheBug]>
if it rebuilds... awesome you had a bad drive
<[TheBug]>
if it fails or does something similar, replace SATA cable (or do both at once if you have a spare)
<[TheBug]>
if it fails after that.. welll....maybe have a good cry in your cherios
<[TheBug]>
cause would sound like controller has problem and you may not anylonger be able to use port 4 (if you try the rest and it keps failing)
<ichernev>
I don't have an 8GB drive lying around ... but it's good to figure out the cable situation before getting a new drive. Will reconnecting to different ports be OK? It should be
<[TheBug]>
port shouldn't matter, technically I believe it should even be hot plug
<[TheBug]>
but I am not normally that brave
<[TheBug]>
hehe
<ichernev>
also it could be the controller. I have 2 identical boards (but due to the covit lockdown they are not with me ATM)
<[TheBug]>
well those are the things I would do
<[TheBug]>
sounds like at leasty your array is online in meantime now
<[TheBug]>
which is a plus
<[TheBug]>
but yeah
<[TheBug]>
you need to try replace drive / sata cable