BlackArmor NAS Network Storage Server

[Solrac]

Got my new flaming Debian installed    everything seems to be running just fine but..

I just messed up the raid devices... and im a bit confused as well, I want to ask a few questions b4 I go to the datacenter were I keep this NAS :

This linux is installed on my Raid 10 or is it outside of it?

It should be possible for me to just drop the raid and re-build a new one?

Should I wipe the disks out of the box and start all over again?  *sigh*

Any hit will be really usefull ^^

Thanks in advance

[Solrac]

I managed to recover the Raid (lacking of 1 hard disk)  and im still not able to set up folder permisions from windows to each directory, everytime will tell me that I have no right to do it, even if the folders are on 777, samba writeable share, etc. etc...

I have a couple of Cent-OS serving files, the permisions on each folder there are working perfectly fine...  so my actual question will be:

- In order to reinstall the OS is really needed to go back to stock OS first?

- Should Debian be difrent from Cent-OS while both using Samba / Krb / Winbind ?

Tnx ^^

[Torpedo]

Thanks for your work Hajo, your installation worked perfectly on my NAS 220.

Is it me or the performance on this NAS is incredibly rubbish? 

I'm getting 3,56 MB/s write speeds.

[Isaac_X]

The results aren't stellar

Version 1.03d       ------Sequential Output------ --Sequential Input- --Random-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
Xanadu         500M  2540  92 58001  59 25817  40  2553  94 63608  54 470.9   5
                    ------Sequential Create------ --------Random Create--------
                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
                 16 12120  98 +++++ +++ 17402  90 12349  97 +++++ +++ 19533 100


Looks like on RAID10 it's capable of 58MB/s block writes and 63MB/s block reads. However, over a Gigabit network, it has a disappointing price/performance ratio with 27MB/s reads and writes on RAID 10.

Too slow and expensive to recommend, although Hajo's Debian installation makes it much more pleasant to use.

[Solrac]

/agreed... I finally managed to get my NAS box working, couldnt fix ACL troubles on debian so im doing everything from the inside of the box...

I had to re-make the raid 10 array and make a new partition as well, somehow the 4th partition was giving me troubles so I started from scratch, everything is beautifully working ^^

22 MB/sec average write speed over a GB network consuming from 30 to 60% of the CPU.... 9GB transfered. I wonder the performance and cpu usage when 10 - 20 ppl writes at the same time...

I think i'll check that next monday...

[see_dog]

Hello,

Thank you for this hack very easy to use. But I'm having an issue with the datavolume partition.

I have an /dev/md4 array created with /dev/sda4 and /dev/sdb4 as such : 

debian-armel:~# cat /proc/mdstat | grep md4
md4 : active raid0 sdb4[1] sda4[0]
      3901415808 blocks 64k chunks

But I can't mount it on my system... The error I get is 

debian-armel:~# mount /dev/md4 /mnt/datavolume/
mount: you must specify the filesystem type

 And I can't find the filesystem type of this array (I tried ext2/3 vfat ntfs) which I find very strange and disappointing.

Could anyone who got the datavolume partition to work please help me ?

Thank you.

[see_dog]

In addition to my previous post here is the result of fdisk -l in case it's useful : 

debian-armel:~# fdisk -l

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


Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x07751000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1      243202  1953514583+  ee  EFI GPT

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


Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x07751000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1      243202  1953514583+  ee  EFI GPT

Disk /dev/md0: 1068 MB, 1068892160 bytes
2 heads, 4 sectors/track, 260960 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table

Disk /dev/md4: 3995.0 GB, 3995049787392 bytes
2 heads, 4 sectors/track, 975353952 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md4 doesn't contain a valid partition table

Disk /dev/md2: 533 MB, 533921792 bytes
2 heads, 4 sectors/track, 130352 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md2 doesn't contain a valid partition table

Disk /dev/md1: 1069 MB, 1069875200 bytes
2 heads, 4 sectors/track, 261200 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md1 doesn't contain a valid partition table

[riha]

---

see_dog wrote:

Hello,

Thank you for this hack very easy to use. But I'm having an issue with the datavolume partition.

I have an /dev/md4 array created with /dev/sda4 and /dev/sdb4 as such : 

debian-armel:~# cat /proc/mdstat | grep md4
md4 : active raid0 sdb4[1] sda4[0]
      3901415808 blocks 64k chunks

But I can't mount it on my system... The error I get is 

debian-armel:~# mount /dev/md4 /mnt/datavolume/
mount: you must specify the filesystem type

 And I can't find the filesystem type of this array (I tried ext2/3 vfat ntfs) which I find very strange and disappointing.

Could anyone who got the datavolume partition to work please help me ?

Thank you.

---

Have you formatted /dev/md4, like so?

mkfs.ext3 /dev/md4

 Of course, data on that partition will be lost when formatting.

After that, mounting should work.

mount -t ext3 /dev/md4 /mnt/datavolume

[see_dog]

Thank you, I skipped that step for fear of losing datas, but my server is new, so I don't have anything to lose, it's working great now, thank you for the tip.

And thanks again to Hajo for the hack !

[roband915]

Hello

I've installed debian on my blackarmor 220 but then all of a sudden  my root partition got full and also one disk failed(Raid 1). So I thought I resize my root and see if it helps. But I can't figure out how! I've connected one disc to a linux computer but the resizing doesn't bite. Can somebody help me figure this one out?