| 00:40.12 | *** join/#maemo capitanocrunch (~capitanoc@host189-61-dynamic.41-79-r.retail.telecomitalia.it) |
| 00:40.12 | *** join/#maemo capitanocrunch (~capitanoc@unaffiliated/capitanocrunch) |
| 00:41.05 | *** part/#maemo capitanocrunch (~capitanoc@unaffiliated/capitanocrunch) |
| 00:42.49 | *** join/#maemo jerardepardieu (~capitanoc@unaffiliated/capitanocrunch) |
| 00:43.19 | jerardepardieu | ~dnsmasq |
| 00:44.23 | *** part/#maemo jerardepardieu (~capitanoc@unaffiliated/capitanocrunch) |
| 00:51.14 | *** join/#maemo capitanocrunch (~capitanoc@host189-61-dynamic.41-79-r.retail.telecomitalia.it) |
| 00:51.15 | *** join/#maemo capitanocrunch (~capitanoc@unaffiliated/capitanocrunch) |
| 00:52.41 | *** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 01:01.23 | *** join/#maemo capitanocrunch (~capitanoc@host189-61-dynamic.41-79-r.retail.telecomitalia.it) |
| 01:01.23 | *** join/#maemo capitanocrunch (~capitanoc@unaffiliated/capitanocrunch) |
| 02:13.13 | *** join/#maemo Wizzup (~Wizzup@a82-161-36-93.adsl.xs4all.nl) |
| 02:54.05 | *** join/#maemo MIchael_a380 (d31f1b25@gateway/web/freenode/ip.211.31.27.37) |
| 03:00.37 | *** join/#maemo ravelo_ (ravelo@85.93.4.75) |
| 03:26.18 | *** join/#maemo spiiroin_ (~spiiroin@37-33-16-174.bb.dnainternet.fi) |
| 03:26.50 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 03:39.50 | MIchael_a380 | ~obsolete |
| 03:40.05 | MIchael_a380 | ~battery |
| 03:40.05 | infobot | extra, extra, read all about it, polarcell is http://www.ebay.co.uk/itm/390402445382 BL-5J Replacement |
| 03:40.46 | MIchael_a380 | ~deprecated |
| 03:40.46 | infobot | i heard deprecated is a term in computer software that indicates a feature is no longer officially supported even if it still exists and may eventually be removed altogether. Deprecated is often misspelled 'depreciated' which is a financial term. |
| 03:43.56 | MIchael_a380 | ~broken package |
| 03:44.17 | MIchael_a380 | ~pkg |
| 03:44.17 | infobot | somebody said pkg was http://maemo.org/packages/ |
| 03:58.45 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 03:59.06 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 04:01.55 | *** join/#maemo lxp1 (~lxp@unaffiliated/lxp) |
| 04:08.17 | MIchael_a380 | Found it :) http://wiki.maemo.org/Community_SSU/known_broken_packages |
| 04:15.56 | DocScrutinizer05 | ~listvalues known_broken_packages |
| 04:18.20 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 04:18.54 | DocScrutinizer05 | freemangordon: sorry, to open a ticket (aka 'create an issue') on github, I'd need an account which I don't have and don't want to start a browser compatible with the capchas and stuff they have there |
| 04:26.48 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 04:49.10 | *** join/#maemo Juesto (~Zilla@rev190-105-167-002.pccp.net.ar) |
| 05:03.10 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 06:37.04 | *** join/#maemo spiiroin_ (~spiiroin@2001:998:2a:dead:d8a6:11c2:94d3:3954) |
| 06:40.12 | *** join/#maemo arcean (~arcean@131.228.32.167) |
| 06:58.25 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 07:42.02 | *** join/#maemo Oksanaa (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 07:55.18 | *** join/#maemo spinal84 (~spinal@nat4-minsk-pool-46-53-176-225.telecom.by) |
| 08:00.06 | *** join/#maemo Wizzup (~Wizzup@a82-161-36-93.adsl.xs4all.nl) |
| 08:01.44 | *** join/#maemo jskarvad (~jskarvad@ip4-83-240-109-95.cust.nbox.cz) |
| 08:01.44 | *** join/#maemo jskarvad (~jskarvad@redhat/jskarvad) |
| 08:01.47 | Vajb | DocScrutinizer05: hmm i can't seem to find dbus-scripts from apmanager nor apt and besides all that looked a bit over my head atm. Thx for ur investigation i hope it'll make editting mce.ini to work as expected :) |
| 08:22.47 | *** join/#maemo BitEvil (~quassel@tor/regular/SpeedEvil) |
| 08:23.12 | *** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 08:26.24 | *** join/#maemo spinal84 (~spinal@nat4-minsk-pool-46-53-176-225.telecom.by) |
| 08:41.08 | *** join/#maemo xorly (~xorly@ip-89-176-102-19.net.upcbroadband.cz) |
| 08:48.56 | bencoh | freemangordon: have you ever tried libgoo/gstgoo (ti/omx api abstraction)? |
| 09:01.10 | *** join/#maemo spinal84 (~spinal@nat4-minsk-pool-46-53-176-225.telecom.by) |
| 09:03.54 | *** join/#maemo Kabouik (~kabouik@147.99.218.243) |
| 09:08.44 | *** join/#maemo jskarvad (~jskarvad@cst-prg-47-4.cust.vodafone.cz) |
| 09:12.11 | Oksanaa | Just had a bug (affecting only one channel in telepathy-idle, as far as I know) where my local_name ( and in outcoming messages, remote_uid ) was affected. Null at times, or wrong value at other times. No idea why. Cleaned it up is SQL database with two update commands, hoping all is well. |
| 09:33.37 | *** join/#maemo krnlyng (~liar@178.114.189.224.wireless.dyn.drei.com) |
| 10:02.46 | Vajb | DocScrutinizer05: i just realised that probably mediaplayer is overdriving mce.ini setting in that matter. |
| 10:03.28 | Vajb | because it needs to be playing something for volume keys to work |
| 10:04.09 | Vajb | while locked that is. I found dbus-script-settings and am trying with it on my test device |
| 10:15.18 | *** join/#maemo silviof (~silviof@unaffiliated/silviof) |
| 10:15.22 | bencoh | Vajb: most probably, yes |
| 10:15.34 | bencoh | I actually wanted to implement that behavior in other players :) |
| 10:16.07 | Vajb | hmm maybe while on it u can change it ;) |
| 10:16.20 | bencoh | because I find not being able to change volume when device is locked quite frustrating |
| 10:16.35 | Vajb | or maybe in next version of omp one can choose wether to disable or enable volume keys |
| 10:16.44 | Vajb | or even choose their behavior |
| 10:16.49 | bencoh | since unlocking it with systemui/powerbutton will stop playback for a second |
| 10:17.10 | bencoh | and same goes for devlock unlock UI |
| 10:17.18 | Vajb | yup, but with slider it is not stopped |
| 10:17.23 | bencoh | slider? |
| 10:17.26 | bencoh | lock switch? |
| 10:17.31 | Vajb | yes |
| 10:17.46 | bencoh | same with keyboard slider, if device doesn't need to enter code |
| 10:18.02 | bencoh | I'd like to fix that as well actually |
| 10:18.13 | Vajb | hmm for me playback is not interrupted with keybslider |
| 10:19.18 | bencoh | it is only if I need to enter code iirc |
| 10:19.23 | bencoh | (not sure about that one, though) |
| 10:24.31 | Vajb | ah with code it stops briefly |
| 10:26.50 | bencoh | yeah |
| 10:33.20 | *** join/#maemo jskarvad (~jskarvad@redhat/jskarvad) |
| 10:38.23 | *** join/#maemo Michael_a380 (d31f1b25@gateway/web/freenode/ip.211.31.27.37) |
| 10:40.41 | *** join/#maemo N-Mi_ (~nicolas@LMontsouris-657-1-196-48.w90-63.abo.wanadoo.fr) |
| 10:54.32 | *** join/#maemo Oksanaa (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 11:12.25 | Vajb | ok tried with dbus-script-settings and it did nothing :) |
| 11:12.38 | Vajb | guess i lack the know how |
| 11:12.59 | Vajb | easiest for me would be to disable it with epoxy |
| 11:19.06 | *** join/#maemo pipoclown (~henk@melange.soleus.nu) |
| 11:21.24 | *** join/#maemo dreamer (~henk@unaffiliated/dreamer) |
| 11:59.25 | *** join/#maemo robink (~quassel@unaffilated/robink) |
| 12:05.36 | KotCzarny | vajb: or maybe.. use one of the other players available? *hinthint* |
| 12:08.22 | Vajb | oh a fresh aproach :) |
| 12:14.35 | *** join/#maemo N-Mi_ (~nicolas@LMontsouris-657-1-196-48.w90-63.abo.wanadoo.fr) |
| 12:16.04 | KotCzarny | :) |
| 12:16.45 | KotCzarny | physical abuse to poor n900 because some software doesnt have a proper option seems excessive |
| 12:19.31 | Vajb | well i didn't say i will do it, but that it would be easiest solution ;) |
| 12:20.32 | Vajb | i think best would be option in player to choose wether to disable volume or to use it for some other thing |
| 12:21.00 | *** join/#maemo xorly (~xorly@ip-89-176-102-19.net.upcbroadband.cz) |
| 12:21.01 | KotCzarny | yeah, post to the thread then |
| 12:27.23 | Vajb | oh such a 2016 solution |
| 12:27.58 | Vajb | but maybe i will when i have some spare moment and can recall the problem. |
| 12:43.36 | KotCzarny | ok, record the video of your life-damaging issue, post on yt and every possible social site and expect problem to resolve itself. |
| 12:43.40 | KotCzarny | and give you pony. |
| 12:43.52 | KotCzarny | ;) |
| 12:44.04 | *** join/#maemo frals (~frals@c151-177-16-163.bredband.comhem.se) |
| 12:44.04 | *** join/#maemo frals (~frals@Maemo/community/contributor/frals) |
| 12:44.12 | KotCzarny | 2017 enough? |
| 12:59.06 | *** join/#maemo NeKit (~nekit@85-95-187-158.saransk.ru) |
| 13:14.09 | Vajb | :D |
| 13:14.54 | Vajb | now i begin to wonder if it is possible to upload video to yt from n900 |
| 13:20.56 | Vajb | KotCzarny: btw, laptop os working very well. With my typical use i haven't been able to make it stuck (which is good) so thx a lot for the hint! |
| 13:21.02 | Vajb | is* |
| 13:21.16 | KotCzarny | :) |
| 13:27.54 | *** join/#maemo xorly (~xorly@ip-89-176-102-19.net.upcbroadband.cz) |
| 13:43.08 | bencoh | Vajb: wanna dev a youtube-sharing-plugin? :> |
| 13:44.57 | KotCzarny | bancoh: authoring ;) |
| 13:47.27 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 13:50.29 | bencoh | KotCzarny: ? |
| 13:51.56 | KotCzarny | shoot, edit and upload own material = authoring |
| 13:54.10 | bencoh | ah, right |
| 14:02.48 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 14:07.38 | *** join/#maemo coderus (~coderus@static.10.21.201.138.clients.your-server.de) |
| 14:07.52 | coderus | TMO: The maemo.org - Talk database has encountered a problem. =( |
| 14:07.54 | *** part/#maemo coderus (~coderus@static.10.21.201.138.clients.your-server.de) |
| 15:05.54 | *** join/#maemo xkr47 (xkr47@2001:14b8:141:5926:5358:9793:2384:6264) |
| 15:42.32 | *** join/#maemo LauRoman (~LauRoman@5-14-51-107.residential.rdsnet.ro) |
| 16:06.05 | *** join/#maemo NeKit (~nekit@85-95-187-126.saransk.ru) |
| 16:10.57 | *** join/#maemo LauRoman (~LauRoman@5-14-51-107.residential.rdsnet.ro) |
| 16:14.24 | *** join/#maemo LauRoman (~LauRoman@5-14-51-107.residential.rdsnet.ro) |
| 16:18.54 | Vajb | KotCzarny: http://talk.maemo.org/showpost.php?p=1522133&postcount=1715 I did it and whats more i used microb. Failed with Opera first. |
| 16:21.58 | *** join/#maemo LauRoman (~LauRoman@5-14-51-107.residential.rdsnet.ro) |
| 16:22.53 | *** join/#maemo spiiroin_ (~spiiroin@37-33-16-174.bb.dnainternet.fi) |
| 16:28.37 | *** join/#maemo at1as (~at1as@2601:404:c600:c21f:9d8a:d2d5:6cb6:a210) |
| 16:37.53 | *** join/#maemo LauRoman (~LauRoman@5-14-51-107.residential.rdsnet.ro) |
| 16:45.42 | *** join/#maemo eMHa (~mh@p200300738E2D1500267703FFFE6CC360.dip0.t-ipconnect.de) |
| 16:51.51 | *** join/#maemo LauRoman (~LauRoman@5-14-51-107.residential.rdsnet.ro) |
| 17:01.11 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 17:13.32 | DocScrutinizer05 | Vajb: ((realised that probably mediaplayer is overdriving mce.ini)) good point. Needs further checking |
| 17:19.19 | Vajb | doc: just made feature request of the matter in omp thread in tmo. |
| 17:23.05 | DocScrutinizer05 | this is a architetural decision issue. |
| 17:28.55 | DocScrutinizer05 | any app *usually* receives input events via X11. However X11 usually doesn't send events to the app when it doesn't have focus (you see that with maemo medi aplayer which only works vol+/- when in foreground, which is basically correct behaviour). Now when you lock screen, X11 is supposed to also obey mce.ini settings regarding keypress events. However the concept of "X11 focus" makes no sense when screen locked - so an app like media |
| 17:28.56 | DocScrutinizer05 | player interested in keypress events when screen locked should probably open /dev/input itself and take *all* events it's interested in (here: vol+/-), and same app might make sure the /dev/input* delivers events so app may want to bind keypad kernel driver when device locked, to override what mce (right now doesn't) do |
| 17:31.57 | DocScrutinizer05 | this is a typical issue for getting handled by middleware managing resource allocations. mce does a very poor job on this, freeesmartphone.org has a more comprehensive and coherent concept for this, alas FSO isn't used in maemo |
| 17:33.37 | *** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net) |
| 17:33.51 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 17:34.54 | DocScrutinizer05 | see http://wiki.openmoko.org/wiki/FSO_Resources fsoraw (my invention ;-S ) |
| 17:35.02 | DocScrutinizer05 | ;-D even |
| 17:46.40 | DocScrutinizer05 | http://wiki.openmoko.org/wiki/FSO_Resources#Automatic_way particularly |
| 17:47.05 | DocScrutinizer05 | raw == resource allocation wrapper |
| 18:02.47 | DocScrutinizer05 | actually locking device shall put a screensaver (here: lockscreen) on top of all other windows and give X11 focus to it, even when immediately after the screen is shut off physically. So any keypress when device (screen) locked would only create X11 events delivered to the lockscreen process. Vol+/- should be a side channel (only while device locked?) via keypad->kerneldriver->/dev/input*->(hulda or )mce->dbus-signal to which an app like |
| 18:02.48 | DocScrutinizer05 | mediaplayer could listen |
| 18:04.31 | *** join/#maemo LauRoman (~LauRoman@5-14-51-107.residential.rdsnet.ro) |
| 18:05.01 | Juesto | that's a great approach |
| 18:05.14 | *** join/#maemo fuz_ (nobody@vau75-10-88-164-23-88.fbx.proxad.net) |
| 18:08.31 | DocScrutinizer05 | alas architecture, and arch is hard to change once a system got established |
| 18:10.55 | KotCzarny | vajb: good job! also tmo is one of the few sites actually checked to be usable on n900 ;) |
| 18:19.08 | *** part/#maemo Oksanaa (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 18:19.46 | timeless | hi DocScrutinizer05 |
| 18:19.56 | timeless | if you had a linux (md) raid array and were having trouble w/ it, what channel would you use to get help? :/ |
| 18:20.23 | DocScrutinizer05 | ugh |
| 18:20.33 | Juesto | try alis |
| 18:20.50 | Juesto | im sure theres a channel about raid somewhere |
| 18:20.56 | DocScrutinizer05 | #debian ? even #devuan maybe, or is there #linux-admin ? |
| 18:20.59 | Juesto | try ##linux first timeless |
| 18:21.48 | DocScrutinizer05 | timeless: I'd probably first check stackoverflow if some answers there |
| 18:21.59 | Juesto | oh yes, searching too ^ |
| 18:24.31 | DocScrutinizer05 | timeless: https://www.ixquick.com/do/search?q=stackoverflow+md+raid |
| 18:24.51 | timeless | http://stackoverflow.com/questions/41525921/ubuntu-mdadm-failed-array-cannot-get-replacement-drives-into-the-array |
| 18:24.56 | timeless | "Questions on professional server- or networking-related infrastructure administration are off-topic for Stack Overflow unless they directly involve programming or programming tools. You may be able to get help on Server Fault." â Mureinik, Mark Rotteveel |
| 18:26.22 | Juesto | ;) |
| 18:26.53 | timeless | http://serverfault.com/questions/180138/software-raid-mdadm-not-adding-spare |
| 18:26.59 | timeless | seems like a good match to my problem |
| 18:28.15 | DocScrutinizer05 | https://www.ixquick.com/do/search?q=stackexchange+md+raid |
| 18:28.31 | Vajb | oh boy. Had a good idea to putting telegram downloads folder to tracker, but since it not in MyDocs i couldn't reach it from tracker-cfg. Then i tried to make symlink in mydocs to point that folder, but that sems to be impossible too.. |
| 18:29.41 | DocScrutinizer05 | no symlinks on VFAT ;-P |
| 18:30.18 | timeless | DocScrutinizer05: none of those are helpful |
| 18:30.22 | DocScrutinizer05 | but I'm pretty sure you can index whatever you like, via tracker.cfg |
| 18:30.56 | DocScrutinizer05 | timeless: sorry then, good luck anyway |
| 18:34.57 | DocScrutinizer05 | timeless: #devuan is "de* Veteran Unix Admins n". maybe you find some veterans there that have a good advice |
| 18:35.13 | timeless | thx |
| 18:36.08 | DocScrutinizer05 | take care to not go too offensively off topic though. Not a general problem there but don't expect to be on topic with such question |
| 18:36.14 | Vajb | yeah learnt that :) |
| 18:36.49 | DocScrutinizer05 | timeless: also, reply time is within hours raher than minutes |
| 18:38.04 | DocScrutinizer05 | timeless: considered pinging warfare and/or xes, our maemo sysops? |
| 18:42.08 | timeless | is nick highlight (what you did) enough? |
| 18:44.11 | DocScrutinizer05 | warfare: ^^^ |
| 18:44.15 | DocScrutinizer05 | xes: ^^^ |
| 18:45.10 | DocScrutinizer05 | warfare: xes: md raid issue, maybe you can help? |
| 18:45.43 | DocScrutinizer05 | timeless: you probably should post a terse explanation resp question |
| 18:45.56 | timeless | can someone suggest a place to get help w/ an md raid array? I had a raid1 array (one partition mirrored on two drives), and one of the drive's cables came out -- i've tried to mdadm --manage /dev/md1 --add /dev/sdf7 the drive, and it rebuilds, but once it finishes rebuilding, it's converted into a spare instead of left as a normal drive |
| 18:45.59 | timeless | ^^ |
| 18:47.49 | DocScrutinizer05 | you looked into https://raid.wiki.kernel.org/index.php/RAID_setup ? |
| 18:49.02 | DocScrutinizer05 | https://raid.wiki.kernel.org/index.php/A_guide_to_mdadm |
| 18:49.53 | DocScrutinizer05 | sorry I'm no mdadm expert myself, just used those pages when setting up mine |
| 18:52.09 | DocScrutinizer05 | I *guess* you first need to switch the defective drive 'offline' somehow, the possibly format or rebuild or whatever, then simply online it again. *adding* a new (third) driver to a raid1 will probably result in exactly what you see, and needs reconfiguration of the raid setup to make the drive an active part of the raid |
| 18:53.42 | DocScrutinizer05 | don't bash me when that's nonsense, I just uttered wild guessing |
| 18:55.28 | DocScrutinizer05 | http://wstaw.org/m/2017/01/17/plasma-desktopU17764.png |
| 18:57.37 | KotCzarny | http://www.linuxquestions.org/questions/linux-server-73/mdadm-re-added-disk-treated-as-spare-750739/#post4936897 |
| 18:57.41 | KotCzarny | doesnt seem optimistic |
| 18:57.47 | KotCzarny | maybe some bug in mdadm |
| 19:00.35 | KotCzarny | maybe first disk also has a problem? |
| 19:01.05 | timeless | KotCzarny: yeah, i'm pretty sure i read that a while ago |
| 19:01.15 | timeless | and yeah, i was sorta nodding "yes, i'd go w/ zfs too" |
| 19:01.24 | timeless | KotCzarny: the first drive is failing, yes |
| 19:01.48 | KotCzarny | https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767243#15 |
| 19:01.52 | timeless | sda is failing https://www.irccloud.com/pastebin/j8byIHuF/ |
| 19:01.54 | KotCzarny | seems to also confirm this behavior |
| 19:02.33 | KotCzarny | corrected by brute force ;) |
| 19:02.45 | Maxdamantus | Actual RAID is silly. |
| 19:02.52 | KotCzarny | but probably some data will be lost |
| 19:02.59 | timeless | KotCzarny: that bts url looks promising |
| 19:03.12 | KotCzarny | make a backup |
| 19:03.13 | KotCzarny | ;) |
| 19:03.19 | timeless | Maxdamantus: yeah... i'm a fan of zfs. i'm not a fan of raid |
| 19:03.29 | timeless | it's more or less broken 7 ways to sunday, by design |
| 19:03.35 | timeless | but,... i inheritted this system |
| 19:03.44 | timeless | KotCzarny: thankfully (or not), this is the backup |
| 19:03.48 | KotCzarny | :) |
| 19:03.48 | Maxdamantus | You basically need a journal (preferably using really fast NVRAM) for it to be consistent. |
| 19:03.58 | timeless | literally, peach's only job in life is to hold backups of everything else |
| 19:03.59 | Maxdamantus | otherwise you have write holes in pretty much any configuration. |
| 19:07.03 | DocScrutinizer05 | timeless: ummm https://www.irccloud.com/pastebin/j8byIHuF/ looks like a hw defect on sda |
| 19:07.17 | timeless | nods |
| 19:08.24 | DocScrutinizer05 | so AIUI you should simply swap sda for a working HDD, assuming that you have intact data on e.g. sdb in a [sda sdb] raid1 |
| 19:09.37 | DocScrutinizer05 | make sure you (or rather md) don't overwite data on sdb with crap from fresh sda |
| 19:09.38 | timeless | so, is the argument that sda is bad and i was unlucky in that sdf fell out of the raid |
| 19:09.45 | KotCzarny | :) |
| 19:09.49 | timeless | there already are sdb..sde |
| 19:10.03 | DocScrutinizer05 | in a raid1? |
| 19:10.29 | DocScrutinizer05 | so you have a raid1 with 3 spares? |
| 19:10.36 | timeless | my raid hell https://www.irccloud.com/pastebin/jvbwumkt/ |
| 19:10.54 | timeless | b / e is a pair |
| 19:11.02 | timeless | c / d is a pair |
| 19:11.07 | DocScrutinizer05 | OH shit |
| 19:11.11 | timeless | a / f is an unhappy pair |
| 19:11.21 | timeless | because the stupid data cable fell out of f |
| 19:12.25 | DocScrutinizer05 | so you have FOUR raid1 on sda? |
| 19:12.29 | DocScrutinizer05 | on partitons |
| 19:13.25 | timeless | i think this is mostly "because linux" + "no zfs" |
| 19:13.25 | timeless | w/ zfs, in a pair, if one drive fails, your replace it w/ a bigger drive, then you let it mirror, then you replace the smaller drive, let it mirror, then you grow the pool |
| 19:13.25 | timeless | yes |
| 19:13.25 | timeless | but... i think "because linux" + "no zfs", it instead went "oh well, let's just create new partitions for each grow operation" |
| 19:13.32 | DocScrutinizer05 | that's pretty weird since your kernel logs hw IO error on sda, not sdf |
| 19:13.58 | timeless | sdf was just unlucky, loose cable |
| 19:14.04 | timeless | sda is probably a much older drive |
| 19:14.10 | timeless | if i were to guess |
| 19:14.17 | DocScrutinizer05 | smartmon sda |
| 19:14.18 | KotCzarny | timeless, your nick seems familiar, but i cant remember what project |
| 19:14.25 | timeless | Qt i think |
| 19:15.05 | timeless | based on my memory |
| 19:15.15 | timeless | but it's nearly 6 years ago now :/ |
| 19:15.23 | KotCzarny | :) |
| 19:15.27 | timeless | i touched pretty much everything |
| 19:15.34 | DocScrutinizer05 | microB |
| 19:15.38 | timeless | yeah that |
| 19:15.51 | timeless | plus ux + localization + bug help + community |
| 19:15.59 | DocScrutinizer05 | yeah, translations |
| 19:16.55 | DocScrutinizer05 | the still fuckedup "tana_fi_*" subject ;-P |
| 19:17.05 | timeless | looks for smartmon |
| 19:17.15 | DocScrutinizer05 | SMART |
| 19:17.21 | DocScrutinizer05 | you know SMART, do you? |
| 19:17.39 | *** join/#maemo esaym153 (~esaym153@75-1-182-8.lightspeed.snantx.sbcglobal.net) |
| 19:17.58 | timeless | yeah, i get email from smart every day complaining about sda dying on peach :( |
| 19:17.58 | KotCzarny | can you get that failing pair offline ? |
| 19:18.08 | DocScrutinizer05 | Self Monitoruing And Reporting Foo |
| 19:19.15 | DocScrutinizer05 | I *guess* md4 is SOL |
| 19:19.32 | timeless | DocScrutinizer05: installing smartmontools didn't give me a `smartmon` |
| 19:19.39 | DocScrutinizer05 | o.O |
| 19:19.41 | timeless | i still have `smartctl` and `smartd` (which i had before) |
| 19:19.51 | DocScrutinizer05 | aah yeah smartctl |
| 19:19.55 | KotCzarny | smart-notifier - graphical hard disk health status notifier |
| 19:19.59 | KotCzarny | maybe this one? |
| 19:20.09 | KotCzarny | though i dont know what doc wanted to do |
| 19:20.09 | KotCzarny | ;) |
| 19:20.12 | timeless | smartctl https://www.irccloud.com/pastebin/CxNAOOMm/ |
| 19:20.18 | KotCzarny | usually smartctl/hdparm is enough |
| 19:20.19 | DocScrutinizer05 | smartctl -a /dev/sda |
| 19:21.26 | timeless | ^ DocScrutinizer05 |
| 19:21.35 | DocScrutinizer05 | reading |
| 19:22.23 | timeless | runs badblocks on sda6 and sdf7 |
| 19:23.04 | KotCzarny | wd black went boo boo? oh well, nothing is safe anymore! :) |
| 19:23.12 | DocScrutinizer05 | Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error |
| 19:23.14 | DocScrutinizer05 | # 1 Short offline Completed: read failure 90% 27923 953187909 |
| 19:25.03 | DocScrutinizer05 | you got a bad sector at 953187909 |
| 19:25.07 | DocScrutinizer05 | I'd guess |
| 19:27.28 | DocScrutinizer05 | FWIW: (maybe just reference) http://paste.opensuse.org/95982284 |
| 19:28.08 | KotCzarny | https://bugs.maemo.org/show_bug.cgi?id=2368 |
| 19:28.10 | KotCzarny | :> |
| 19:28.10 | povbot | 04Bug 2368: -, timeless isn't nice |
| 19:28.25 | KotCzarny | resolved fixed ;) |
| 19:28.27 | timeless | nods |
| 19:28.52 | warfare | timeless: md issue fixed? (I don't want to read the whole backlog, I'm just lazy) |
| 19:29.16 | KotCzarny | warfare, raid1 doesnt rebuild with badblocks on only drive left |
| 19:29.20 | KotCzarny | just a quick summary |
| 19:29.31 | KotCzarny | unless you know how to ignore read errors |
| 19:30.00 | warfare | oO |
| 19:30.58 | KotCzarny | and i bet he has more lurking around on other drives too |
| 19:31.17 | DocScrutinizer05 | your damn /proc/mdstat puzzles hell outa me, by the indices [2] [3] etc |
| 19:31.46 | DocScrutinizer05 | https://www.irccloud.com/pastebin/jvbwumkt/ |
| 19:32.51 | DocScrutinizer05 | I always thought a raid1 had just [1],[0] (in that sequence) with [0] being 'master' |
| 19:33.16 | DocScrutinizer05 | I never tried to really learn what it actually is all about |
| 19:34.33 | DocScrutinizer05 | anyway one thing's for sure: you should do a dd if=/dev/sda of=whateverishugeenough; and then swap sda for a drive without smart errors |
| 19:35.43 | DocScrutinizer05 | warfare: sdf data cable fell off, seems md4 never recovers, prolly because of sda has IO errors since ages already |
| 19:35.44 | KotCzarny | ^ bad suggestion, dd_rescue is better, it wont break on read errors |
| 19:36.11 | warfare | (I won't start to question the use of partions for raid devices) |
| 19:36.24 | DocScrutinizer05 | neither :-P |
| 19:37.01 | timeless | DocScrutinizer05: not md4, md1 |
| 19:37.13 | timeless | warfare: inheritted crap |
| 19:37.28 | warfare | timeless: Ugh, good luck. |
| 19:37.36 | timeless | i'm pretty sure it's because the drives were replaced by bigger ones and the way the person grew the lv was by adding paired partitions |
| 19:38.36 | warfare | Can I recommend putting everything on 2 physical disks, put lvm on top and let lvm mirror the blocks? |
| 19:39.32 | warfare | timeless: But I think the data on md1 is gone. |
| 19:40.00 | DocScrutinizer05 | timeless: ((md1) makes sense with your smartmon result "IO error at 10%" |
| 19:40.31 | DocScrutinizer05 | 10% (the checked 10 remaining 90) is most likely in md1 |
| 19:40.32 | timeless | warfare: if i'm going to rebuild this stupid machine, there's no way i'm using md |
| 19:40.46 | timeless | my general preference is zfs/zpool |
| 19:41.03 | timeless | i know of 0 good arguments in favor of md or lvm |
| 19:41.06 | warfare | timeless: Please use freebsd for that :) |
| 19:41.11 | timeless | warfare: fine w/ me |
| 19:41.24 | timeless | i'm really agnostic |
| 19:41.32 | DocScrutinizer05 | veteran meeting ;-D |
| 19:41.42 | timeless | has used osx, osol, nexenta for zfs |
| 19:42.14 | timeless | installs devscripts |
| 19:42.16 | DocScrutinizer05 | waits for GeneralAntilles chiming in |
| 19:43.08 | DocScrutinizer05 | warfare: what do yiu use for offsite backup? I'm using duplicity right now, it sucks donkey balls |
| 19:43.28 | warfare | DocScrutinizer05: I just rsync the backuppc directory over. |
| 19:43.56 | DocScrutinizer05 | aaah ok, that requires a vull double up of HDD space |
| 19:44.02 | DocScrutinizer05 | full* |
| 19:45.10 | warfare | And everything else which is backup worthy is in a few dmg's on my home server which get copied to a hetzner host every week. |
| 19:45.23 | DocScrutinizer05 | BackupPC is nice but conceptually runs on backup target, while duplicity runs on source |
| 19:46.53 | DocScrutinizer05 | I guess you could run BackupPC on, and beackup, localhost. and possibly even to a sftp target, but... |
| 19:48.50 | DocScrutinizer05 | sometimes feels like knowing enough of IT and computers to eventually find a job as bricklayer |
| 19:49.13 | timeless | fwiw https://www.irccloud.com/pastebin/MjFaRZFC/badblocks-sda6-sdf7 |
| 19:49.24 | DocScrutinizer05 | it's frustrating when you know enough of a topic to start hating it |
| 19:49.38 | warfare | so sdf7 is actually ok? |
| 19:49.43 | timeless | yeah |
| 19:49.50 | timeless | sdf was just unlucky wrt the data cable |
| 19:49.57 | timeless | it's sda that's failing |
| 19:50.07 | KotCzarny | maybe you can get lucky if you move those bad sectors to sda? |
| 19:50.16 | timeless | ? |
| 19:50.20 | DocScrutinizer05 | so it can't rebuild the logically broken sdf |
| 19:50.34 | DocScrutinizer05 | from physically broken sda |
| 19:50.36 | KotCzarny | hdparm --write-sector would force badblock reallock |
| 19:50.45 | timeless | KotCzarny: got a specific command |
| 19:50.49 | timeless | (otherwise i'll read the man page) |
| 19:50.56 | KotCzarny | its in that bts ticket |
| 19:51.02 | timeless | ah yeah :) |
| 19:51.30 | KotCzarny | but dont confuse sda sector with relative sda6 rector |
| 19:51.35 | DocScrutinizer05 | I seen same "cannot reallocate bad blocks" on my sdb (now nuked) |
| 19:51.56 | timeless | KotCzarny: err |
| 19:52.11 | DocScrutinizer05 | yeah, https://www.irccloud.com/pastebin/MjFaRZFC/badblocks-sda6-sdf7 usn't in line with LBA on smartctl log |
| 19:52.28 | timeless | so, since the sectors were reported by badblocks for sda6 |
| 19:52.48 | DocScrutinizer05 | you should write to sda6 |
| 19:52.56 | KotCzarny | you can also try to find out what file occupies those sectors |
| 19:53.08 | timeless | KotCzarny: ooh, i like that idea |
| 19:53.09 | KotCzarny | and maybe redo the specific backup only |
| 19:53.09 | timeless | how? :) |
| 19:53.17 | KotCzarny | what fs? extX ? |
| 19:53.24 | timeless | i think the answer is "lvm" |
| 19:53.28 | KotCzarny | nah |
| 19:53.45 | KotCzarny | oh, raw backup? |
| 19:53.54 | timeless | this is what the world looks like https://www.irccloud.com/pastebin/axU4eK7j/ |
| 19:55.01 | timeless | basically, /dev/md1 is one of the things backing VG peach-raid1 which in turn backs LV peach-sys-backups which in turn backs |
| 19:55.12 | KotCzarny | o.O |
| 19:55.13 | DocScrutinizer05 | blkid |
| 19:55.18 | timeless | ext3 /backups |
| 19:55.37 | timeless | a maze of twisty hell... because someone couldn't be bothered to use ZFS... "because linux" |
| 19:56.12 | DocScrutinizer05 | **make a full backup of sda first!** |
| 19:56.15 | timeless | blkid https://www.irccloud.com/pastebin/k4sfXJMV/ |
| 19:56.27 | timeless | that's helpful |
| 19:56.34 | KotCzarny | well, you can try hdparm --read-block 104846128 and GUESS |
| 19:57.54 | timeless | KotCzarny: got a syntax for that? |
| 19:58.05 | timeless | all i see in hdparm is --read-sector |
| 19:58.25 | DocScrutinizer05 | read man hdparm! it's a very dangerous tool |
| 19:58.26 | KotCzarny | hdparm --read-block 104846128 /dev/sda6 |
| 19:58.39 | KotCzarny | it will dump the sector on the screen |
| 19:58.57 | timeless | no. https://www.irccloud.com/pastebin/K24oqE17/ |
| 19:59.13 | KotCzarny | read-sector then |
| 19:59.14 | DocScrutinizer05 | ((blkid)) full list (no parameters) would be even more helpful ;-) |
| 19:59.15 | KotCzarny | :) |
| 19:59.37 | timeless | cute https://www.irccloud.com/pastebin/Clsp7XFG/ |
| 20:00.07 | timeless | goes to try to figure out what the hex says https://www.irccloud.com/pastebin/K9rTDp1q/ |
| 20:00.31 | DocScrutinizer05 | ((cute)) HAHA indeed ;-P |
| 20:01.06 | KotCzarny | mysterious |
| 20:01.27 | DocScrutinizer05 | honestly, go make a dd_rescure backup of sda6! |
| 20:01.50 | KotCzarny | doc, its not that easy, its a part of live structure |
| 20:02.50 | DocScrutinizer05 | umount is your friend |
| 20:03.30 | DocScrutinizer05 | and even without, how high is the risk to backup totally harbled data |
| 20:03.38 | DocScrutinizer05 | garbled |
| 20:03.54 | DocScrutinizer05 | prolly zilch as long as you remount ro |
| 20:04.12 | DocScrutinizer05 | or simply don't write (noatime!) |
| 20:05.18 | DocScrutinizer05 | you even can do a simple tar backup on logical files of md1 |
| 20:05.37 | DocScrutinizer05 | you can see the errors pop up in syslog then |
| 20:06.10 | DocScrutinizer05 | and with a tad of luck you can identify the badblock-riddled files |
| 20:07.31 | KotCzarny | funny thing is that, when backup fails or is taken down for maintenance it's probably the time when backup restore would be needed |
| 20:07.35 | DocScrutinizer05 | actually the latter is roughly what I did when my sdb blew chunks, got me a raid1 and copied all files over |
| 20:07.43 | KotCzarny | can you duplicate backups to another source? |
| 20:08.02 | KotCzarny | s/source/destination/ |
| 20:10.46 | timeless | so, the problem is that this is a fragment of a VG which is part of a LV |
| 20:11.01 | timeless | i think i could remove sda6 and try adding sdf7 |
| 20:11.20 | DocScrutinizer05 | ??? |
| 20:11.38 | warfare | timeless: this could actually work. |
| 20:12.15 | DocScrutinizer05 | aren't both _already_ added to md1? |
| 20:12.27 | KotCzarny | sdf7 isnt active |
| 20:12.36 | timeless | got a command? |
| 20:12.39 | timeless | ... https://www.irccloud.com/pastebin/FhMubmPl/ |
| 20:12.40 | *** join/#maemo DrCode (~DrCode@5.28.134.3) |
| 20:12.49 | timeless | device busy https://www.irccloud.com/pastebin/DeGtG6uK/ |
| 20:13.06 | timeless | KotCzarny: hrm, would it help if i unmounted the LV? |
| 20:13.30 | KotCzarny | maybe |
| 20:13.45 | DocScrutinizer05 | timeless: why do you want to remove drives from a md? |
| 20:13.53 | DocScrutinizer05 | or add? |
| 20:13.58 | warfare | mdadm --manage /dev/md1 --remove /dev/sdf7 |
| 20:14.06 | KotCzarny | but question is, can you take whole lv offline? |
| 20:14.47 | warfare | More interesting might be if linux recognizes the pv signature on the drive. |
| 20:14.56 | DocScrutinizer05 | aiui a md would still try to function as good as possible even when one drive blows chunks |
| 20:15.28 | timeless | warfare: that worked |
| 20:15.35 | timeless | but it left me w/ the sda6 which is the failed drive |
| 20:15.39 | timeless | can i mark it as failed? :) |
| 20:15.52 | timeless | actually, maybe that's what i should do |
| 20:15.57 | DocScrutinizer05 | a totally uneducated guess: I'd try to assemble md1 like it originally was, and do a backup of it |
| 20:16.09 | warfare | mdadm --manage /dev/md1 --fail /dev/sda6 |
| 20:16.21 | KotCzarny | timeless, mount |grep /dev/md1 ? |
| 20:16.22 | timeless | mdadm: set device faulty failed for /dev/sda6: Device or resource busy |
| 20:16.26 | DocScrutinizer05 | *now* we're talking :-) |
| 20:16.53 | warfare | KotCzarny: /dev/md1 might be a pv, being part of a vg with parts of a lv on it.. |
| 20:17.07 | timeless | KotCzarny: as noted, [sda6+sdf7] contribute to md1 which contributes to an PG which contributes to an LV which is ext3 |
| 20:17.19 | timeless | something like what warfare said |
| 20:17.23 | timeless | all "because linux" |
| 20:17.36 | KotCzarny | then if you want to take it offline whole thing would need to go offline? |
| 20:17.37 | DocScrutinizer05 | no, because ENOBRAIN |
| 20:17.39 | timeless | so wants to shoot this system and replace it w/ fbsd + zfs in the cloud |
| 20:17.56 | KotCzarny | and that's why i asked if it can go offline |
| 20:18.23 | timeless | KotCzarny: oh, "yes, there's nothing wrong w/ taking the whole thing offline" |
| 20:18.27 | KotCzarny | then you can try zeroing the sectors, maybe copying them from sdf drive and all will be peachy |
| 20:18.43 | DocScrutinizer05 | timeless: why not start with genuine md1, untweked and then see what it reports? |
| 20:18.49 | KotCzarny | or you can just say the whole thing failed and experiment on it ;) |
| 20:19.03 | timeless | DocScrutinizer05: eh?? |
| 20:19.40 | DocScrutinizer05 | you --remove'd and --add'ed drives to md1. Maybe try original productive assembly first? |
| 20:19.45 | DocScrutinizer05 | if that makes any sense |
| 20:20.37 | timeless | ok, i'm wrong |
| 20:20.37 | DocScrutinizer05 | or doesn't it 'come up' anymore? |
| 20:20.42 | timeless | i can't take this thing offline |
| 20:20.58 | timeless | there are two LVs (root and backup) but they share a VG |
| 20:21.13 | DocScrutinizer05 | OUCH!! |
| 20:21.44 | timeless | really really really really wants to shoot this configuration |
| 20:21.48 | DocScrutinizer05 | don't shoot the system, shoot the admin who committed that crime, possibly using the system as projectile |
| 20:22.06 | KotCzarny | you know what they say about horse with broken leg |
| 20:22.13 | KotCzarny | ;) |
| 20:22.30 | KotCzarny | if you have time you can check for files that fail to read |
| 20:22.32 | DocScrutinizer05 | timeless: what's the total storage size? |
| 20:22.41 | timeless | ~5TB ? |
| 20:22.53 | DocScrutinizer05 | timeless: can't you simply get a few HDD and copy the whole shite to sth sane? |
| 20:22.55 | timeless | err, maybe ~4.5TB? |
| 20:22.58 | KotCzarny | more resource consuming but otherwise you would have to solve the lv puzzle |
| 20:23.08 | KotCzarny | sure, why not, you are going to bed anytime soon? |
| 20:23.23 | timeless | it's 3pm |
| 20:23.35 | timeless | i don't have any 5TB drives handy |
| 20:23.45 | DocScrutinizer05 | then don't rush this |
| 20:23.57 | KotCzarny | find . -type f -exec cat {} >/dev/null \; |
| 20:23.57 | DocScrutinizer05 | not worth the headache |
| 20:23.58 | KotCzarny | ;) |
| 20:24.14 | DocScrutinizer05 | sth like that, yes |
| 20:24.17 | KotCzarny | maybe do some error redirect to catch the failing file |
| 20:24.56 | KotCzarny | i wonder how that raid would react on badblock during read though |
| 20:25.25 | DocScrutinizer05 | isn't that what a raid genuinely is about, to handle it |
| 20:25.49 | DocScrutinizer05 | it will try to read same block from sdf7 |
| 20:26.09 | DocScrutinizer05 | that's why I suggested to start with productive assembly of md1 |
| 20:27.22 | DocScrutinizer05 | when BOTH sdf7 and sda6 fail with read error (or 'block not synced on mirror') on same block, then I suppose md driver will throw normal read error to userland |
| 20:27.35 | timeless | DocScrutinizer05: sorry, you've lost me |
| 20:27.44 | timeless | what command would i use to assemble this stupid thing in a way that works |
| 20:28.00 | timeless | i'm pretty sure the goal is to have sdf7 sda6 instead of sda6 sdf7 |
| 20:28.03 | DocScrutinizer05 | what does system use during boot? |
| 20:28.05 | timeless | although i have no idea if i can even do that |
| 20:28.36 | timeless | i can't remember, it probably went into maintenance mode |
| 20:28.56 | DocScrutinizer05 | that's relevant info |
| 20:29.01 | KotCzarny | timeless, hdparm --write-sector on sda6 would zero the badblocks (and data) and will allow for rebuild probably |
| 20:29.17 | DocScrutinizer05 | or kill more blocks |
| 20:29.27 | DocScrutinizer05 | when you failed to guess right block |
| 20:29.33 | timeless | DocScrutinizer05: is there an easy way for me to check dmesg/syslog to confirm? |
| 20:29.42 | timeless | ponders |
| 20:29.45 | timeless | <PROTECTED> |
| 20:30.01 | timeless | i don't have syslog going back that far |
| 20:30.05 | DocScrutinizer05 | hmm, err. less /var/log/messages? |
| 20:30.15 | DocScrutinizer05 | cat /etc/fstab? |
| 20:30.20 | DocScrutinizer05 | I'm not sure |
| 20:30.32 | timeless | https://www.irccloud.com/pastebin/rYywcTJq/fstab |
| 20:30.44 | timeless | i'm pretty sure /backups came up as readonly |
| 20:30.54 | timeless | and / and /boot were fine |
| 20:31.05 | DocScrutinizer05 | https://raid.wiki.kernel.org/index.php/A_guide_to_mdadm#Assembling_your_arrays |
| 20:31.07 | timeless | ok, i have /var/log/messages |
| 20:31.20 | timeless | DocScrutinizer05: sorry |
| 20:31.25 | KotCzarny | isnt there a typo in that fstab? |
| 20:31.29 | KotCzarny | 01 instad of 0 1 ? |
| 20:31.33 | timeless | i've read those stupid pages. and they're utterly useless |
| 20:31.36 | inz | somehow i misread mdadm as madman |
| 20:31.48 | timeless | inz: seems like a good reading in my book |
| 20:32.13 | timeless | KotCzarny: that's a tab that got elided, dunno how/why |
| 20:32.52 | DocScrutinizer05 | I have no idea who, when, how does assemble md during boottime |
| 20:33.14 | timeless | minus the fact that the system is held together by ducttape, and is failing, the system has a configuration that would otherwise work |
| 20:35.18 | KotCzarny | nuke those badblocks and hope for the best |
| 20:35.21 | KotCzarny | ;) |
| 20:35.51 | KotCzarny | and shedule backups as soon as you can after rebuild |
| 20:36.00 | timeless | KotCzarny: it's a backup drop system |
| 20:36.09 | timeless | there's not much to backup, where would i back it up? |
| 20:36.12 | timeless | backup-of-backup? |
| 20:36.21 | DocScrutinizer05 | I think https://raid.wiki.kernel.org/index.php/Replacing_a_failed_drive is not useless |
| 20:36.24 | KotCzarny | then shedule backups redrop |
| 20:36.27 | KotCzarny | :) |
| 20:37.40 | DocScrutinizer05 | >>...if the array is in trouble, then you want to --replace a drive if possible...<< |
| 20:38.15 | KotCzarny | that's assuming sdf7 is holding correct data |
| 20:38.21 | KotCzarny | if not, sorry |
| 20:39.42 | DocScrutinizer05 | when your data cable fell off, you plug it in again and *AIUI* md should recover the drive in background, after next boot the latest |
| 20:40.30 | timeless | DocScrutinizer05: so... the question is how to get this moving |
| 20:40.48 | timeless | i think i'd need to not have sda plugged in otherwise i think i end up in this state again |
| 20:41.15 | KotCzarny | start building new system and migrate |
| 20:41.33 | DocScrutinizer05 | what *is* 2this state"? |
| 20:42.23 | DocScrutinizer05 | hoenstly, does the system still boot? does the raid come up? what's the status of the raid after boot? |
| 20:42.54 | timeless | the /backups mount was readonly |
| 20:42.59 | timeless | (because sdf was missing) |
| 20:43.19 | DocScrutinizer05 | why is it missing? you re-plugged the cable I assume |
| 20:44.18 | timeless | i hadn't rebooted since plugging in the cable |
| 20:44.21 | timeless | and i'm going to scream |
| 20:44.43 | DocScrutinizer05 | ooooh |
| 20:44.50 | KotCzarny | then sdf7 holds proper copy still, not bad |
| 20:45.00 | DocScrutinizer05 | oh well, you can't expect a HDD work that you hotplugged |
| 20:45.01 | timeless | i was trying to get the system back online by poking the pieces |
| 20:45.01 | KotCzarny | what happens if sda6 goes missing? |
| 20:45.15 | timeless | KotCzarny: right now? dunno |
| 20:45.19 | timeless | but how can i get it to do that? |
| 20:45.26 | timeless | md won't let go of it |
| 20:45.35 | KotCzarny | i've though of .. plugging the cable ;) |
| 20:45.41 | DocScrutinizer05 | actually you're lucky when it didn't break physcally on hotplug (less likely on SATA but anyway) |
| 20:45.45 | timeless | there are 6 stupid HDDs in this system |
| 20:45.56 | timeless | and there's *no* way to find out which stupid drive is on which port |
| 20:46.05 | timeless | "because linux" |
| 20:46.18 | timeless | which means figuring out which cable to pull for sda is non-trivial |
| 20:46.18 | DocScrutinizer05 | o.O |
| 20:46.20 | KotCzarny | dd </dev/sda >/dev/null and touch which one is clicking |
| 20:46.31 | timeless | KotCzarny: yeah yeah |
| 20:46.48 | timeless | but i mean.... seriously |
| 20:46.52 | DocScrutinizer05 | o.OYOU DON NOT WANT to pull or plug cables on a powered system!!!! |
| 20:47.00 | timeless | ignore that |
| 20:47.01 | KotCzarny | he already did, on sdf |
| 20:47.02 | KotCzarny | ;) |
| 20:47.10 | timeless | it isn't easier when the thing is off |
| 20:47.22 | timeless | i mean, sure, i can ask each drive "what's your serial number" |
| 20:47.30 | DocScrutinizer05 | no, just healthier for the hardware |
| 20:47.32 | timeless | and then i can unscrew each drive from its bay and try to compare |
| 20:47.37 | timeless | but, gosh, this is insane. |
| 20:47.46 | DocScrutinizer05 | but WHY?? |
| 20:47.49 | KotCzarny | i was just joking anyway |
| 20:47.49 | timeless | ok, debian people |
| 20:48.01 | timeless | what's the proper way to tell dpkg "yes i want to install x" |
| 20:48.09 | KotCzarny | dpkg -i |
| 20:48.29 | KotCzarny | i think dpkg ignores dependencies? |
| 20:48.30 | DocScrutinizer05 | honestly you ought reboot system ASAP |
| 20:48.57 | KotCzarny | it's the apt-get that checks them |
| 20:49.05 | DocScrutinizer05 | your raid sufgfered severe impact from cable break and any further action on that system will further degrade the raid |
| 20:49.57 | DocScrutinizer05 | you can't reasonably fuzz around with mdadm when your SATA driver didn't initialize the sdf |
| 20:50.14 | DocScrutinizer05 | that's madness |
| 20:50.59 | DocScrutinizer05 | dd if=/dev/sdf of=/dev/null count=1 |
| 20:51.21 | DocScrutinizer05 | for a first very basic sanity check, that already most likely will fail |
| 20:52.31 | DocScrutinizer05 | so REBOOT! |
| 20:53.28 | timeless | KotCzarny: Do you want to continue? [Y/n] |
| 20:53.33 | timeless | ^ that stupid prompt came from dpkg -i |
| 20:54.02 | DocScrutinizer05 | can't you do that after reboot? |
| 20:54.23 | timeless | !? |
| 20:54.29 | timeless | i have two headaches |
| 20:54.32 | timeless | 1. peach |
| 20:54.39 | timeless | 2. installing some debs on unrelated systems |
| 20:54.42 | timeless | 2 is more important |
| 20:54.46 | DocScrutinizer05 | aaah |
| 20:54.47 | timeless | peach has been broken for a while |
| 20:54.48 | KotCzarny | timeless, what is the issue ? bad signatures or something more? |
| 20:55.03 | timeless | KotCzarny: just looks like it wants to confirm |
| 20:55.09 | DocScrutinizer05 | is out |
| 20:55.13 | KotCzarny | ahm, so you want batch mode? |
| 20:55.30 | timeless | yes |
| 20:56.14 | KotCzarny | there are multiple --force-xx options |
| 20:56.25 | KotCzarny | it might ask about something more than just confirm |
| 20:56.27 | timeless | actually, maybe this is apt |
| 20:56.31 | KotCzarny | :) |
| 20:57.02 | KotCzarny | <PROTECTED> |
| 20:57.20 | KotCzarny | you can also --assume-no |
| 20:57.31 | KotCzarny | if something unexptected happens |
| 20:58.16 | KotCzarny | but generally -y is what you want |
| 20:59.11 | DocScrutinizer05 | timeless: http://serverfault.com/questions/5336/how-do-i-make-linux-recognize-a-new-sata-dev-sda-drive-i-hot-swapped-in-without |
| 21:00.49 | timeless | DocScrutinizer05: interesting reading |
| 21:01.14 | DocScrutinizer05 | however reboot strongly recommended |
| 21:02.20 | DocScrutinizer05 | you not only removed data cable, you also devalidated the driver's buffers for that drive. So simply replugging for sure won't work |
| 21:03.07 | DocScrutinizer05 | the kernel needs to re-initialize the whole drive |
| 21:03.27 | DocScrutinizer05 | and before that happened, no md will use that drive |
| 21:04.03 | DocScrutinizer05 | afk for good now, good luck! :-) |
| 21:04.58 | *** join/#maemo kgu (~kgu@new.freebox.dk) |
| 21:05.56 | KotCzarny | http://serverfault.com/questions/510895/find-file-by-block-number-on-ext3-fs-on-lvm |
| 21:06.33 | KotCzarny | i hope you are good with maths |
| 21:10.34 | *** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net) |
| 21:11.23 | *** join/#maemo Birchy (~Birchy@178-164-108.52.3p.ntebredband.no) |
| 21:39.51 | DocScrutinizer05 | http://serverfault.com/questions/645862/when-does-a-raid-restore-redundancy-after-a-broken-sector-is-flagged-as-defectiv |
| 21:48.40 | DocScrutinizer05 | >>...Instead, it reported the surrounding 8k stripe of data to be a stripe of zeroes and the read operation to be successful. [...] vendor's customer support even stated this to be perfectly acceptable, as RAID were to recover from full disk failure only and not handling the failure of individual blocks<< ROTFL BWAHAHAHAHA |
| 22:11.34 | *** join/#maemo ravelo (ravelo@neo900/community/supporter/ravelo) |
| 22:13.05 | *** join/#maemo pagurus (~user@p4FDC3A6F.dip0.t-ipconnect.de) |
| 22:49.49 | bencoh | 22:46 < DocScrutinizer05> o.OYOU DON NOT WANT to pull or plug cables on a powered system!!!! |
| 22:50.03 | bencoh | actually, that just works on well-behaving sata controllers |
| 22:52.41 | DocScrutinizer05 | for sure not, at *minimum* a umount is needed prior to unplug |
| 22:54.45 | DocScrutinizer05 | and definitely an unplug and replug of a device will not go unnoticed by system, however system refuses to simply accept newdev==olddev, rather it invalidates all handles to old dev and detects a all_new newdev |
| 22:55.05 | DocScrutinizer05 | if it detects any new device without a kick into the butt |
| 22:55.13 | *** join/#maemo M4rtinK (~M4rtinK@ip-78-45-144-165.net.upcbroadband.cz) |
| 22:55.48 | DocScrutinizer05 | heck, you're not even supposed to unplug a USB memstick without prior "removve safely" |
| 22:58.27 | DocScrutinizer05 | and fixing a pathological state of sdf that's caused by inadvertent mate round, by unplugging another drive from same raid - that doesn't sound like it has any chances for a happy ending |
| 23:01.31 | Maxdamantus | On a proper filesystem, you should be able to unplug the drive and not have the filesystem in an invalid state (you might lose the last few modifications you did though) |
| 23:02.13 | Maxdamantus | ext supposedly kind of behaves like that if you have -o data=ordered or the option that journals everything |
| 23:02.50 | DocScrutinizer05 | it rather sounds like "I opened right clothespin and now the cloth isn't straight anymore. Let me open left pin to fix it" |
| 23:03.04 | Maxdamantus | (usually only metadata is journalled, so the filesystem itself would still be consistent, but the contents of files might end up in a state you never actually put them intoâunless you're ordering data writes) |
| 23:04.54 | Maxdamantus | There is a reason that Linux has things like write barriers that interact with NCQ, etc |
| 23:06.50 | KotCzarny | its a raid |
| 23:06.54 | KotCzarny | it has to rebuild |
| 23:07.18 | KotCzarny | usual 'umount' rules are a bit different here |
| 23:09.25 | DocScrutinizer05 | yes |
| 23:10.08 | M4rtinK | shouldn't you be fine as long as you made sure to fsync the write & fsync returned before you yanked the drive out ? |
| 23:10.36 | DocScrutinizer05 | [2017-01-18 Wed 00:03:07] <timeless> anyway, it booted and has decided that sda6 is "failed" and it seems to be trying to use sdf7 as the primary |
| 23:10.37 | DocScrutinizer05 | [2017-01-18 Wed 00:03:15] <timeless> it was around 5% through the process when i last visited it |
| 23:12.04 | DocScrutinizer05 | raid is about safety net when errors occur in a drive, it's not exactly about plug&pray drive hotswap |
| 23:12.23 | timeless | shrugs |
| 23:12.33 | timeless | this system's configuration is about hell |
| 23:12.38 | timeless | or at least a rat's nest |
| 23:12.45 | timeless | turns to MAIN_TLS_CERTKEY |
| 23:12.47 | DocScrutinizer05 | you probably usually can hotswap fix a borked drive of raid, but you need to follow a certain procedure for this to work |
| 23:13.30 | *** join/#maemo pagurus (~user@p4FDC3A6F.dip0.t-ipconnect.de) |
| 23:14.34 | DocScrutinizer05 | M4rtinK: yep, usually sync is the most problematic issue when _not_ done |
| 23:15.09 | M4rtinK | the you basically get what you wanted |
| 23:15.17 | M4rtinK | speed > consistency |
| 23:15.41 | M4rtinK | it's actually a pretty good tradeoff in some cases |
| 23:15.59 | M4rtinK | like when building packages in a changeroot or installing a system |
| 23:16.10 | KotCzarny | o.O |
| 23:16.13 | M4rtinK | in both cases you only care about the end result |
| 23:16.22 | KotCzarny | why would you want inconsistent system? |
| 23:16.24 | M4rtinK | and want it to be done as fast as possible |
| 23:16.46 | M4rtinK | well, it the system installation does not run to end for any reason |
| 23:16.57 | M4rtinK | it will be most probably broken anyway |
| 23:17.06 | DocScrutinizer05 | lost the thread now |
| 23:17.12 | KotCzarny | it might be quiet corruption |
| 23:17.26 | M4rtinK | if it *does* run to end you of course call fsync & make sure all cached fs data end on the disk |
| 23:18.11 | DocScrutinizer05 | you meant sync, not fsync |
| 23:18.24 | M4rtinK | yeah |
| 23:18.45 | M4rtinK | basically ignoring forced backing storage writes |
| 23:19.42 | M4rtinK | so stuff the application things is safely on backing storage might actually still be in cache in ram somewhere |
| 23:21.06 | DocScrutinizer05 | thus `man 8 umount` |
| 23:21.22 | DocScrutinizer05 | which obviously doesn't really work with md |
| 23:22.55 | DocScrutinizer05 | without umount (or equivalent) however you can't be sure there's no dirty buffer pending to get written to the device, even when you did a sync 1 second ago |
| 23:23.57 | DocScrutinizer05 | which is the point about "safely remove" |
| 23:24.46 | DocScrutinizer05 | didn' |
| 23:24.55 | DocScrutinizer05 | t read except headline: http://knowledge.seagate.com/articles/en_US/FAQ/192211en |
| 23:25.56 | DocScrutinizer05 | http://unix.stackexchange.com/questions/290336/safely-remove-usb-from-linux-device more on topic |
| 23:44.04 | DocScrutinizer05 | anyway, is there a command to find the file that's using a certain block/sector, on a plain ext3 HDD? |
