Quantcast
Channel: Linux Device Hacking - Debian
Viewing all 26847 articles
Browse latest View live

Re: LG N1T1 NAS

$
0
0
yongki,

> Hi, I have LG NAS N2B1
>
> in my case, success on step 6 but step 10 fail to
> booting.

Which procedure are you using (step 6 and step 10 from where)? Can you post the log of your attempt?

> I think n2b1's dtb is not same with n1t1's.
> ( cat /root/dts/kirkwood-n1t1.dtb >> zImage.fdt)

Do you have a list of the N2B1 specifications? how does that compare to the N1T1? i.e. what are the differences or the same?

It might be possible if they simliar and there is only some minor differences.

You do need to post a lot more information so we can see if it possible to create a different DTS/DTB for this N2B1 box.

Re: Zyxel NAS326 - Debian / Boot from USB?

$
0
0
nielsek,

> I attached serial and it seems that both NANDs are
> corrupt. NAND2 doesn't boot at all, NAND1 is tryi
> ng but can't attach ubi.

Yes it does look like both were corrupted.

> It should be possible to write firmware again from
> debian or u-boot? I'm unable to find instructions
> though.

Yes. If you have saved your mtds using nanddump then you could write them back. Did you? If not, somebody needs to upload their mtds for you. I could, but it will take some time (I have a slow upload speed internet).

These are about 240MB:
0x000000e00000-0x000001d00000 : "Kernel-1"
0x000001d00000-0x000008700000 : "RootFS-1"
0x000008700000-0x000009600000 : "Kernel-2"
0x000009600000-0x000010000000 : "RootFS-2"

Let's wait until tomorrow. If there is no one has uploaded them by then. I'll create a tarball and upload it to Dropbox.

Re: Zyxel NAS326 - Debian / Boot from USB?

$
0
0
Thanks in advance!
Unfortunately I don't have copies of them myself. I did backups of them, but after I ran into problems :-(

Re: LG N1T1 NAS

$
0
0
Normal mode boot start!

_   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** LGE-NAS BOARD: NC1 LE 

U-Boot 1.1.4 (Feb 24 2012 - 15:06:45)NC1

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006D0700

Soc: 88F6192 A1 CPU running @ 1000Mhz L2 running @ 500Mhz
SysClock = 250Mhz , TClock = 166Mhz 

DRAM (DDR2) CAS Latency = 3 tRP = 3 tRAS = 8 tRCD=3
DRAM CS[0] base 0x00000000   size 128MB 
DRAM Total size 128MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:nand_bbm_init: Init nand bad block information...
nand_bbm_find_pos: nand_bbm_check = 0, erasesize = 20000
nand_bbm_find_pos: nand_bbm_find_pos: bbm pos = 7800000, pos = 7800000
Loading nand bad block info(07800000+00020000)...
nand_bbm_info_load: bbm->magic        = 8192a5a7
nand_bbm_info_load: bbm->bb_count     = 1
nand_bbm_info_load: bbm->assign_index = 3fe
nand_bbm_info_load: [0 (0:0)] maps(2c6->3ff) pos(58c0000->7fe0000)
Assign index = 3fe
nand_bbm_info_load: Loading nand bad block info...ok
128 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
 Normal mode : lg_bootmode = 0 
Hit any key to stop autoboot:  0 
LGE-NAS>>   usb start
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
       scanning bus for storage devices... 1 Storage Device(s) found
LGE-NAS>>   ext2load usb 0:1 0x800000 /boot/uImage
....
................................................................................................................................................................................................................................................................................................................................

3326598 bytes read
LGE-NAS>>   setenv console console=ttyS0,115200 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env)
LGE-NAS>>   setenv bootargs_usb root=/dev/sda1 rw rootdelay=10 rootfstype=ext3
LGE-NAS>>   setenv bootargs $(console) $(bootargs_usb)
LGE-NAS>>
LGE-NAS>> bootm 0x800000

....


Debian GNU/Linux 8 debian ttyS0

debian login: root
Password:
Last login: Sat Mar 25 21:12:03 PDT 2017 on ttyS0
Linux debian 4.4.0-n1t1-tld-1 #1 PREEMPT Tue Mar 15 14:10:10 CET 2016 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@debian:~#

