| 08:10 | jnettle | 08:10 * jnettlet is back. |
| 08:10 | jnettlet | stupid freenode crashing my bouncer. |
| 10:19 | Exaga | morning jnettlet lol |
| 10:19 | jnettlet | morgen |
| 10:22 | Exaga | what's your take on the clearfog jnettlet ? |
| 10:23 | jnettlet | Exaga, it is really fast. Throughput is just crazy good. Needs more work regarding idle power consumption |
| 10:23 | Exaga | excellent :> |
| 10:23 | jnettlet | docs should be released soon, so will be another open platform |
| 10:24 | jnettlet | working on cool features like the ability to flash images using a chrome extension :) |
| 10:24 | Exaga | oh nice |
| 10:26 | jnettlet | definitely like that the expansion headers can be configured to be either mini pcie, or msata...I should have that in u-boot this week. |
| 10:26 | jnettlet | this week has turned into my fun week in u-boot. I had to de-stress yesterday to prepare myself :) |
| 10:26 | Exaga | lol |
| 10:26 | Exaga | i have been there many times in the same position :D |
| 10:27 | jnettlet | but it already has decent upstream support, and will only get better once the docs are fully released. rmk added hotplug support for the sfp port |
| 10:28 | Exaga | then it's all good |
| 10:29 | Exaga | just from reading about the clearfog it is very impressive |
| 10:30 | jnettlet | but you get full gigabit everywhere, and you can saturate 3 SSDs at 540MB/s |
| 18:21 | topi` | I'm testing the sr-jessie-cli image on the HB Gate, what's the recommended way of displaying video on that image? |
| 18:22 | topi` | there's gst-launch-1.0 |
| 18:22 | jnettlet | topi`, yes that is the default |
| 18:22 | jnettlet | is there something specific you want to display? |
| 18:22 | topi` | good |
| 18:22 | topi` | just h.264 |
| 18:24 | jnettlet | then the default video playback should be fine for you. |
| 18:25 | jnettlet | topi`, all three video sinks should work and be vsync'd with the current plugins. |
| 18:28 | topi` | I'll do some testing :) |
| 18:33 | topi` | gst-launch taking 22% cpu, this is on the i.mx solo |
| 18:33 | topi` | but the video output looks good |
| 18:34 | topi` | next thing. Which X server should I run to get accelerated 2D graphics? like for running a web browser. |
| 18:34 | topi` | we have an "infoscreen" application which actually is a browser + local web "proxy" |
| 18:34 | topi` | not made by me, but I need to get it running on the HB :) |
| 18:36 | topi` | Artox: is this image your handiwork? I didn't know you were employed by SR. |
| 18:41 | topi` | searching with apt-cache... is this the right X server/driver? |
| 18:41 | topi` | xserver-xorg-video-imx-viv - |
| 18:43 | topi` | xserver-xorg-core : Depends: xserver-common (>= 2:1.16.4-1imx1) but it is not going to be installed |
| 18:43 | topi` | broken dependencies make me sad :( |
| 18:45 | jnettlet | topi`, I still need to fix some problems with the Freescale provided 2d driver. It has some rendering issues, missing a cache flush somewhere. |
| 18:46 | jnettlet | Artox, is doing our package and build management now |
| 18:46 | topi` | ok |
| 18:47 | jnettlet | what is your timeline for needing working Xorg? FYI, wheezy still works fine. |
| 18:47 | topi` | OK. well, our internal target is to ship with jessie, and we have already shipped one customer with jessie (running on x86 hw) |
| 18:48 | topi` | my colleague just placed the order for a bath of HB's, so it'll take 2-3 weeks until they are here, so there's plenty of time to fix issues ;) |
| 18:48 | topi` | batch, not bath |
| 18:48 | topi` | I wonder how it would feel to have a bath of HB's, like Uncle Scrooge ;) |
| 18:48 | jnettlet | okay, it is on my list. If you haven't heard from me by next week then poke me a bit |
| 18:49 | jnettlet | I am battling Android right now, and may be doing some GPU upgrades during that time. |
| 21:15 | topi` | sounds like a hefty backlog |
| 21:44 | heap_ | jnettlet: hi, pls is there any howto how to install that debian image? |
| 21:46 | jnettlet | heap_, I believe the wiki has a page...but it is pretty simple |
| 21:46 | jnettlet | are you doing it from a Linux system |
| 21:48 | heap_ | since i added drive into lvm im constantly getting those errors why writting data onto storage http://pastie.org/10559215 |
| 21:48 | heap_ | jnettlet:yes i can do it from ubuntu |
| 21:51 | mk01 | heap_: the drive if turning power off. |
| 21:52 | mk01 | then hardreset on link is turning it on again. kable, or wrong AC perhaps ? |
| 21:52 | heap_ | mk01: the drive is turning power off? |
| 21:52 | heap_ | u mean the power is gettin off? |
| 21:53 | heap_ | like AC power into drives? |
| 21:54 | jnettlet | it may be power savings for sata as well |
| 21:54 | mk01 | heap_: either power to drive is bad, or cabling from device <> drive is bad loosing some signalling |
| 21:55 | mk01 | jnettlet: each 3 seconds ? |
| 21:55 | mk01 | ok, 300s |
| 21:55 | mk01 | 5mn |
| 21:56 | mk01 | min |
| 21:56 | jnettlet | yeah |
| 21:56 | heap_ | is it possible that AC adapor is not enought powerful for 4 drives? |
| 21:56 | heap_ | jnettlet: so should i then disable that saving? |
| 21:57 | jnettlet | heap_, you can give it a try |
| 21:57 | heap_ | how |
| 21:57 | heap_ | ;( |
| 21:57 | mk01 | heap_: you have any jbod box for the drives or what ? |
| 21:58 | heap_ | mk01: its some external esata enclosure |
| 21:58 | heap_ | for 4 drives |
| 21:58 | heap_ | icy box |
| 21:58 | jnettlet | my icy box is a hardware raid |
| 21:58 | mk01 | then you can approach the drives like localy attached ATA |
| 21:58 | jnettlet | do they make jbod's also? |
| 21:59 | mk01 | jnettlet: yup |
| 21:59 | mk01 | by coincidence bought last week |
| 21:59 | heap_ | i use drives separately i built LVM on top of them |
| 21:59 | mk01 | JBOD then |
| 21:59 | heap_ | what do you mean? |
| 22:00 | heap_ | is it ok or wrong approach? |
| 22:00 | mk01 | no no |
| 22:00 | mk01 | all fine |
| 22:00 | mk01 | use hdparm -B /dev/sd{a,b,c,d} |
| 22:02 | mk01 | jnettlet: does the sata on cubox have FIS or not ? |
| 22:02 | heap_ | /dev/sda: APM_level = not supported |
| 22:02 | mk01 | heap_: WD drives ? |
| 22:02 | heap_ | yes |
| 22:02 | heap_ | wd red |
| 22:03 | jnettlet | mk01, no it is just Command based switching |
| 22:05 | heap_ | really its constantly issue |
| 22:05 | heap_ | i can hear how drives are something like powered on/off |
| 22:06 | mk01 | heap_: this doesn't mean it is powering off. |
| 22:06 | heap_ | so what can happen while this sound and dmesg log got the errrors i pasted |
| 22:07 | mk01 | it is only spinning low -> down , perhaps parking heads |
| 22:07 | mk01 | install smartctl |
| 22:07 | mk01 | and on one drive |
| 22:07 | mk01 | do |
| 22:07 | mk01 | smartctl -a /dev/sda |
| 22:07 | mk01 | and check this line: |
| 22:07 | mk01 | 193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always XXXXXXXXXX |
| 22:08 | mk01 | report the XXXXXXX number |
| 22:08 | heap_ | give me sec |
| 22:08 | mk01 | NP |
| 22:09 | heap_ | 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 57 |
| 22:09 | mk01 | how long are the drives UP ? |
| 22:09 | mk01 | in TOTAL |
| 22:10 | heap_ | 22:10:03 up 5:55, 2 users, load average: 0.45, 0.48, 0.49 |
| 22:10 | mk01 | oh so brand new |
| 22:10 | heap_ | well around 6 months |
| 22:10 | heap_ | sorry |
| 22:11 | heap_ | mk01: do you think they are faulty? |
| 22:11 | mk01 | ok, then it is not the internal management, if you hear them - they REALLY do go stanby |
| 22:11 | mk01 | standby |
| 22:12 | mk01 | as the "Load_Cycle_Count" is perfectly low |
| 22:12 | heap_ | yes i can hear some weird sound |
| 22:12 | heap_ | and each time that sound happend error is added into dmesg |
| 22:15 | heap_ | mk01: so any idea? |
| 22:15 | mk01 | heap_: I can't speak for cubox - low level wise - re-discuss with Jnettlet. but normally drive going standby should not trigger such errors ... "should" |
| 22:15 | mk01 | what I would do |
| 22:15 | mk01 | is |
| 22:16 | mk01 | replug the icy into another esata |
| 22:16 | mk01 | and keep it for an hour |
| 22:16 | mk01 | to see how it behaves |
| 22:16 | mk01 | and secondly |
| 22:17 | mk01 | I would disable the APM, if hdparm can't (what is mostly usual already with WD drives), then via WDIDLE / WDSETUP tool |
| 22:17 | mk01 | still, can you download & compile wdidle for linix |
| 22:17 | mk01 | linux |
| 22:17 | mk01 | and get me the value ? |
| 22:17 | heap_ | mk01: when i connected it to cubox pro v1 i think there were simillar problems ; or even i cant access that lvm |
| 22:17 | mk01 | wdidle -g .de |
| 22:17 | mk01 | -g /dev/sdXX |
| 22:19 | mk01 | heap_: I can shutdown mine 12disk raid and replug the ICY box into cubox, ... just to see. |
| 22:19 | mk01 | if you give me 30m |
| 22:19 | heap_ | so the question is why i cant mount it on cuboxprov1? |
| 22:20 | mk01 | heap_; jnettlet - Don't know anything about ... jnettlet |
| 22:21 | heap_ | is there wdidle tool for linux? can see it |
| 22:22 | mk01 | mmoment |
| 22:22 | heap_ | mk01: np |
| 22:22 | mk01 | http://idle3-tools.sourceforge.net |
| 22:23 | heap_ | mk01: today what happened all lights on drives turn off and i couldnt access my LVM box was on cubox + icy box but i was getting something like I/O error when ls /mount |
| 22:23 | heap_ | turned off* |
| 22:24 | heap_ | so i turn off /on icy and rebooted cubox and it worked again |
| 22:25 | mk01 | heap_: basically, everything is just made by humans (so can go wrong), but your situation is not OK |
| 22:26 | mk01 | ((if of course the orhers arrors you are speaking about are uneelated to the powersaving as it seems)) |
| 22:29 | mk01 | btw why I talked about original WDSETUP/WDIDLE is because the WDIDLE you are compiling is not setting general APM on drives, just the auto spinning / heads control (forced without any setting on APM) which can leads to the "load cycle counts" like in thousands in days. but your drive is FINE this way. |
| 22:30 | heap_ | mk01: then i have no idea what to do. do u think if i change AC power for icybox it might help |
| 22:30 | heap_ | ? |
| 22:30 | mk01 | WD DOS utility SHOULD allow you disable the regular APM behaviour - set to OFF |
| 22:31 | mk01 | heap_: nope (of course TRY is for free, so why not), but Jnet was right with the interval, it is regular 5min |
| 22:32 | heap_ | mk01: that interval is related to APM? |
| 22:32 | mk01 | also what can be, that simply there is a quirck on yours ICY box FW with toubles with cubox specifically - such things happen , but ... |
| 22:32 | mk01 | heap_: yes, looks that way |
| 22:33 | heap_ | ok so what should i do? use wdidle -g ? |
| 22:34 | heap_ | bc not i got more confused then before ;-) |
| 22:35 | mk01 | but again : if we want or not APM control is quite default for years now and by default from manufacturing lines turned on - all should happen transparently - normally there is timeout like 10-20 seconds perhaps, but if drive is not going OFF (FULL OFF) its time-to-ready is much shorter. |
| 22:36 | mk01 | I very much hate saying "I don't have problems" - but I have around like 30 drives in various combos and machines - don't remember when I seen BUS error, re-reresting etc |
| 22:36 | mk01 | heap_: ok so what should i do? use wdidle -g ?: yes, please. for me to feel completed ;0 |
| 22:36 | mk01 | ;) |
| 22:36 | heap_ | and after that? |
| 22:36 | mk01 | then go for original WD utility |
| 22:36 | mk01 | turn APM OFF |
| 22:37 | mk01 | and check behaviour |
| 22:37 | heap_ | u mean dos one? |
| 22:37 | heap_ | ;/ ah |
| 22:37 | mk01 | :( |
| 22:37 | mk01 | unfortunatelly |
| 22:37 | mk01 | BUT if you have UEFI board around |
| 22:37 | heap_ | but im thinking why i cant even mount that lvm on cuboxprov1 |
| 22:37 | mk01 | boot that IMG directly from it |
| 22:38 | heap_ | mk01: have only macboopro ;-( |
| 22:38 | mk01 | HEH |
| 22:38 | mk01 | still |
| 22:38 | heap_ | mk01: long time ago it worked on cuboxprov1 |
| 22:38 | heap_ | now i just can mount it |
| 22:38 | heap_ | so many errors |
| 22:38 | mk01 | do you have any cheap esata < |
| 22:38 | mk01 | esata cable |
| 22:39 | mk01 | to check one drive directly ? |
| 22:40 | heap_ | mk01: check for what? |
| 22:40 | mk01 | If the drive disconects the same way in intervals of 5mins :) |
| 22:40 | heap_ | ah |
| 22:41 | heap_ | so u mean to plug one drive directly via esata into cubox? |
| 22:41 | mk01 | YES |
| 22:41 | mk01 | buy such cable online - for |
| 22:41 | mk01 | 2euro |
| 22:41 | heap_ | but i think it happens most of time when u write data on that drive |
| 22:41 | mk01 | OK then |
| 22:41 | mk01 | wait |
| 22:41 | heap_ | when its idling nothing going on |
| 22:41 | mk01 | I;m going to power off the hdd pool |
| 22:42 | mk01 | after two years |
| 22:42 | mk01 | ;)) |
| 22:42 | heap_ | why? |
| 22:42 | mk01 | and test ICY |
| 22:42 | mk01 | in cubox |
| 22:42 | mk01 | myself |
| 22:42 | heap_ | mk01: how do you want to test it? |
| 22:42 | heap_ | or what do you want to test? |
| 22:42 | heap_ | what functionality? |
| 22:43 | mk01 | heh |
| 22:43 | mk01 | functionality of not doing FAIL over FAIL :D |
| 22:43 | mk01 | ike yours |
| 22:43 | mk01 | like yours |
| 22:44 | mk01 | just have to find USB cable to boot from 2.5 drive (which is root now booted from esata) |
| 22:44 | mk01 | so I can still boot something |
| 22:44 | mk01 | ]give me 20m |
| 22:44 | heap_ | np |
| 22:45 | heap_ | mk01: ops it is that box |
| 22:45 | heap_ | http://www.icydock.com/goods_downloads.php?osid=34&softwareid=148&id=172 |
| 22:45 | mk01 | between .... get friends on phone to provide you a board with sata connector and option to boot dos / disk / img |
| 22:45 | heap_ | http://www.icydock.com/goods.php?id=172 |
| 22:46 | mk01 | yes yes, all about the same |
| 22:47 | mk01 | wait |
| 22:49 | heap_ | u have the same model? |
| 23:00 | mk001 | http://paste.debian.net/332901/ |
| 23:03 | mk001 | jnettlet: even just with cis - unbalanced but full speed (100mb+) |
| 23:03 | mk001 | root@cubox ~ # hdparm -t /dev/sdb & hdparm -t /dev/sda |
| 23:03 | mk001 | [1] 3970 |
| 23:03 | mk001 | /dev/sdb: |
| 23:03 | mk001 | /dev/sda: |
| 23:03 | mk001 | Timing buffered disk reads: Timing buffered disk reads: 260 MB in 3.00 seconds = 86.66 MB/sec |
| 23:03 | mk001 | 52 MB in 3.07 seconds = 16.93 MB/sec |
| 23:04 | mk001 | ((that was both drives in parallel.)) |
| 23:05 | jnettlet | mk01, I haven't tested drives in parallel. The fastest SSD I have tested has done 128MB/s buffered sequential reads |
| 23:07 | mk001 | jnettlet: looks very fine |
| 23:10 | mk001 | and with just queuing the parallel test is fine too. the first disk goes first, second has to spinup already thus doing such low transfer for the test time |
| 23:10 | jnettlet | makes sense |
| 23:11 | mk001 | heap_: I might just keep it running for ~30 min - then I will need those drives to load the big pool again |
| 23:12 | mk001 | by any chance don't you have BIG mac, or at least MacbookPro with PCIE ? you can but esata card for it |
| 23:12 | mk001 | and retest |
| 23:14 | mk001 | beside the normal startup time (when box is powering up) nothing like you |
| 23:14 | mk001 | [ 2.656726] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) |
| 23:14 | mk001 | [ 2.657110] ata1.15: Port Multiplier 1.2, 0x197b:0x575f r0, 15 ports, feat 0x5/0xf |
| 23:14 | mk001 | [ 2.662312] ata1.00: hard resetting link |
| 23:14 | mk001 | [ 3.647836] scsi 1:0:0:0: Direct-Access Hitachi HTS725050A9A362 1.08 PQ: 0 ANSI: 4 |
| 23:14 | mk001 | [ 3.653484] sd 1:0:0:0: Attached scsi generic sg0 type 0 |
| 23:14 | mk001 | [ 3.654159] sd 1:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB) |
| 23:14 | mk001 | [ 3.654647] sd 1:0:0:0: [sda] Write Protect is off |
| 23:14 | mk001 | [ 3.654661] sd 1:0:0:0: [sda] Mode Sense: 23 00 00 00 |
| 23:14 | mk001 | [ 3.655154] sd 1:0:0:0: [sda] No Caching mode page found |
| 23:14 | mk001 | [ 3.655166] sd 1:0:0:0: [sda] Assuming drive cache: write through |
| 23:14 | mk001 | [ 3.894027] ata1.00: SATA link up 6.0 Gbps (SStatus 133 SControl 300) |
| 23:14 | mk001 | [ 3.894084] ata1.01: hard resetting link |
| 23:14 | mk001 | [ 4.354017] ata1.01: SATA link up 6.0 Gbps (SStatus 133 SControl 300) |
| 23:14 | mk001 | [ 4.354069] ata1.02: hard resetting link |
| 23:14 | mk001 | [ 4.379279] sda: sda1 sda2 |
| 23:14 | mk001 | [ 4.382027] sd 1:0:0:0: [sda] Attached SCSI disk |
| 23:14 | mk001 | [ 4.659188] ata1.02: SATA link down (SStatus 0 SControl 320) |
| 23:14 | mk001 | [ 4.659282] ata1.03: hard resetting link |
| 23:14 | mk001 | [ 4.998189] ata1.03: SATA link down (SStatus 0 SControl 320) |
| 23:14 | mk001 | [ 4.998282] ata1.04: hard resetting link |
| 23:14 | mk001 | [ 5.303185] ata1.04: SATA link down (SStatus 0 SControl 320) |
| 23:15 | mk001 | [ 5.303278] ata1.05: hard resetting link |
| 23:15 | mk001 | [ 5.608195] ata1.05: SATA link down (SStatus 0 SControl 320) |
| 23:15 | mk001 | [ 5.608289] ata1.06: hard resetting link |
| 23:15 | mk001 | [ 5.913180] ata1.06: SATA link down (SStatus 0 SControl 320) |
| 23:15 | mk001 | [ 5.913275] ata1.07: hard resetting link |
| 23:15 | mk001 | [ 6.218177] ata1.07: SATA link down (SStatus 0 SControl 320) |
| 23:15 | mk001 | [ 6.218271] ata1.08: hard resetting link |
| 23:15 | mk001 | [ 6.523191] ata1.08: SATA link down (SStatus 0 SControl 320) |
| 23:15 | mk001 | [ 6.523286] ata1.09: hard resetting link |
| 23:15 | mk001 | [ 6.921187] ata1.09: SATA link down (SStatus 0 SControl 320) |
| 23:15 | mk001 | [ 6.921281] ata1.10: hard resetting link |
| 23:15 | mk001 | [ 7.226185] ata1.10: SATA link down (SStatus 0 SControl 320) |
| 23:15 | mk001 | [ 7.226278] ata1.11: hard resetting link |
| 23:15 | mk001 | [ 7.531178] ata1.11: SATA link down (SStatus 0 SControl 320) |
| 23:15 | mk001 | [ 7.531273] ata1.12: hard resetting link |
| 23:15 | mk001 | [ 7.836180] ata1.12: SATA link down (SStatus 0 SControl 320) |
| 23:15 | mk001 | [ 7.836273] ata1.13: hard resetting link |
| 23:15 | mk001 | [ 8.141186] ata1.13: SATA link down (SStatus 0 SControl 320) |
| 23:15 | mk001 | [ 8.141279] ata1.14: hard resetting link |
| 23:15 | mk001 | [ 8.446174] ata1.14: SATA link down (SStatus 0 SControl 320) |
| 23:15 | mk001 | [ 8.446742] ata1.00: ATA-9: WDC WD30EZRX-00D8PB0, 80.00A80, max UDMA/133 |
| 23:15 | mk001 | [ 8.446753] ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32) |
| 23:15 | mk001 | [ 8.447281] ata1.00: configured for UDMA/133 |
| 23:15 | mk001 | [ 8.447767] ata1.01: ATA-9: WDC WD30EZRX-00D8PB0, 80.00A80, max UDMA/133 |
| 23:15 | mk001 | [ 8.447777] ata1.01: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32) |
| 23:15 | mk001 | [ 8.448295] ata1.01: configured for UDMA/133 |
| 23:15 | mk001 | [ 8.448402] ata1: EH complete |
| 23:15 | mk001 | [ 8.448787] scsi 0:0:0:0: Direct-Access ATA WDC WD30EZRX-00D 0A80 PQ: 0 ANSI: 5 |
| 23:15 | mk001 | [ 8.449659] sd 0:0:0:0: Attached scsi generic sg1 type 0 |
| 23:15 | mk001 | [ 8.449800] sd 0:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) |
| 23:16 | mk001 | [ 8.449812] sd 0:0:0:0: [sdb] 4096-byte physical blocks |
| 23:16 | mk001 | [ 8.450213] scsi 0:1:0:0: Direct-Access ATA WDC WD30EZRX-00D 0A80 PQ: 0 ANSI: 5 |
| 23:16 | mk001 | [ 8.450922] sd 0:1:0:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) |
| 23:16 | mk001 | [ 8.450933] sd 0:1:0:0: [sdc] 4096-byte physical blocks |
| 23:16 | mk001 | [ 8.451140] sd 0:0:0:0: [sdb] Write Protect is off |
| 23:16 | mk001 | [ 8.451153] sd 0:0:0:0: [sdb] Mode Sense: 00 3a 00 00 |
| 23:16 | mk001 | [ 8.451188] sd 0:1:0:0: [sdc] Write Protect is off |
| 23:16 | mk001 | [ 8.451201] sd 0:1:0:0: [sdc] Mode Sense: 00 3a 00 00 |
| 23:16 | mk001 | [ 8.451252] sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA |
| 23:16 | mk001 | [ 8.451300] sd 0:1:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA |
| 23:16 | mk001 | [ 8.451569] sd 0:1:0:0: Attached scsi generic sg2 type 0 |
| 23:16 | mk001 | [ 19.253712] random: nonblocking pool is initialized |
| 23:16 | mk001 | [ 21.567089] sdc: sdc1 sdc9 |
| 23:16 | mk001 | [ 21.567188] sdb: sdb1 sdb9 |
| 23:16 | mk001 | [ 21.568399] sd 0:1:0:0: [sdc] Attached SCSI disk |
| 23:16 | mk001 | [ 21.568827] sd 0:0:0:0: [sdb] Attached SCSI disk |
| 23:16 | mk001 | and those two are WD GREEN |
| 23:16 | mk001 | now at 8m both drives were powered off |
| 23:16 | mk001 | box turned even both LEDS off |
| 23:17 | mk001 | no log |
| 23:17 | mk001 | ANY |
| 23:17 | mk001 | [ 46.185616] brcmfmac: brcmf_fws_init: failed to set bdcv2 tlv signaling |
| 23:17 | mk001 | [ 46.191472] brcmfmac: brcmf_setup_wiphybands: rxchain error (-52) |
| 23:17 | mk001 | [ 46.199613] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code |
| 23:17 | mk001 | [ 46.781387] mousedev: PS/2 mouse device common for all mice |
| 23:17 | mk001 | [ 47.332671] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52 |
| 23:17 | mk001 | [ 47.334129] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52 |
| 23:17 | mk001 | [ 47.336412] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52 |
| 23:17 | mk001 | [ 47.516974] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52 |
| 23:17 | mk001 | [ 47.524089] brcmfmac: _brcmf_set_multicast_list: Setting BRCMF_C_SET_PROMISC failed, -52 |
| 23:17 | mk001 | [ 48.113359] Adding 797716k swap on /dev/sda2. Priority:0 extents:1 across:797716k FS |
| 23:17 | mk001 | root@cubox ~ # |
| 23:18 | mk001 | power them on via fdisk -l |
| 23:18 | mk001 | no single error. |
| 23:19 | mk001 | you can just BUY the model I have - exactly |
| 23:20 | mk001 | ICY BOX IB-3664SU3 |
| 23:21 | heap_ | sec |
| 23:21 | mk001 | perhaps the cheapest solution - considering all the time you invest in resolution of your error |
| 23:21 | jnettlet | mk001, well he should test out my kernel...right now he is running a bastard Arch kernel |
| 23:22 | mk001 | jnettlet: oh I expected this elaborations be already done |
| 23:22 | jnettlet | nope |
| 23:23 | heap_ | mk001: so all works fine for you? |
| 23:23 | mk001 | replace zImage & reboot . 5 minutes max |
| 23:23 | mk001 | yes, still. 22th minute of up |
| 23:23 | mk001 | drives are again off |
| 23:23 | mk001 | no any error / warning |
| 23:24 | heap_ | hmhm but u run jnettlete debian? |
| 23:24 | mk001 | kernel, yes |
| 23:24 | heap_ | yes kernel |
| 23:24 | heap_ | ok i need to install it |
| 23:25 | heap_ | jnettlet: pls so how can i easilly install that image u posted link few days ago? |
| 23:25 | mk001 | heap_: don't over complicate for now. grab kernel & reboot |
| 23:25 | heap_ | but i have arch |
| 23:25 | mk001 | then you can rethink strategy again |
| 23:26 | heap_ | so probably its not that easy to use kernel only |
| 23:26 | mk001 | apples, oranges |
| 23:26 | mk001 | I use the same kernel for all roots I boot (ubuntu / debian / redhat) |
| 23:26 | jnettlet | basically download it, and then as root run. xzcat imagename.xz | dd of=/dev/sdcard bs=1M conv=fsync |
| 23:27 | jnettlet | change imagename and sdcard to reflect the image and sdcard |
| 23:27 | heap_ | ah ok |
| 23:28 | mk001 | jnettlet: unrelated - is kexec working ? |
| 23:29 | heap_ | mk001: anyway thank you for all that |
| 23:29 | mk001 | I know some years ago kexec / arm was broken (perhaps DTs?), then supossed to work (but fail for me any try), I didn't test for some time now |
| 23:29 | mk001 | heap_: no problem |
| 23:29 | mk001 | welcome |
| 23:29 | jnettlet | I haven't tested it, upstream it works |
| 23:29 | heap_ | ill install jnettlets kernel or debian with that kernel and will see |
| 23:30 | jnettlet | although there was some breakage between 4.1 and 4.2 I believe |
| 23:30 | mk001 | jnettlet: OH that might be my test window |
| 23:30 | heap_ | jnettlet: are u tunning that kernel for general use of cubox? |
| 23:30 | heap_ | or for some solidrun internal purpose? |
| 23:30 | mk001 | heap_: that kernel is tuned cubox general |
| 23:31 | jnettlet | heap_, my kernel is tuned for SolidRun customers, but I take patchsets from the community to support many iMX6 boards |
| 23:31 | heap_ | oh ok |
| 23:33 | mk001 | heap: at over 40min up I'm ending experiment |
| 23:33 | mk001 | no error |
| 23:34 | heap_ | nice |
| 23:34 | heap_ | so if its not kernel issue then hw? |
| 23:36 | mk001 | lets wait |
| 23:36 | mk001 | for your test |
| 23:36 | mk001 | first |
| 23:38 | mk001 | sorry for spam but just for completeness: this is when I HARD removed cable without taking care of drives: |
| 23:38 | mk001 | [ 1667.365957] ata1.00: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.365972] ata1.01: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.365982] ata1.02: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.365991] ata1.03: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.365999] ata1.04: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.366008] ata1.05: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.366016] ata1.06: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.366024] ata1.07: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.366032] ata1.08: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.366041] ata1.09: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.366050] ata1.10: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.366058] ata1.11: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.366066] ata1.12: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.366074] ata1.13: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.366082] ata1.14: failed to read SCR 1 (Emask=0x40) |
| 23:38 | mk001 | [ 1667.366096] ata1.15: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen |
| 23:38 | mk001 | [ 1667.366104] ata1.15: irq_stat 0x00400000, PHY RDY changed |
| 23:38 | mk001 | [ 1667.366117] ata1.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:38 | mk001 | [ 1667.366130] ata1.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:38 | mk001 | [ 1667.366143] ata1.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:38 | mk001 | [ 1667.366156] ata1.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:38 | mk001 | [ 1667.366170] ata1.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:38 | mk001 | [ 1667.366183] ata1.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:38 | mk001 | [ 1667.366196] ata1.06: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:38 | mk001 | [ 1667.366209] ata1.07: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:38 | mk001 | [ 1667.366221] ata1.08: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:39 | mk001 | [ 1667.366234] ata1.09: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:39 | mk001 | [ 1667.366247] ata1.10: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:39 | mk001 | [ 1667.366260] ata1.11: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:39 | mk001 | [ 1667.366272] ata1.12: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:39 | mk001 | [ 1667.366285] ata1.13: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:39 | mk001 | [ 1667.366298] ata1.14: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen |
| 23:39 | mk001 | [ 1667.366315] ata1.15: hard resetting link |
| 23:39 | mk001 | [ 1668.088644] ata1.15: SATA link down (SStatus 0 SControl 300) |
| 23:39 | mk001 | [ 1671.088443] ata1.15: qc timeout (cmd 0xe4) |
| 23:39 | mk001 | [ 1671.088460] ata1.15: failed to read PMP GSCR[0] (Emask=0x4) |
| 23:39 | mk001 | [ 1671.088468] ata1.15: PMP revalidation failed (errno=-5) |
| 23:39 | mk001 | [ 1673.088307] ata1.15: hard resetting link |
| 23:39 | mk001 | [ 1673.393262] ata1.15: SATA link down (SStatus 0 SControl 300) |
| 23:39 | mk001 | [ 1676.393074] ata1.15: qc timeout (cmd 0xe4) |
| 23:39 | mk001 | [ 1676.393090] ata1.15: failed to read PMP GSCR[0] (Emask=0x4) |
| 23:39 | mk001 | [ 1676.393100] ata1.15: PMP revalidation failed (errno=-5) |
| 23:39 | mk001 | [ 1676.393110] ata1.15: limiting SATA link speed to 1.5 Gbps |
| 23:39 | mk001 | [ 1678.392935] ata1.15: hard resetting link |
| 23:39 | mk001 | [ 1678.697904] ata1.15: SATA link down (SStatus 0 SControl 310) |
| 23:39 | mk001 | [ 1681.697718] ata1.15: qc timeout (cmd 0xe4) |
| 23:39 | mk001 | [ 1681.697735] ata1.15: failed to read PMP GSCR[0] (Emask=0x4) |
| 23:39 | mk001 | [ 1681.697744] ata1.15: PMP revalidation failed (errno=-5) |
| 23:39 | mk001 | [ 1683.697588] ata1.15: hard resetting link |
| 23:39 | mk001 | [ 1684.002546] ata1.15: SATA link down (SStatus 0 SControl 310) |
| 23:39 | mk001 | [ 1687.002358] ata1.15: qc timeout (cmd 0xe4) |
| 23:39 | mk001 | [ 1687.002374] ata1.15: failed to read PMP GSCR[0] (Emask=0x4) |
| 23:39 | mk001 | [ 1687.002382] ata1.15: PMP revalidation failed (errno=-5) |
| 23:39 | mk001 | [ 1689.002225] ata1.15: hard resetting link |
| 23:39 | mk001 | [ 1689.307185] ata1.15: SATA link down (SStatus 0 SControl 310) |
| 23:39 | mk001 | [ 1692.307002] ata1.15: qc timeout (cmd 0xe4) |
| 23:40 | mk001 | [ 1692.307018] ata1.15: failed to read PMP GSCR[0] (Emask=0x4) |
| 23:40 | mk001 | [ 1692.307027] ata1.15: PMP revalidation failed (errno=-5) |
| 23:40 | mk001 | [ 1692.307035] ata1.15: failed to recover PMP after 5 tries, giving up |
| 23:40 | mk001 | [ 1692.307042] ata1.15: Port Multiplier detaching |
| 23:40 | mk001 | [ 1692.307051] ata1.00: disabled |
| 23:40 | mk001 | [ 1692.307061] ata1.01: disabled |
| 23:40 | mk001 | [ 1692.307082] ata1.00: disabled |
| 23:40 | mk001 | [ 1694.306869] ata1: hard resetting link |
| 23:40 | mk001 | [ 1694.611830] ata1: SATA link down (SStatus 0 SControl 300) |
| 23:40 | mk001 | [ 1694.611864] ata1: EH complete |
| 23:40 | mk001 | [ 1694.611898] ata1.00: detaching (SCSI 0:0:0:0) |
| 23:40 | mk001 | [ 1694.618680] sd 0:0:0:0: [sdb] Synchronizing SCSI cache |
| 23:40 | mk001 | [ 1694.618934] sd 0:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00 |
| 23:40 | mk001 | [ 1694.618949] sd 0:0:0:0: [sdb] Stopping disk |
| 23:40 | mk001 | [ 1694.619008] sd 0:0:0:0: [sdb] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 |
| 23:40 | mk001 | [ 1694.623543] ata1.01: detaching (SCSI 0:1:0:0) |
| 23:40 | mk001 | [ 1694.625261] sd 0:1:0:0: [sdc] Synchronizing SCSI cache |
| 23:40 | mk001 | [ 1694.625425] sd 0:1:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00 |
| 23:40 | mk001 | [ 1694.625438] sd 0:1:0:0: [sdc] Stopping disk |
| 23:40 | mk001 | [ 1694.625487] sd 0:1:0:0: [sdc] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 |
| 23:40 | mk001 | so one cmd / sata line |
| 23:40 | mk001 | then detach & done |
| 23:41 | heap_ | ? what do you mean |
| 23:41 | heap_ | u removed cable while system was on? |
| 23:42 | mk001 | yes |
| 23:42 | heap_ | is that safe? |
| 23:42 | mk001 | yes |
| 23:42 | mk001 | hardware wise |
| 23:42 | heap_ | and what did it prove? |
| 23:43 | mk001 | different story is your pool data - that depends |
| 23:43 | heap_ | mk001: im bit confused. |
| 23:43 | mk001 | heap_: of what ? |
| 23:43 | heap_ | of what you are trying to explain me |
| 23:44 | mk001 | nothing special - just showed that even hard unplug is not starting this weird series of errors you had |
| 23:44 | heap_ | oh ok |
| 23:45 | heap_ | so what should i do as 1)? |
| 23:45 | mk001 | continue with flashing proper kernel |
| 23:45 | mk001 | test it |
| 23:46 | mk001 | then I would test your enclosure with drives as is in another system |
| 23:46 | heap_ | yeah |
| 23:46 | mk001 | if again same failures |
| 23:46 | mk001 | I would buy another box |
| 23:46 | heap_ | ;/ |
| 23:46 | mk001 | ((between you can just for piece of soul get hand onto SINGLE esata cable and test single drive |
| 23:47 | heap_ | ll try |
| 23:48 | mk001 | but when you look at your log - its repetitive exactly at 5 mins and WITH ALL drives always and always - so either it's just drives exactly same configured going down and box can't properly handle that |
| 23:48 | mk001 | OR |
| 23:49 | mk001 | it is triggered directly by box ITSELF (on what kind of event we don't know) - but result is same - not perhaps the most polite ICY box you bought -> buy another |
| 23:49 | mk001 | with feedback from community |
| 23:49 | mk001 | OK or NOTOK |
| 23:51 | mk001 | but this wizard stuff of planing future is all useless - until you finally reboot :D |
| 23:51 | mk001 | and see |
| 23:54 | heap_ | mk001: but for example now it stopped, it didnt generate that error message for at least one hour |
| 23:55 | mk001 | sure |
| 23:55 | mk001 | but try to spin it up |
| 23:56 | heap_ | there is cp still in progress |
| 23:56 | mk001 | whhen it''s a sleep is asleep |
| 23:56 | mk001 | ????? how can it stop with cp in progress ? |
| 23:57 | heap_ | ok im running rsync for about 3 hours... it is still running. What i am saying those errors are not gennerating for at least one hour |
| 23:57 | mk001 | kick mbr reread (with 'partprobe' or 'fdisk -l') |
| 23:58 | heap_ | i did fdisk -l |
| 23:58 | mk001 | heap_: doesn't negate what we spoke before. |
| 23:58 | heap_ | mk001: so it is completely random behaviour? |
| 23:58 | mk001 | if nothing goes sleep, the link won't go off /timeout either |