• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 2 [3] 4 5 ... 16
31  General Category / General Discussion / Problems automouting USB HDD on boot. on: August 25, 2010, 03:34:10 PM
Hi, running Debian Squeeze without any issues for rather a long time.  However recently something has changed.  When I start my system now, my big USB HDD is not mounted, and thus lots of things like my mail server/web server and other stuff all fall over.

I am using the wait4usbdisks.sh script, and that's worked well, but something had changed in either the kernel or debian base that's made it less than efficient (I have seen it work a couple of boots, but it's far from robust and 9/10 times it does not work anymore).

IS there a better, more bullet-proof way of delaying the init until the HDD has spun up?  What solutions are others using?
32  Linux Stuff / Kernel / Re: 2.6.35.2 new release on: August 18, 2010, 12:31:11 PM
Moving from 2.6.35.1 to 2.6.35.2, my USB HDD does not automount on boot anymore, I need to manually mount it.

Has any config change caused this?

Anyone else seeing this?

EDIT:   Seen this is DMESG

Code:
EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sda1): recovery complete
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
swapper: page allocation failure. order:3, mode:0x4020
[<c003044c>] (unwind_backtrace+0x0/0xec) from [<c00826e8>] (__alloc_pages_nodemask+0x4a8/0x50c)
[<c00826e8>] (__alloc_pages_nodemask+0x4a8/0x50c) from [<c008275c>] (__get_free_pages+0x10/0x3c)
[<c008275c>] (__get_free_pages+0x10/0x3c) from [<c030fb00>] (pskb_expand_head+0x58/0x1a0)
[<c030fb00>] (pskb_expand_head+0x58/0x1a0) from [<c033aec8>] (ip_rcv_finish+0x164/0x3dc)
[<c033aec8>] (ip_rcv_finish+0x164/0x3dc) from [<c0316a50>] (__netif_receive_skb+0x474/0x4d0)
[<c0316a50>] (__netif_receive_skb+0x474/0x4d0) from [<c0316b3c>] (process_backlog+0x90/0x15c)
[<c0316b3c>] (process_backlog+0x90/0x15c) from [<c0316e20>] (net_rx_action+0x58/0x180)
[<c0316e20>] (net_rx_action+0x58/0x180) from [<c0042608>] (__do_softirq+0x88/0x124)
[<c0042608>] (__do_softirq+0x88/0x124) from [<c00426ec>] (irq_exit+0x48/0xa0)
[<c00426ec>] (irq_exit+0x48/0xa0) from [<c002b070>] (asm_do_IRQ+0x70/0x8c)
[<c002b070>] (asm_do_IRQ+0x70/0x8c) from [<c03e4ae8>] (__irq_svc+0x48/0xa8)
Exception stack(0xc051ff48 to 0xc051ff90)
ff40:                   000797ee 00001f40 000797ee 20000013 c0525630 c0525640
ff60: c05ef6dc c0522320 00023c48 56251311 00023b44 00000000 1da979cb c051ff90
ff80: c005bea4 c003441c 20000013 ffffffff
[<c03e4ae8>] (__irq_svc+0x48/0xa8) from [<c003441c>] (kirkwood_enter_idle+0x64/0x90)
[<c003441c>] (kirkwood_enter_idle+0x64/0x90) from [<c02e1718>] (cpuidle_idle_call+0xb4/0x118)
[<c02e1718>] (cpuidle_idle_call+0xb4/0x118) from [<c002c9ac>] (cpu_idle+0x60/0xb8)
[<c002c9ac>] (cpu_idle+0x60/0xb8) from [<c0008988>] (start_kernel+0x284/0x2e4)
[<c0008988>] (start_kernel+0x284/0x2e4) from [<00008034>] (0x8034)
Mem-info:
Normal per-cpu:
CPU    0: hi:  186, btch:  31 usd: 173
active_anon:10108 inactive_anon:11353 isolated_anon:0
 active_file:21490 inactive_file:74670 isolated_file:0
 unevictable:0 dirty:27 writeback:0 unstable:0
 free:4987 slab_reclaimable:2261 slab_unreclaimable:1417
 mapped:3534 shmem:37 pagetables:359 bounce:0