root@debian:~#tar jxvf linux-4.6.0-kirkwood-tld-1-bodhi.tar.bz2
...
root@debian:~#tar xvf linux-dtb-4.6.0-kirkwood-tld-1.tar
...
root@debian:~# dpkg -i linux-image-4.6.0-kirkwood-tld-1_1.0_armel.deb
Selecting previously unselected package linux-image-4.6.0-kirkwood-tld-1.
(Reading database ... 12657 files and directories currently installed.)
Preparing to unpack linux-image-4.6.0-kirkwood-tld-1_1.0_armel.deb ...
Examining /etc/kernel/preinst.d/
Done.
Unpacking linux-image-4.6.0-kirkwood-tld-1 (1.0) ...
Setting up linux-image-4.6.0-kirkwood-tld-1 (1.0) ...

Hmm. There is a symbolic link /lib/modules/4.6.0-kirkwood-tld-1/build
However, I can not read it: No such file or directory
Therefore, I am deleting /lib/modules/4.6.0-kirkwood-tld-1/build


Hmm. The package shipped with a symbolic link /lib/modules/4.6.0-kirkwood-tld-1/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/4.6.0-kirkwood-tld-1/source

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.6.0-kirkwood-tld-1 /boot/vmlinuz-4.6.0-kirkwood-tld-1
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.6.0-kirkwood-tld-1 /boot/vmlinuz-4.6.0-kirkwood-tld-1
update-initramfs: Generating /boot/initrd.img-4.6.0-kirkwood-tld-1
run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 4.6.0-kirkwood-tld-1 /boot/vmlinuz-4.6.0-kirkwood-tld-1


root@debian:/boot# cp -a /root/zImage-4.6.0-kirkwood-tld-1 zImage.fdt
root@debian:/boot# cat /root/dts/kirkwood-n1t1.dtb >> zImage.fdt
Linux-4.6.0-kirkwood-tld-1 -d zImage.fdt uImage kernel -C none -a 0x00008000 -n
Image Name: Linux-4.6.0-kirkwood-tld-1
Created: Sun Mar 26 04:38:57 2017
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3269366 Bytes = 3192.74 kB = 3.12 MB
Load Address: 00008000
Entry Point: 00008000
uInitrd000 -n initramfs-4.6.0-kirkwood-tld-1 -d initrd.img-4.6.0-kirkwood-tld-1
Image Name: initramfs-4.6.0-kirkwood-tld-1
Created: Sun Mar 26 04:39:03 2017
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7251403 Bytes = 7081.45 kB = 6.92 MB
Load Address: 00000000
Entry Point: 00000000

root@debian:/boot# sync
root@debian:/boot# reboot

....

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
 Normal mode : lg_bootmode = 0 
Hit any key to stop autoboot:  0 
LGE-NAS>>   usb start
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
       scanning bus for storage devices... 1 Storage Device(s) found
LGE-NAS>>   ext2load usb 0:1 0x800000 /boot/uImage
....
.
......
............
.........................
...................................................
......................................................................................................
..................................................................................................................

3269430 bytes read
LGE-NAS>>   ext2load usb 0:1 0x1100000 /boot/uInitrd
....
.
......
............
.........................
...................................................
......................................................................................................
............................................................................................................................................................................................................
....
.....................................................................................................................................................................................................................................................................................................

7251467 bytes read
LGE-NAS>>   setenv bootargs $(console) $(bootargs_usb)
LGE-NAS>> bootm 0x800000 0x1100000

7251467 bytes read
LGE-NAS>>   setenv bootargs $(console) $(bootargs_usb)
LGE-NAS>> bootm 0x800000 0x1100000
## Booting image at 00800000 ..., header_size = 00000040, header_addr = 0069024c
image_header_t hdr contents
hdr->ih_magic = 56190527, hdr->ih_hcrc = a064e8d6
hdr->ih_time = 51a8d758, hdr->ih_size = 0031e2f6
hdr->ih_load = 00800000, hdr->ih_ep = 00800000
hdr->ih_dcrc = e6257564
hdr->ih_os = 05, hdr->ih_arch = 02
hdr->ih_type = 02, hdr->ih_comp = 00
hdr->ih_name = Linux-4.6.0-kirkwood-tld-1

   Image Name:   Linux-4.6.0-kirkwood-tld-1
   Created:      2017-03-26  11:38:57 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3269366 Bytes =  3.1 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000, header_addr = 0069024c, header_size = 00000040 ...
