|
|
Up |
|
|
  |
|
|
  |
|
|
  |
Author: John HollandJohn Holland
Date: Dec 24, 2008 14:10
On Wed, 2008-12-24 at 13:53 +0100, Martin Michlmayr wrote:
> * John Holland [2008-12-23 15:26]:
>> Dec 23 12:10:01 utah kernel: [43103436.040000] md1_resync D c020fd94
>> 0 2887 2
>> Dec 23 12:10:01 utah kernel: [43103436.050000] [] (schedule
>> +0x0/0x3ac) from [] (md_do_sync+0x224/0xad8 [md_mod])
>> Dec 23 12:10:01 utah kernel: [43103436.050000] [] (md_do_sync
>
> How easy is it for you to reproduce this problem? Can you post the
> _full_ dmesg when this problem occurs?
To be honest, I haven't tried to reproduce the problem. I got these
messages about every two minutes while resync'ing md0, which took well
over 24h (perhaps 28-32h) for about 2.9TB.
Depending upon what the distributor says in the new year, I may need to
rebuild the raid and install debian. And I will definitely keep you in
mind.
I have done a 'smartctl -t long /dev/sd[a-d]' w/o any errors. So I
believe the drives are o.k. Just the messages about checksums as in the
files I had attached are getting rather annoying.
|
| Show full article (1.45Kb) |
|
no comments
|
|
  |
Author: Ben SchwarzBen Schwarz
Date: Sep 22, 2008 22:30
Hi,
I've been trying to get netatalk working on my new Qnap NAS.
Through a little hunting I've found that I do not have a appletalk
kernel module..
What can be done to do this and add afp support for my shiny NAS?
Cheers,
Ben
|
| |
|
no comments
|
|
  |
Author: slugmanbashislugmanbashi
Date: Sep 21, 2008 15:30
Hi All
Ive had cause to compile applications such as rtorrent on an Etch NSLU2 in
the past.
Each time I used the CXXFLAGS settings recommended here,
http://libtorrent.rakshasa.no/wiki/LibTorrentKnownIssues .
Which are, CXXFLAGS="-O2 -mcpu=xscale -mtune=xscale" .
Are these CXXFLAGS setting still-valid/the-best for applications compiled on
a Lenny NSLU2(IXP420) running armel ?
(Lenny Beta2 on the NSLU2 is currently running GCC 4.3.1-9 and kernel
2.6.26-1-ixp4xx)
I see on this page http://wiki.debian.org/ArmEabiPort that there is talk of
improved Floating Point performance and a more efficient syscall convention
with armel.
Are there any FLAGS that should be set at compile time to ensure these
performance improvements are taken advantage of on a Lenny armel NSLU2?
Thanks
|
| Show full article (1.13Kb) |
|
3 Comments |
|
  |
Author: RichardRichard
Date: Sep 17, 2008 02:30
hey
i have a DLink DNS-323, and am interested in getting the armel port running
on it. can anyone point me in the right direction? all i can find is a small
section of the arm port wiki ( http://wiki.debian.org/ArmPort ) that
mentions kernel only. i assume this means there is a kernel running, but no
initramfs? could anyone point me to this kernel image, or any further info?
thanks
heyi have a DLink DNS-323, and am interested in getting the armel port running on it. can anyone point me in the right direction? all i can find is a small section of the arm port wiki ( http://wiki.debian.org/ArmPort ) that mentions kernel only. i assume this means there is a kernel running, but no initramfs? could anyone point me to this kernel image, or any further info?
thanks
|
| |
|
1 Comment |
|
  |
Author: Heinrich HiemeschHeinrich Hiemesch
Date: Sep 16, 2008 12:20
Sorry for being late with my slug runnig etch while all are talking
about lenny here.
This is the problem as far as I can decribe it - I'm only a debian
*user*:
After I upgraded some days ago my slug running Debian Etch 4.03r using
apt-get upgrade the slug hangs during reboot. Status led yellow,
Ehternet blinking, Disk 1 + 2 off. Ok, maybe fsck running, I waited
for over an hour but nothing changed.
Then I copied a previously saved /boot - folder to the actual /boot -
folder. The slug started normally. My sda ( a 4 GB stick) is
partitioned as follows:
sda1 /boot (bootable)
sda5 /swap
sda6 /
Today I had to reboot the slug due to a problem with the usb hub which
connects two hdds and another stick (swap) to the slug - and the slug
hangs again. I then tried the solution of Martin Michelmayr posted
here in April for a corrupt lenny update (flashing the slug after
booting into the debian installer) = no go.
|
| Show full article (1.82Kb) |
|
5 Comments |
|
  |
Author: Gordon FarquharsonGordon Farquharson
Date: Sep 15, 2008 00:20
Hi Michael
On Sun, Sep 14, 2008 at 03:09, Michael Glockenstein
wrote:
> I changed the udev rules like suggested to
>
> SUBSYSTEM=="usb", DEVPATH=="*/usb1/1-[12]", ACTION=="add",
> PROGRAM="/usr/bin/leds disk-%%n on"
> SUBSYSTEM=="usb", DEVPATH=="*/usb1/1-[12]", ACTION=="remove",
> PROGRAM="/usr/bin/leds disk-%%n off"
>
> and first it worked for me but since yesterday it fails again.
> I do not understand much of udev, but I think the bus number
> is not constant.
>
> Now again the following is working:
> SUBSYSTEM=="usb", DEVPATH=="*/usb3/3-[12]", ACTION=="add",
> PROGRAM="/usr/bin/leds disk-%%n on"
> SUBSYSTEM=="usb", DEVPATH=="*/usb3/3-[12]", ACTION=="remove",
> PROGRAM="/usr/bin/leds disk-%%n off"
|
| Show full article (1.14Kb) |
|
2 Comments |
|
  |
|
|
  |
|
|
  |
|
|
|
|
|