Re: [ts-7000] Problem with USB-drive development system

[Jason Stahls <>]

A few things....

1)  I found it much easier to use NFS for booting Debian, I at first ran a USB-IDE adaptor and had a 60gig hard drive connected to my 7200 but Debian never really ran "right" like that, always had some error or whatnot

2)  You need to edit /etc/fstab on the USB key since your root FS is not /dev/hda1, it's probably /dev/sda1 or /dev/scsi/host0/target0/lun0/part1 or similar.

Jason

Pasqual Nebot wrote:

Recently I have installed the debian-woody-256MB-10-27-2005.tar.bz2 from

the embeddedarm ftp to a USB drive following the "linuxarm-guide-rev2.0.pdf"

instructions.

But there is a problem when I try to run the scripts to change root into the

debian USB thumb drive, so...I need your help, please.

 

$ loadUSBModules.sh

Using /lib/modules/2.4.26-ts9/kernel/drivers/usb/usbcore.o
Using /lib/modules/2.4.26-ts9/kernel/arch/arm/common/pcipool.o
Using /lib/modules/2.4.26-ts9/kernel/drivers/usb/host/usb-ohci.o
Using /lib/modules/2.4.26-ts9/kernel/drivers/usb/host/usb-ohci-ep93xx.o
Using /lib/modules/2.4.26-ts9/kernel/drivers/scsi/scsi_mod.o
Using /lib/modules/2.4.26-ts9/kernel/drivers/scsi/sd_mod.o
Using /lib/modules/2.4.26-ts9/kernel/drivers/usb/storage/usb-storage.o

$ loadUSB.sh

Creating extra device nodes...done.
Started device management daemon v1.3.25 for /dev
modprobe: cannot create /var/log/ksymoops/20061017.log Read-only file system
modprobe: cannot create /var/log/ksymoops/20061017.log Read-only file system
Checking root file system...
fsck 1.27 (8-Mar-2002)
e2fsck 1.27 (8-Mar-2002)
modprobe: cannot create /var/log/ksymoops/20061017.log Read-only file system
modprobe: cannot create /var/log/ksymoops/20061017.log Read-only file system
modprobe: cannot create /var/log/ksymoops/20061017.log Read-only file system
modprobe: cannot create /var/log/ksymoops/20061017.log Read-only file system
modprobe: cannot create /var/log/ksymoops/20061017.log Read-only file system
modprobe: cannot create /var/log/ksymoops/20061017.log Read-only file system
fsck.ext2: No such file or directory while trying to open /dev/hda1

 

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

 

fsck failed.  Please repair manually and reboot.  Please note
that the root file system is currently mounted read-only.  To
remount it read-write:

 

   # mount -n -o remount,rw /

 

CONTROL-D will exit from this shell and REBOOT the system.

__._,_.___

SPONSORED LINKS

Single board computer	Hardware	Computer running slow
Linux os	Single board

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: =Email Delivery: Digest | m("yahoogroups.com?subject","ts-7000-fullfeatured");=Change Delivery Format: Fully Featured">Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | =Unsubscribe

__,_._,___