RAMdisk image_header_t hdr contents
hdr->ih_magic = 56190527, hdr->ih_hcrc = ba9adaf7
hdr->ih_time = 57a8d758, hdr->ih_size = 006ea5cb
hdr->ih_load = 00000000, hdr->ih_ep = 00000000
hdr->ih_dcrc = 0e1244dc
hdr->ih_os = 05, hdr->ih_arch = 02
hdr->ih_type = 03, hdr->ih_comp = 01
hdr->ih_name = initramfs-4.6.0-kirkwood-tld-1

   Image Name:   initramfs-4.6.0-kirkwood-tld-1
   Created:      2017-03-26  11:39:03 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7251403 Bytes =  6.9 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


...

[    4.749649] i2c /dev entries driver
[    4.754918] hidraw: raw HID events driver (C) Jiri Kosina
[    4.760877] drop_monitor: Initializing network drop monitor service
[    4.767455] NET: Registered protocol family 17
[    4.772169] Key type dns_resolver registered
[    4.777453] registered taskstats version 1
[    4.781579] Loading compiled-in X.509 certificates
[    4.786456] zswap: loaded using pool lzo/zbud
[    4.801304] Key type encrypted registered
[    4.805982] hctosys: unable to open rtc device (rtc0)
[    4.813768] Freeing unused kernel memory: 304K (c0824000 - c0870000)
[    4.820210] This architecture does not have kernel memory protection.
Loading, please wait...
[    4.908684] systemd-udevd[83]: starting version 215
[    4.926198] random: systemd-udevd urandom read with 8 bits of entropy available
[    5.119631] SCSI subsystem initialized
�



========================================

specifications : https://www.cnet.com/products/lg-n2b1-nas-server-2-tb/specs/

thanks in advance!!!

Re: USB serial console connected, lost root password

$
0
0
Tushar Wrote:
-------------------------------------------------------
> Hi,
>
> I have my Pogoplug V4 connected via serial cable w
> hich is on U-Boot 2016.05-tld-1 (June 12 2016 ....
> ) I forgot my Debian's root password. Is there any
> way I can reset the password? -or- most preferably
> , I like to re-install the rootfs/linux (debian) o
> n a new flash drive - how can I do that ?
>
> Thanks,
>
> Tushar.

-- Actually what I meant here if it is possible to install rootfs/ (debian-linux) right from the serial console? in my pogopolug series 4 model, I get "Pogov4>" prompt which doesn't have /tmp path or any "linux" like environment so that I could extract the rootfs as described in topic http://forum.doozan.com/read.php?2,12096

Re: USB serial console connected, lost root password

$
0
0
Tushar,

> -- Actually what I meant here if it is possible to
> install rootfs/ (debian-linux) right from the seri
> al console?

No, it is not possible. It has be done inLinux. Any Linux system would work.

Re: LG N1T1 NAS

$
0
0
yongki,

First, please use code tags when posting log.

1. How did you create this rootf? was it based on my Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs ? And if true, did you compile the 4.4.0-n1t1-tld-1 kernel?

Debian GNU/Linux 8 debian ttyS0 

debian login: root 
Password: 
Last login: Sat Mar 25 21:12:03 PDT 2017 on ttyS0 
Linux debian 4.4.0-n1t1-tld-1 #1 PREEMPT Tue Mar 15 14:10:10 CET 2016 armv5tel

2. At this point, is the box running OK? any thing different from the N1T1?

3. Your box is not the same as the N1T1. The N1T1 use the 6281 SoC

Your box
Soc: 88F6192 A1 CPU running @ 1000Mhz L2 running @ 500Mhz
SysClock = 250Mhz , TClock = 166Mhz

N1T1
Soc: 88F6281 A1 (DDR2)
CPU running @ 1000Mhz L2 running @ 333Mhz
SysClock = 333Mhz , TClock = 200Mhz


4. Your box is not the N2B1 either! It's the same SoC, but running at a different clock
** LGE-NAS BOARD: NC1 LE
...
Soc: 88F6192 A1 CPU running @ 1000Mhz L2 running @ 500Mhz
SysClock = 250Mhz , TClock = 166Mhz

In the link you posted, the N2B1 SoC is the same as yours, but running at a slower clock speed, exactly like the Pogo V4.
Processors Installed Marvell 88F6192 800 MHz
RAM Installed DRAM 128 MB

-------

So not sure what your intention is. If you can run the "Linux debian 4.4.0-n1t1-tld-1" kernel without propblem, then you shoudl use the DTB from that box, which is Ron's version that I incorporated into the kernel since 4.4+.

