ReadyNAS Duo v2 & NV+ v2 File Protocol

iesus wrote:
I have a few questions about my new NV+ V2 unit.

What version of RAIDiator are you running?

iesus wrote:
How are you doing woth those updates, i need FTP or NFS or SSH access (due to my permission problems below).

SSH access is already available via the EnableRootSSH add-on for ARM. See e.g. http://www.readynas.com/forum/viewtopic.php?p=338927#p338927

iesus wrote:
Also i cant install any addons bc. i get the message "invalid update image"

Sounds like you're using add-ons for the wrong platform.

iesus wrote:
Also have problem with disk space i added 4pcs of 3tb disks and have only 5,4tb total space(!) after my calcualtions i should have about 8tb my best guess is that it has chosen to have raid 5+1spare but i have not told it to =/.

Were these use disks? If so had they been formatted to use MBR not GPT?

Have you tried a factory default: http://www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu

I am using the latest version of the firmware i belive it was 5,3,2 or something like that
i have tried to use the x86 (i get the error message "wrong architecture") and the sparc ("invalid update image") release but none seems to work.

!Thanks for the link!

Two of the disks were un-used, two were used some (about a month or two), they were ext3 formatted (mbr i guess)
in the "health" section it states the disks are ok and the size seems fine.

If i factory reset i loose my backups (again) =/, but i guess that's the final option

x86 is for x86 NAS units. Sparc is for Sparc units. ARM is for ARM units. You have an ARM unit. DIfferent OS, different firmware, different add-ons.

If you download your logs and extract the zip contents what does your partition.log look like?

Now i get the error message
-
SSH access failed to be enabled due to error 13.

____________________________________________________________________________________________________

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md2 doesn't contain a valid partition table
Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/sda: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 1 4294967295 2147483647+ ee GPT

Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT

Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdc1 1 4294967295 2147483647+ ee GPT

Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdd1 1 4294967295 2147483647+ ee GPT

Disk /dev/md0: 4293 MB, 4293906432 bytes
2 heads, 4 sectors/track, 1048317 cylinders, total 8386536 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/md1: 536 MB, 536858624 bytes
2 heads, 4 sectors/track, 131069 cylinders, total 1048552 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/md2: 5991.5 GB, 5991515553792 bytes
2 heads, 4 sectors/track, 1462772352 cylinders, total 11702178816 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0x00000000


Disk /dev/dm-0: 5980.7 GB, 5980741959680 bytes
255 heads, 63 sectors/track, 727117 cylinders, total 11681136640 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0x00000000

So they are all using GPT. I can only guess that you've had some problems due to using used disks. Would be best to backup your data and try a factory default and see if this fixes it.

mdgm wrote:
So they are all using GPT. I can only guess that you've had some problems due to using used disks. Would be best to backup your data and try a factory default and see if this fixes it.

But two of the disks ( the ones i added first ) was completly new =/
Well well, backing up and starting over...

Any ideas about the ssh package why i cannot add it What is error 13?

That's understandable. However the old disks may not have been able to be wiped properly. Now if the two used disks were formatted using MBR this could be a situation where the NAS treated it as 2x2TB and 2x3TB. Vertical expansion doesn't work when you format with mixed drive capacities on the current firmware.

Regarding SSH, you tried the ARM version? Have you tried rebooting the NAS then reattempting to install the add-on?

k i'll try the backup-restore-defaults option

I did try the linked arm version, and got
"SSH access failed to be enabled due to error 13." sent to my email

Have not yet tried re-trying

Seems to be working better now,
i emtied it (moved files to another disk)

and then it suddenly started to reshape and now it states 8.1tb instead
so that did the trick

And then the ssh was successfully installed as well so it seems fine now.

yoh-dah wrote:
Yes, we'll have future updates that will provide more protocols.

Hi, yoh-dah

5.3.4 released but it seems does not added file protocol..
When will it add?