Cannot access 5big network 2

[Mijzelf]

Work around: Download fun_plug.tgz. Tftp it to the NAS. Then

Code: Select all

mkdir /ffp
cd /ffp
tar xzf /path/to/fun_plug.tgz
rm /path/to/fun_plug.tgz

/ffp/bin/cp -r /tmp/mountpoint/shares/1 /tmp/usbdisk/

[pacco]

I really have to go now. Will be back on Thursday with a usb bay.
Will leave the Lacie on as it is right now.

Thanks so far and hopefully we can find a solution! It was all about the big files wasn't it :-)

@Mijzelf, will try the fun_plug.tgz on Thursday.

Bye for now and once again thank you very much!

Frank

[Jocko]

as ffp requires around 122MB and it will be load in RAM I am pretty sure it is too big. Currently, you should have as free space 130-140MB.

So the work around of the work around is to install it on your usb disk or wait the static cp binary (I think that fvdw can compile it this evening)

So

Code: Select all

mkdir /tmp/usbdisk/ffp
cd /tmp/usbdisk/ffp
tar xzf /path/to/fun_plug.tgz
rm /path/to/fun_plug.tgz


and create a symlink

Code: Select all

ln -s  /tmp/usbdisk/ffp /ffp

You need to create again only the symlink after a boot

[Mijzelf]

as ffp requires around 122MB and it will be load in RAM I am pretty sure it is too big. Currently, you should have as free space 130-140MB.

:shock: I can hardly imagine that the stand alone kernel will need more than 24MB. And the box has 512 MB. So I think at least 450MB should be available.

[Jocko]

I must be tired... Indeed I made two errors: take as available RAM 256MB and confuse about the memory used( I believed have read somewhere only 130MB was available) :whistle

The kernel uses around 11-12MB.

anyhow save ffp on the usb avoid to download it at each boot...

I made some additional tests about the usb port with a nwsp2 which uses the same kernel standalone version and I succeeded to mount an ext3 USB partition...

Code: Select all

[  458.603753] usb 1-1: USB disconnect, device number 2
[  530.316077] usb 1-1: new high speed USB device number 3 using orion-ehci
[  530.467192] usb 1-1: New USB device found, idVendor=152d, idProduct=2329
[  530.473891] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[  530.481036] usb 1-1: Product: USB to ATA/ATAPI bridge
[  530.486085] usb 1-1: Manufacturer: JMicron
[  530.490206] usb 1-1: SerialNumber: F607355FFFFF
[  530.496206] usb-storage 1-1:1.0: Quirks match for vid 152d pid 2329: 8020
[  530.503067] scsi3 : usb-storage 1-1:1.0
[  531.548823] scsi 3:0:0:0: Direct-Access     Hitachi  HDT721010SLA360       PQ: 0 ANSI: 2 CCS
[  531.557762] No LaCie disk map available
[  531.562850] sd 3:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[  531.572217] sd 3:0:0:0: [sdb] Write Protect is off
[  531.577160] sd 3:0:0:0: [sdb] Mode Sense: 28 00 00 00
[  531.577178] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[  531.585087] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[  531.625862]  sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 >
[  531.635719] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[  531.641852] sd 3:0:0:0: [sdb] Attached SCSI disk
[  582.178664] EXT3-fs: barriers not enabled
[  582.196457] EXT3-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
[  582.205225] kjournald starting.  Commit interval 5 seconds
[  582.211245] EXT3-fs (sdb1): using internal journal
[  582.216049] EXT3-fs (sdb1): recovery complete
[  582.221111] EXT3-fs (sdb1): mounted filesystem with ordered data mode


So there is something wrong with 5big2.

[Mijzelf]

I must be tired

Happens to the best.

[Jocko]

It is an issue with the last version of fvdw-sl console (5.4).

Indeed with the previous version, the usb device is detected (my previous post) where as with the last version 5.4, the same usb device is never detected. :whistle
So something to deepen

[fvdw]

It is an issue with the last version of fvdw-sl console (5.4).

Indeed with the previous version, the usb device is detected (my previous post) where as with the last version 5.4, the same usb device is never detected. :whistle
So something to deepen

mmm...it must be then the standalone kernel not the fvdw-sl console itself as the kernel does the loading, let me check the config file of the last standalone kernel

---edit :mrgreen: yep I forgot to enable the usb driver, it is now compiled as module. I will recompile it and post an updated kernel

Code: Select all

CONFIG_USB_EHCI_HCD_ORION=m


I enabled the ehci driver and storage driver for usb but forgot that in newer kernels also ehci_hcd_orion driver must be added. :whistle
sorry for this. The compiler will be put to work for a new kernel

[Jocko]

@fvdw,

did you note this previous post about a static cp command: viewtopic.php?f=26&t=2209&start=120#p18786

[fvdw]

@fvdw,

did you note this previous post about a static cp command: viewtopic.php?f=26&t=2209&start=120#p18786

yes I saw that but I need to llok if that is going to work, not all binaries can be compiled static.

About the usb issue of the new standalone kernel. I recompiled the kernel but I see some issues when activating usb driver, need more time to find out what is causing this