But when you install the kernel 4.6, it does not work any more? is that the question?

Note: at each section of log that you posted, please write a short sentence of what you want to say about that snippet of log. Does not have to be long (lot of us here are not native English speakers), just enough to say what you want to convey.

Re: USB serial console connected, lost root password

$
0
0
bodhi Wrote:
-------------------------------------------------------
> Tushar,
>
> > -- Actually what I meant here if it is possible
> to
> > install rootfs/ (debian-linux) right from the se
> ri
> > al console?
>
> No, it is not possible. It has be done inLinux. An
> y Linux system would work.

So, I went ahead and formatted an USB stick on my laptop (running Debian 8) and copied whole "linux-4.10.0-kirkwood-tld-1-bodhi.tar.bz2" to the /boot directory, extract the archive and now, getting following error while I try to run dpkg install command...

note that, I manually created /boot directory inside the usb stick labeled as 'rootfs'

root@atlantis:/media/root/rootfs/boot# dpkg -i linux-image-4.10.0-kirkwood-tld-1_1.0_armel.deb
dpkg: error processing archive linux-image-4.10.0-kirkwood-tld-1_1.0_armel.deb (--install):
package architecture (armel) does not match system (i386)
Errors were encountered while processing:
linux-image-4.10.0-kirkwood-tld-1_1.0_armel.deb

Re: USB serial console connected, lost root password

$
0
0
Tushar,

You can create the Debian rootfs on any Linux box, that's what I meant.

To install newer kernel, you need to do it in the system while Debian is running. Or using chroot in the host system.

What you did using dpkg is not creating rootfs, you tried to install a newer kernel. This is the section you need to follow:

Quote

Updated 20 Feb 2016:

This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1.

Basic minimal Debian Kirkwood rootfs for most Kirwood plugs:

Re: Zyxel NAS326 - Debian / Boot from USB?

Re: Deb on Medion MD86783 (Soc: 88F6702 Marvell Feroceon 88FR131)

$
0
0
hi bodhi,
hi pengu,

i confirm that the device won't boot with the mentioned DTB. As always without a response.

@pengu
Have you seen the "strange" broadcasts the Medion NAS does while in Recovery? Its shouting "Hail dictator-of-germany-'till-1945"... in my network oO

Re: Kirkwood and Oxnas Samba Performance