Normal free:19948kB min:2884kB low:3604kB high:4324kB active_anon:40432kB inactive_anon:45412kB active_file:85960kB inactive_file:298680kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:520192kB mlocked:0kB dirty:108kB writeback:0kB mapped:14136kB shmem:148kB slab_reclaimable:9044kB slab_unreclaimable:5668kB kernel_stack:944kB pagetables:1436kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0
Normal: 2875*4kB 728*8kB 154*16kB 5*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 19948kB
96197 total pagecache pages
0 pages in swap cache
Swap cache stats: add 0, delete 0, find 0/0
Free swap  = 0kB
Total swap = 0kB
131072 pages of RAM
5434 free pages
2617 reserved pages

33  Linux Stuff / Kernel / Re: 2.6.34 new release on: May 19, 2010, 11:03:07 AM
Your SD Card does internal wear levelling and block management with an undisclosed algorithm.

Ahh, I didn't know this....

I wanted something that managed the wear leveling of my SD Card.   I ran for a while with a split setup, with some stuff on the NAND and my /VAR partition mounted on my Transcend Class6 SDCard (EXT3) but every now and again the system would fall over because the mmcblk device was readonly...   Never got to the bottom of it, so move back to NAND only.

I was thinking of re-using my sdcard for something less critical like /var/log

34  Linux Stuff / Kernel / Re: 2.6.34 new release on: May 18, 2010, 11:30:26 PM
Hmm, that's not what the LogFS site says..

http://logfs.org/logfs/

"Q: Does FogFS work on both NAND and NOR?

A: Yes, it does. It works on block devices (USB stick, hard disk, etc.) as well."
35  Linux Stuff / Kernel / Re: 2.6.34 new release on: May 18, 2010, 09:58:55 AM
Is there a module (or builtin) support for log-fs?

I was thinking of trying out logfs as a format for my sdcard..
36  General Category / General Discussion / Re: What Now? on: April 29, 2010, 12:23:19 AM
Twonkymedia should do the trick. 

I have a Wiki page setup here that describes installation and configuration on Sheevaplug:

http://plugcomputer.org/plugwiki/index.php/Run_TwonkyMedia_on_Sheevaplug

As mentioned, it's not free, but it is GOOD, infact it's the only one that delivers rock solid performance to my home network, both wired and wireless, for video, music, and photos..

You geta  30 day trial, if it works, there is a 50% promo at the mo.

http://www.twonkymedia.com/Promotions/index.html
37  General Category / General Discussion / /var on SDCard, frequently fails and ends up being mounted readonly. on: April 06, 2010, 12:00:44 AM
A couple of months back, after several posters here planted seeds of doubt in my head about internal nand wear, I picked up a transcend 4GB Class6 SDCard, and moved my /var partition to it. (as looking at iotop, that's where most of my writes were occuring, by doing just var, I don't take too much of a write performance hit that sdcard brings compared to internal nand).

Anyway, several times now, it's all gone pear shaped, and several services break down.  Upon investigation, my sdcard is mounted read-only.

Today I managed to get in via ssh after this had happened, and got a dump of dmesg (snippet included)

Any ideas what's going on?  (latest cxbiker kernel)

Quote
mmcblk0: error -110 transferring data, sector 437848, nr 8, card status 0xc00
end_request: I/O error, dev mmcblk0, sector 437848
Buffer I/O error on device mmcblk0p1, logical block 53707
lost page write due to I/O error on mmcblk0p1
mmcblk0: error -110 sending read/write command, response 0xd00, card status 0x400d00
mvsdio mvsdio: FIFO_EMPTY bit missing
end_request: I/O error, dev mmcblk0, sector 3700800
end_request: I/O error, dev mmcblk0, sector 3700808
Aborting journal on device mmcblk0p1-8.
mvsdio mvsdio: FIFO_EMPTY bit missing
mmcblk0: error -110 sending read/write command, response 0x400d00, card status 0x400d00
mvsdio mvsdio: FIFO_EMPTY bit missing
end_request: I/O error, dev mmcblk0, sector 3678208
Buffer I/O error on device mmcblk0p1, logical block 458752
lost page write due to I/O error on mmcblk0p1
JBD2: I/O error detected when updating journal superblock for mmcblk0p1-8.
EXT4-fs error (device mmcblk0p1): ext4_journal_start_sb: Detected aborted journal
EXT4-fs (mmcblk0p1): Remounting filesystem read-only
EXT4-fs error (device mmcblk0p1): ext4_journal_start_sb: Detected aborted journal
EXT4-fs (mmcblk0p1): Remounting filesystem read-only

