[RAID1] Need some advice on setting up a second disk

[Jocko]

@fvdw

On Internet, I found this page : http://www.steppen-wolf.eu/blog/2009/11 ... -and-more/

Please to note this sentence:

Sinteticamente è un sistema operativo linux con un kernel decisamente datato (sic!) compilato per processori con architettura arm, cpu a 400mhz, 64mb di ram (i nuovi modelli hanno 128 mb di ram) e bootloader uboot.

<=>

Synthetically is a Linux operating system kernel with a very dated (sic) compiled for processors with architecture arm, cpu to 400mhz, 64mb of ram (the new models have 128 MB of RAM) and uboot bootloader.

So exists a version with 128MB

Confirmed by several pages like this one: http://www.opineo.pl/opinie-620723-laci ... 0-rai.html

[danyboy666]

I will try and get those images for your but i can't garantee they will be the clearest since i can only use an iphone at this time.

In the mean while i'll upload your patch and see if this solve my transfer issues.

btw what control code should i be using to upload this patch?

edit: a simple "unzip" did the trick.

[danyboy666]

http://imgur.com/a/Bs6Gd

The pack was too big to upload on the forum so i've uploaded them to imgur.

No the clearest as i said but still clear enough to see the PCB model/rev.

"Lacie 2Big rev. c"

[danyboy666]

Found another 2big version with 512MB!!!

In 2012, LACIE release a new version with 2 disks 3TB and RAM size 512MB : http://www.59hardware.net/dossier/stock ... 12469.html (Sorry French page)

Sur la face opposée du PCB, la puce mémoire y est soudée. Elle est de la marque Hynix et sa capacité est de 512MB.

<=>

On the opposite side of the PCB, the memory chip is welded. It is the Hynix brand and its capacity is 512MB.

Oh with e-SATA too :P but with a single USB 2 port. Also the power switch on this one only have two position (on | off)

[danyboy666]

hdparm report very slow speed for what these drives are able to do.

~100 MB/s write and ~50MB/s read these are far from the speed for which those drive were designed for. They are suppose to reach 7200 RPM so i would expect them to be comparable to my other WD's. FYI even my 2TB WD green which i'm removing from my VM is giving me better write/read speed.

I have a comparable HDD WD 3TB Blue on my VM

Code: Select all

/dev/sde:
 Timing cached reads:   15932 MB in  2.00 seconds = 7971.14 MB/sec
 Timing buffered disk reads: 384 MB in  3.03 seconds = 126.67 MB/sec
dferron@homeshare:~$ sudo hdparm -tT /dev/sdb


At least this would explain why this is running at less than USB2 speeds on my Gigabit network.

Any reason this is occuring in fvdw-sl?

Also i could not test the patch fo sendfile yet i deleted everything after recovering my stuff from nas. I'd have to be able to transfer a file at of least 2GB on the nas but with the "No space available error" i get every time i won't be able to do that test unless i create an iso and dump it directly on the nas which i did the first time. Note that this error is random as i got the same error while trying to transfer files less than 200MB. I've only seen the broken pipe error while trying to download big files on my win desktop.

I can definitely try again but given that there are so many issues with the compatility of this firmware with this nas i feel this is just a lost of time for now.

As for the RTC i would not expect they would design a PCB with no battery to keep the time on their nas. If they did that is a major design flaw imo. The nas would be able to keep it's time in case of power failure. I work with DS1307 for my home projects and even those need a battery to keep time.

As for trying to set time with internet (NTP) there is still that error mentionned on my other topic so i can't even remove the server i've put in the first field. Even if i want to clear the field it keeps coming back. Altough i am able to set another server address or IP i still get that error everytime. The OS is able to keep the correct time though anyways this is not major for now since i've set it up at my time zone and manually set the correct time. Too many other issues before trying to solved the RTC riddle.

Also the shutdown issue if this helps. When i sent the shutdown command via the web interface i get a message "Current System Status: The NAS is in Standby mode".

[fvdw]

http://imgur.com/a/Bs6Gd

The pack was too big to upload on the forum so i've uploaded them to imgur.

No the clearest as i said but still clear enough to see the PCB model/rev.

"Lacie 2Big rev. c"

I compared the picture the only difference seems to be the memory chips.
So I have no idea why your rtc is not working.
One check do you have a file /dev/rtc0 and a symlink /dev/rtc pointing to /dev/rtc0 ?
Maybe we can find another member with a 2big1 of the newer generation to see if his rtc is working. I could have look to the newer kernels that support the 2big1 if there is a change in the setup files. I don't think so, as I used one of the more recent setups.
But because the error message is that it can't read the registers I can imagine that the GPIO pin assignment should be deffirent

about battery, the rtc doesn't need one, of course time is lost when it powers off, see picture of 2big1 here http://lacie.nas-central.org/wiki/File: ... boardl.jpg. Also the nwsp2 lite doens't has a battery to keep time.

About the 2big2 with 512MB, that is not a 2big1 vs 1 but a version 2 (6281 cpu)

[fvdw]

~100 MB/s write and ~50MB/s read these are far from the speed for which those drive were designed for. They are suppose to reach 7200 RPM so i would expect them to be comparable to my other WD's. FYI even my 2TB WD green which i'm removing from my VM is giving me better write/read speed.

I have a comparable HDD WD 3TB Blue on my VM