$
0
0
Well, the "server" side used a crappy Realtek 1000M card... (Linux Server01 3.16.0-4-686-pae #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) i686 GNU/Linux on Intel Q6600 with 3GB memory)

For Dockstar / Kirkwood system (Linux Dockstar01 3.9.5-dockstar-goflex-shyd #3 Sun Jun 9 11:36:48 CEST 2013 armv5tel GNU/Linux)

# iperf -c 192.168.7.201 -r
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.7.201, TCP port 5001
TCP window size:  117 KByte (default)
------------------------------------------------------------
[  3] local 192.168.7.17 port 33542 connected with 192.168.7.201 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec   857 MBytes   719 Mbits/sec
[  5] local 192.168.7.17 port 5001 connected with 192.168.7.201 port 47774
[  5]  0.0-10.0 sec   734 MBytes   615 Mbits/sec



=======================================================
For Pogoplug Pro / Oxnas system (Debian Wheezy, Linux PogoPro 3.18.5-oxnas-tld-1 #2 SMP PREEMPT Thu Feb 12 11:17:40 PST 2015 armv6l GNU/Linux )
(I tried another kernel version... not the same as I mentioned before)

#  iperf -c  192.168.7.201 -r
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.7.201, TCP port 5001
TCP window size:  175 KByte (default)
------------------------------------------------------------
[  5] local 192.168.7.18 port 46676 connected with 192.168.7.201 port 5001
[ ID] Interval       Transfer     Bandwidth
[  5]  0.0-10.0 sec   478 MBytes   401 Mbits/sec
[  4] local 192.168.7.18 port 5001 connected with 192.168.7.201 port 51278
[  4]  0.0-10.0 sec   412 MBytes   345 Mbits/sec

Pogoplug Pro with latest kernel (Jessie)

root@PogoPro:~# uname -a
Linux PogoPro 4.4.54-oxnas-tld-1 #2 SMP PREEMPT Sat Mar 18 23:09:58 PDT 2017 armv6l GNU/Linux
root@PogoPro:~# iperf -c 192.168.7.201 -r
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.7.201, TCP port 5001
TCP window size:  118 KByte (default)
------------------------------------------------------------
[  5] local 192.168.7.18 port 45262 connected with 192.168.7.201 port 5001
[ ID] Interval       Transfer     Bandwidth
[  5]  0.0-10.0 sec   366 MBytes   307 Mbits/sec
[  4] local 192.168.7.18 port 5001 connected with 192.168.7.201 port 51280
[  4]  0.0-10.0 sec   353 MBytes   296 Mbits/sec

Looks like even worse than old wheezy with old kernel.


Maybe this can explain why the Mfr. changed back to Kirkwood?


If you need more tests, tell me.

Re: Kirkwood and Oxnas Samba Performance

$
0
0
Thanks daviddyer,

That's a big drop in performance! I suspected this because the same smb config should behave the same way, considering we are using mainline Debian packages. The only significant difference is the ethernet driver which is an OXNAS version, versus Marvell version.

I'll take a peek at this code to see if I can find anything.

I think we also should run a Kirkwood-->OXNAS and Kirkwood-->Kirkwood iperf tests. That'll narrow down the problem further (Realtek is not that good a card comparing to Marvell).

Re: Wiki

$
0
0
Added daviddyer's benchmarks

Quote

Kirkwood vs OXNAS network performance

Re: Kirkwood and Oxnas Samba Performance

$
0
0
By the way, it was a really good test :)

I think the OpenWRT/LEDE version in 4.4.54-tld-1 might have made it even worse.

Re: Kirkwood and Oxnas Samba Performance

$
0
0
Kirkwood/Dockstar to Kirkwood/Dockstar (Both has 3.9.5 kernel)

# iperf -c 192.168.7.27 -r
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.7.27, TCP port 5001
TCP window size:  164 KByte (default)
------------------------------------------------------------
[  3] local 192.168.7.17 port 56289 connected with 192.168.7.27 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec   892 MBytes   748 Mbits/sec
[  5] local 192.168.7.17 port 5001 connected with 192.168.7.27 port 49458
[  5]  0.0-10.0 sec   894 MBytes   750 Mbits/sec

Oxnas / Pogoplug Pro to Kirkwood / Dockstar

root@PogoPro:~# iperf -c 192.168.7.27 -r
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.7.27, TCP port 5001
TCP window size: 74.4 KByte (default)
------------------------------------------------------------
[  5] local 192.168.7.18 port 49320 connected with 192.168.7.27 port 5001
[ ID] Interval       Transfer     Bandwidth
[  5]  0.0-10.0 sec   456 MBytes   382 Mbits/sec
[  4] local 192.168.7.18 port 5001 connected with 192.168.7.27 port 33083
[  4]  0.0-10.0 sec   955 MBytes   801 Mbits/sec

Oxnas / PogoPro to Oxnas / PogoPro

root@Pro02:~# iperf -c 192.168.7.18 -r
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.7.18, TCP port 5001
TCP window size: 43.8 KByte (default)
------------------------------------------------------------
[  4] local 192.168.7.58 port 47564 connected with 192.168.7.18 port 5001
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec   506 MBytes   424 Mbits/sec
[  5] local 192.168.7.58 port 5001 connected with 192.168.7.18 port 41192
[  5]  0.0-10.0 sec   600 MBytes   503 Mbits/sec

Re: Kirkwood and Oxnas Samba Performance

$
0
0
If we can't improve Oxnas's network performance, I guess we don't need to continue the project of adding usb 3.0 to pogoplug pro...

Re: Kirkwood and Oxnas Samba Performance

$
0
0
daviddyer Wrote:
-------------------------------------------------------
> If we can't improve Oxnas's network performance, I
> guess we don't need to continue the project of add
> ing usb 3.0 to pogoplug pro...

That's a different issue altogether. Just increasing the speed of the disk drive would make the transfer rate substantially faster. Curently the Pogo V3 network is slow, but not that slow to the point where USB3.0 is brought down to USB 2.0 speed!

Re: Kirkwood and Oxnas Samba Performance

$
0
0
Well, I tried sata boot Pogoplug Pro then samba, the hard drive I used is quite old, (still a lot faster than USB 2.0 hard drive, About 70MB/s read), samba read speed was about 18MB/s for big files.

Re: Zyxel NAS326 - Debian / Boot from USB?

$
0
0
bodhi Wrote:
-------------------------------------------------------
> Uploading...

Awesome, thanks!
Viewing all 26847 articles
Browse latest View live
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>