mvsdio mvsdio: FIFO_EMPTY bit missing
mmcblk0: retrying using single block read
mvsdio mvsdio: FIFO_EMPTY bit missing
mmcblk0: error -110 sending read/write command, response 0xd00, card status 0x400d00
end_request: I/O error, dev mmcblk0, sector 75664

38  Linux Stuff / Linux distributions / Re: The alternative Debian install method. on: March 09, 2010, 01:22:32 PM
The kernel that gets loaded is the one in the SheevaInster 1.0 (2.6.30 I recall).  But yes, once you are up and running, you can simply update it to the latest from sheeva-with-linux.

This is exactly what I do, it works without issue.
39  Linux Stuff / Linux distributions / Re: The alternative Debian install method. on: March 08, 2010, 06:24:15 AM
Hi, this is my first message.
i don't understand this passage:
"At the end of the build process (which should only take about 10 minutes), you will be left with a rootfs.tar.gz that can be used to overwrite the one in the sheeva installer 1.0 download."
I have downloaded a prebuilt rootfs.tar.gz
I have downloaded sheevaplug-installer-v1.0.tar.gz
and now?
Sorry for my english  Tongue

You don't need to use the "build process", this is if you want to use the script to build your OWN rootfs.tar.gz  You have opted to download a pre-built one.

You need to untar the sheevaplug-installer-v1.0.tar.gz, replace the Ubuntu rootfs.tar.gz with the debian one you have download.  Then follow the instructions for SheevaInstaller.
40  Linux Stuff / Kernel / Re: 2.6.33 new release on: March 03, 2010, 02:02:39 AM
Thanks, working here Globalscale 1.3 Sheevaplug.
41  Linux Stuff / Linux distributions / Re: The alternative Debian install method. on: February 07, 2010, 09:30:10 AM
Use these ones:

http://www.mediafire.com/?mxzzmymzyjk  (Lenny)

Or

http://www.mediafire.com/?z2ljmnukmdc (Squeeze)

Or use the script to build your own (and more uptodate) rootfs.

42  Hardware and U-Boot firmware / Hardware / Weird problem with mmc card being mounted readonly on: February 01, 2010, 03:39:51 AM
My server has been stable for many months, however yesterday I did two things:

1/ Updated to 2.6.32.7 cxbiker kernel.
2/ Update debian squeeze packages.

Last night I got a couple of errors from cron saying that /var is readonly (I have most of my system on nand, but have /var mounted on SDcard).  I did a check and /var was listed as being mounted as readonly.

What is weird, is the system uptime was in weeks, and it certainly wasn't readonly earlier that day (as the cron would be moaning every hour).

Even stranger today, I couldn't access the system via SSH, and had to reboot it to get access.   I can access it again now, and /var on mcc is rw.

Anyone got any ideas what may have occured?
43  Linux Stuff / Kernel / Re: Kernel 2.6.32 Crypto on: January 18, 2010, 02:36:43 PM
Just found out that all you have to do is select a cipher which has a drivername that starts with mv-, and you'll get hardware support.

Can you eleborate?  You have hardware crypto working?  What with?  How?
44  Hardware and U-Boot firmware / Hardware / Re: crypto accelaration on: January 18, 2010, 02:35:41 PM
The only words I understood of that last post where "hello"...  Shocked Shocked Shocked
45  General Category / General Discussion / Re: SheevaPlug Installer with updated kernel, uboot, distro ? on: January 15, 2010, 05:27:08 PM
It's pretty hard to totally brick a plug.  Those that are tinkering because they know how to get things back.

There are documented and well tested methods of updating your uboot, kernel, rootfs, but this is not one of them (yet..)

Off skiing next week (French Alps), so unlikely to have tinker time until I get back..
Pages: 1 2 [3] 4 5 ... 16