• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Linux Stuff / General Linux questions / Re: problems mounting external USB hard drives on: May 28, 2012, 12:21:08 AM
I'm not sure...I had a hard time setting it up early on. After I finally put Debian on the SD, I couldn't get the external HD to work, and I thought it had something to do with its large size. I had a USB key working though. I experimented various things, but never really set up a HD because I wasn't using it as a server on a regular basis.
2  Linux Stuff / General Linux questions / problems mounting external USB hard drives on: May 27, 2012, 07:33:58 AM
Hello,
I have a sheevaplug running Debian (2.6.32-5-kirkwood) on an SD card. Everything is running smoothly except that I cannot mount external USB drives.

Trying to connect a USB drive gives:
Code:
dmesg | tail
[  202.191072] usb 1-1: new high speed USB device using orion-ehci and address 2
[  202.343225] usb 1-1: New USB device found, idVendor=067b, idProduct=2507
[  202.349964] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  202.357147] usb 1-1: Product: Mass Storage Device
[  202.361888] usb 1-1: Manufacturer: Prolific Technology Inc.
[  202.367489] usb 1-1: SerialNumber: 0
[  202.373016] usb 1-1: configuration #1 chosen from 1 choice
[  202.456271] scsi_mod: Unknown symbol blk_get_queue
[  202.467174] scsi_mod: Unknown symbol blk_put_queue
[  202.490700] scsi_mod: Unknown symbol blk_get_queue
[  202.501623] scsi_mod: Unknown symbol blk_put_queue

# fdisk -l  does not show the USB drive.

I get this with several different hard drives (1TB Western Digital, 40GB 2.5", USB thumbdrive, with or without external USB hub, etc.). There is very little information on the web regarding a "scsi_mod: Unknown symbol..." error. One forum discusses issues with the kernel not being flashed properly: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644850
However, running flash-kernel and rebooting doesn't help.

Any ideas about what could be wrong? Should I try a different kernel ? I'm at a loss here. Any advice would be appreciated.

3  Linux Stuff / General Linux questions / Re: problems enabling UBIFS on NAND on: February 14, 2010, 01:38:28 PM
duh! You were right, the md5sums did not match. That'll teach me not to check large files when I copy them (especially on USB keys).

Now ubiformat works, but it fails when I try to ubiattach it. The problem looks very similar  to this thread:
http://plugcomputer.org/plugforum/index.php?topic=1279.15
Same ubimkvol error initially, similar ubiattach errors. Apparently the same kernel. At some point, I may try to rebuild the kernel as suggested, but not in the short term...

thanks for your precious help, pingtoo.

4  Linux Stuff / General Linux questions / Re: problems enabling UBIFS on NAND on: February 13, 2010, 09:01:10 AM
I haven't used an SD card. To make the ubi.img file, I plugged my USB-key on a laptop with an up-to-date karmic system. I later rebooted the plug with the USB-key with 2.6.32-trunk-kirkwood, with a copy of ubi.img . On both systems, I have mtd-utils 20090606-1.

How can I check if the ubi.img is corrupted?

I am thinking about trying with an SD card, so I can do the whole procedure on the plug.
5  Linux Stuff / General Linux questions / problems enabling UBIFS on NAND on: February 13, 2010, 07:34:17 AM
This is my first post here. I have only limited experience with devices like the sheevaplug, but hopefully my explanations will make sense.

I first followed the 'Installing Debian to Flash' howto:
http://plugcomputer.org/plugwiki/index.php/Installing_Debian_To_Flash
I installed debian on a USB-key, and later got stuck at the ubimkvol command when trying to convert the internal flash tu ubifs:
Code:
ubimkvol /dev/ubi0 -N rootfs -m
Set volume size to 517386240
[10341.904532] UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 0:512, written 0 bytes
[10341.913664] UBI warning: ubi_eba_write_leb: failed to write VID header to LEB 2147479551:0, PEB 0
[10341.923269] UBI: try another PEB
[10341.926701] UBI: run torture test for PEB 0
[10341.931504] UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 4055:512, written 0 bytes
[10341.940874] UBI warning: ubi_eba_write_leb: failed to write VID header to LEB 2147479551:0, PEB 4055
[10341.976543] UBI: try another PEB
[10342.147505] UBI: PEB 0 passed torture test, do not mark it a bad
[10342.155682] UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 4054:512, written 0 bytes
[10342.165058] UBI warning: ubi_eba_write_leb: failed to write VID header to LEB 2147479551:0, PEB 4054
[10342.175067] UBI: run torture test for PEB 4055
[10342.196798] UBI: try another PEB
[10342.376145] UBI: PEB 4055 passed torture test, do not mark it a bad
[10342.384607] UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB 0:512, written 0 bytes
[10342.393726] UBI warning: ubi_eba_write_leb: failed to write VID header to LEB 2147479551:0, PEB 0
[10342.403170] UBI: run torture test for PEB 4054
[10342.419413] UBI warning: ubi_ro_mode: switch to read-only mode
[10342.436434] UBI error: ubi_create_volume: cannot create volume 0, error -30
ubimkvol: error!: cannot UBI create volume
          error 30 (Read-only file system)

My problem seems very similar to this thread: http://plugcomputer.org/plugforum/index.php?topic=1279.msg8119#msg8119
I followed pingtoo's advice, and went along this howto: http://www.plugcomputer.org/plugwiki/index.php/Enabling_UBIFS
My system is on a USB-key. I plugged the key into my laptop, and made the ubi.img file this way:

sudo mkfs.ubifs -r /mnt/sheeva/ -m 2048 -e 129024 -c 4096 -o ubifs.img
sudo ubinize -v -o ubi.img -m 2048 -p 128KiB -s 512 ubi.cfg

I copied ubi.img (242MB) back to the USB-key, rebooted the sheevaplug with it, and went along:

Code:
ubiformat /dev/mtd2 -s 512 -f ubi.img

ubiformat: mtd2 (nand), size 531628032 bytes (507.0 MiB), 4056 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 4055 -- 100 % complete 
ubiformat: 4052 eraseblocks have valid erase counter, mean value is 5
ubiformat: 2 eraseblocks are supposedly empty
ubiformat: bad eraseblocks: 1075, 2684
ubiformat: flashing eraseblock 449 -- 22 % complete  ubiformat: error!: bad UBI magic 0x5744444e, should be 0x55424923
ubiformat: error!: bad EC header at eraseblock 449 of "/home/shami/ubi/ubi.img"

I tried the procedure twice, with similar errors. Did I misunderstand how to  create ubi.img on another pc? Is there a proper way?
Thanks in advance for any help.
Pages: [1]