New Lacie Networkspace 2TB with GPT enabled?

[Jocko]

Hi mamboman

I just returned from the weekend and indeed some files should be amended to allow $ and # in the passwords. I think I can send these files in the late evening ...

But it is best before installing them that your share problems are resolved.

[mamboman]

Hi Jocko and fvdw,

love this forum. Very active development.
Please excuse some delay - I am currently transferring my backup media work from my home server to the NAS. I would like to have this process completed before I do the test.

Anyway I do better understand the process now. So the file "nas_conf_db.xml" is some kind of single source? It will be sufficient when I just modify it?
Then once your PHP pages have been updated almost everything should be fine then.

I will try to find out why the creation of shares was stuck on my NAS. I was a bit unclear in my statement in the last post. The "Accept" button on the file share metadata mask did not do anything on my NAS. I will see whether this has changed or some debug output will help diagnosing it.

As I mentioned - to me this is really a big advantage over the old firmware and really great work you guys did! All my respects.

Once I have changed the GUI/PHP files from you, Jocko, I will try to move on to perform administration over the GUI and send my experience.
Please give me 1/2 days until my "robocopy" job has completed :)

Thanks so much!

[mamboman]

One thing that I need to mention - when I started working with the new firmware (before I did something manually in the files), I had started FireFly for iTunes support. And I found out it created shares like "mp3" automatically and successfully. So "under the hood" the system seems to work correctly.
Maybe this is of any help for you guys?

[Jocko]

Hi mamboman,

I just sent you a pm for the password issue

About the other problem, you can use FF with the addon "Firebug", like this, you will be able to trace the request when you make a submit. ;)

[Jocko]

One thing that I need to mention - when I started working with the new firmware (before I did something manually in the files), I had started FireFly for iTunes support. And I found out it created shares like "mp3" automatically and successfully. So "under the hood" the system seems to work correctly.
Maybe this is of any help for you guys?

This confirm my opinion. Maybe there is an issue with your browser (or its settings).

our web interface works well with IE (6 and upper) and FF (3 and upper) but not with opera. In principle, it must work also with chrome (tested in the past but not recently. I don't like Chrome because after installing and removing, there are troubles with the other browsers... :dry )

So that our web interface works, you must enable java and your browser must support AJAX object.

[mamboman]

Hi guys,

@Jocko: thanks for the pm. I received it, installed it - and glad: it works :)
Also I tested setting up shares over the web GUI and checked the system via SSH login afterwards to see what happened in the system - everything seems to work correctly. Don't know what it was. Now it says something like "saving..." in the status bar of the GUI whenever I say "accept". This did not happen at all at the first boot of the system.

So: perfect! ;)

My wishlist has come down to:
- Support more special characters including umlauts in passwords
- Allow blanks in description fields (why not?)
- Update to a newer version of Samba - but currently I can perfectly work with the given setup.

Thanks a lot!

[fvdw]

....
Also I tested setting up shares over the web GUI and checked the system via SSH login afterwards to see what happened in the system - everything seems to work correctly. Don't know what it was. Now it says something like "saving..." in the status bar of the GUI whenever I say "accept". This did not happen at all at the first boot of the system.

:tapfoot did you clear the caches of your browser after upgrading to 12-1 as mentioned in the help text...

but good to read that you solved all the issues. Normally installtion should be smoother

[Jocko]

Yes, Fvdw.

The object share is not identical between the versions 11.0 and 12.1 : has new properties (hide/show technical shares). So if the browser cache is not emptied, as the previous menus (htm/js) can not handle them, a fatal error occurs when you edit or create a share.

After this fatal error, you can no more submit requests (hanged menu).

[mamboman]

Could have happened. What I did was starting with 11.1, immediately updating to 12. I have "Delete temporary files" set in my IE, but it could be I did not exit IE between the two sessions...
Whatever. it works.

One last question: when I get it right with the new GPT layout I could even install a disk >> 2.2 TB. What would I have to save and copy from the current disk to a fresh new empty disk then to get a clean new up and running NAS?
I would assume just copy the bootsector from the current disk by doing this:

Old disk installed:
dd if=/dev/sda of=/path-to-a-backup-disk/mbr.img bs=512 count=1

And on the new disk then
dd if=/path-to-a-backup-disk/mbr.img of=/dev/sda bs=512 count=1
or
dd if=/path-to-a-backup-disk/mbr.img of=/dev/sda bs=446 count=1 (if the new disk has another partition table that needs to be preserved)

and the rest like desribed in your manual (like seeing up partitions, writing the images, etc.). It this correct?

I would like to make a backup of my system in case of a disk problem. /dev/sda8 of course will be backed up differently :)

[fvdw]

One last question: when I get it right with the new GPT layout I could even install a disk >> 2.2 TB. What would I have to save and copy from the current disk to a fresh new empty disk then to get a clean new up and running NAS?
I would assume just copy the bootsector from the current disk by doing this:

Old disk installed:
dd if=/dev/sda of=/path-to-a-backup-disk/mbr.img bs=512 count=1

And on the new disk then
dd if=/path-to-a-backup-disk/mbr.img of=/dev/sda bs=512 count=1
or
dd if=/path-to-a-backup-disk/mbr.img of=/dev/sda bs=446 count=1 (if the new disk has another partition table that needs to be preserved)

and the rest like desribed in your manual (like seeing up partitions, writing the images, etc.). It this correct?

I would like to make a backup of my system in case of a disk problem. /dev/sda8 of course will be backed up differently :)

I don't think that the procedure you describe is the right way to do it.
If the new disk is bigger it will have more sectors. And just copying the mbr will not work. In fact gpt partioned disks doesn't use the mbr it puts there something to protect older system form accessing the disk in the wrong way.
For disk bigger the 2.2TB only GPT can be used to make use of all space. If you use ms-dos partions then the max will be that you can use of the disk 2.2 TB

In fact the bootloader only tries to find partition 6 to load the kernel and pass some arguments to it. When it is a GPT formatted disk the loader will not use the MBR as far as I know (but I could be wrong)

I would just create the 8 partitions with gparted as you did with this one and using for sda8 the remaining size of the disk.
And the do the rest just as described in our manual
To preserve the settings you made you could copy the data base file as present in /rw_fs/etc (this is on sda5) on the current diks and write that to new disk sda5 partition instead of the one in the first time install package