Code:
/dev/sde:
Timing cached reads: 15932 MB in 2.00 seconds = 7971.14 MB/sec
Timing buffered disk reads: 384 MB in 3.03 seconds = 126.67 MB/sec
dferron@homeshare:~$ sudo hdparm -tT /dev/sdb


At least this would explain why this is running at less than USB2 speeds on my Gigabit network.

Any reason this is occuring in fvdw-sl?

Yes it is not the firmware but the cpu and the limited amount of ram limiting the speed. To write to disk the cpu needs to do some calculation and control of the disk. You cannot compare this cpu and ram with a intel pentium running at 5 times the speed and have 10 times more ram.

Furthermore, you say that there are incompatibilities with the fvdw-sl firmware. Yest there are maybe some bugs and adjustments to be done for this nas. But as we don't have a 2big1 ourselves we need to get feedback from users, like you, to adapt the firmware to eliminate these issues.
ps the hwclock not working is not a real problem, as long as the system clock is running and synchronized with internet time all is well. Leds and so are cosmetic and nice to have but also cosmetic, the sendfile issue is because your nas is relative old and the hardware on your board isn't supporting it. It can be disabled....
The shutdown issue, what happens if you perform on the linux prompt (ssh server) if you give command poweroff -f
PS does the reboot command work ?
If the poweroff command doesn't work then als that might be a gpio assignment issue.

Final, its up to you to decide if you want to quite using this nas and our firmware, but at least our firmware could get it running which can not be said from the lacie firmware ;)

[danyboy666]

~100 MB/s write and ~50MB/s read these are far from the speed for which those drive were designed for. They are suppose to reach 7200 RPM so i would expect them to be comparable to my other WD's. FYI even my 2TB WD green which i'm removing from my VM is giving me better write/read speed.

I have a comparable HDD WD 3TB Blue on my VM

Code:
/dev/sde:
Timing cached reads: 15932 MB in 2.00 seconds = 7971.14 MB/sec
Timing buffered disk reads: 384 MB in 3.03 seconds = 126.67 MB/sec
dferron@homeshare:~$ sudo hdparm -tT /dev/sdb


At least this would explain why this is running at less than USB2 speeds on my Gigabit network.

Any reason this is occuring in fvdw-sl?

Yes it is not the firmware but the cpu and the limited amount of ram limiting the speed. To write to disk the cpu needs to do some calculation and control of the disk. You cannot compare this cpu and ram with a intel pentium running at 5 times the speed and have 10 times more ram.

Furthermore, you say that there are incompatibilities with the fvdw-sl firmware. Yest there are maybe some bugs and adjustments to be done for this nas. But as we don't have a 2big1 ourselves we need to get feedback from users, like you, to adapt the firmware to eliminate these issues.
ps the hwclock not working is not a real problem, as long as the system clock is running and synchronized with internet time all is well. Leds and so are cosmetic and nice to have but also cosmetic, the sendfile issue is because your nas is relative old and the hardware on your board isn't supporting it. It can be disabled....
The shutdown issue, what happens if you perform on the linux prompt (ssh server) if you give command poweroff -f
PS does the reboot command work ?
If the poweroff command doesn't work then als that might be a gpio assignment issue.

Final, its up to you to decide if you want to quite using this nas and our firmware, but at least our firmware could get it running which can not be said from the lacie firmware ;)

I know about clock and memory limitations don't worry about it. I guess i misread my hdparm test last night I should have stopped right there when i saw those results.

And as far as trying lacie firmware again. no. Just no. I'd better try to spend time to boot it up my PXE to install a slimmed down ubuntu instead of wasting my time of their firmware again.

And don't worry I'm not blaming fvdw-sl firmware either. It is an oustanding piece of software. I just should have realized earlier that this box was a real piece of crap that even a RPi can outperform. As i said i know there are some incompatibilities and as your guys pointed out to me several time now this is simply a matter of studying the harware which you guys didn't even know existed before i brought it up to this forum. Sorry if about the misunderstanding here.

If you guys can compile a new version later that might fix some issues with this i might give it another shot but i think at this point i've spent enough time on this. The only reason i would consider running this nas would be if i could reach Gigabit speed which i doubt any firmware in the world would fix that. Too bad i'm not working at the moment i think if i had the cash to send it i would donate this. The only reason i'm not considering it right now is it would probably cost me more than the box is worth right now. You might find it more useful than me anywais.

If you guys need some infos on this i'll boot it up for you and give what you guys need. I might reinstall fvdw with those 250GB seagate but as far as using my new 1TB's with this is think i've made my mind. I have other plans with them and some other hardware i can use them with.

in final all i can say is that companies will buy anything as long it is labelled SAFE. Even if they pay a thousand buck for a box which a USB3 can beat anytime.

[maikatisum]

I was about to start a new thread, but noticed this one had a similar post.

I've managed to start up my useless box thanks to your awesome firmware! Nice job. And that easy installation trick was so cool! I had a terminal connected and I was looking at the screen in awe.
IT was all good until I tried to copy some things, but this thing is so slow..
I just wanted to confirm that with you guys. I've got SSDs in it and I get a transfer speed of around 1MB/s :((

Firmware Version 2big1 fvdw-sl 16.0
Kernel: Linux 3.14.2 #6 Sat Nov 29 22:15:32 CET 2014

Don't think I've got the raid setup, could that be an issue?

[fvdw]

think you might have a partiton alignment problem,
ssd need special formatting and partition setup if I remember well, if not you don't do that writing and reading can be slow
You need to find information on this for the type you have used to see if there is a requirement to align partitions