BlackArmor NAS Network Storage Server

[tubeswed]

Hi,

My BA 110 NAS do not connect to the network anymore on boot. Installed Debian more than a year ago but have not used it for some months.

Erasing the hard drive and putting it in again will that solve the problem or will I after that still have have the custom firmware installed?

Is there a way to restore it to factory default?

Thanks in advanced!

[turbo3]

Hi tubeswed,

if you didn't use your NAS for some months, it is possible, that the router had given a new ip to the NAS.

Please scan for new net devices.

For factory default (Seagate) have a look at the beginning of this forum.

Remove disk, delete disktable, insert disk and start will reinstall the Seagate firmware.

regards,

turbo3

[jcentel]

@turbo3, to me it's the same.

I have a 3 Tb BA 110.

debian-armel:/media# parted /dev/sda print
Model: Seagate ST33000651AS (scsi)
Disk /dev/sda: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Flags
 1      100MB   1169MB  1069MB  ext3                  raid 
 2      1169MB  2239MB  1070MB  linux-swap            raid 
 3      2239MB  2773MB  534MB   ext3                  raid 
 4      2773MB  3000GB  2998GB               primary  raid

¿What does this error messages means?

Error: /dev/mtdblock6: unrecognised disk label                            
Error: /dev/mtdblock5: unrecognised disk label                            
Error: /dev/mtdblock4: unrecognised disk label                            
Error: /dev/mtdblock3: unrecognised disk label                            
Error: /dev/mtdblock2: unrecognised disk label                            
Error: /dev/mtdblock1: unrecognised disk label                            
Error: /dev/mtdblock0: unrecognised disk label

¿Is it harmfulless to format /dev/sd4 and add an /etc/fstab entry?

mkfs.ext3 /dev/sda4 

[mittim]

Hi All

Thanks Hajo for this process, it worked well, and I've gotten Lenny installed with webmin on my NAS110

I ran into one issue though, which was that /dev/md3 was not available.   I've solved this, and want to post my experience in case anyone else has trouble with this,  its odd that I'm the first to note this (or maybe i missed it, i scannedthe previous 22 pages though)

I checked dmesg and found that md complained of an invalid magic number on the sb for md3.  

md: Autodetecting RAID arrays.
md: invalid raid superblock magic on sda4
md: sda4 has invalid sb, not importing!

I was able to cleanly assemble the array (odd that they have a raid array for a single disk anyways) with the following command: 

mdadm --assemble /dev/md3 /dev/sda4 

And that allowed me to mount /dev/md3 correctly and my data seems intact. 

However, still after reboot md3 wasn't detected automatically.  

So, I read a little on mdadm and ran the following: 

mdadm -Esc partition >> /etc/mdadm/mdadm.conf

This defines the md devices into the conf file,  since only md3 was the troubled one, I commented out md0 through md2

So my mdadm.conf looks like this: 

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays

# This file was auto-generated on Sat, 18 Dec 2010 10:26:52 +0100
# by mkconf $Id$
#ARRAY /dev/md0 level=raid1 num-devices=2 UUID=398d577c:d879ff48:e32581ad:8faca043
#ARRAY /dev/md1 level=raid1 num-devices=2 UUID=dd79a665:534af6d7:1ea45cb1:9769f445
#ARRAY /dev/md2 level=raid1 num-devices=2 UUID=8ddaeb17:c8352b32:d44150cb:4fa09cb0
ARRAY /dev/md/3 level=raid1 metadata=1.2 num-devices=2 UUID=f7cb3873:3a0745b8:64d282c1:672863c0 name=3

Since then /dev/md3 is available, and I then setup /etc/fstab to mount.  

Maybe I was taking the wrong approach,  if anyone else knows of something I'm doing wrong, please let me know. 

-Tim

[bims]

Hi Hajo,

The new firmware released by Seagate for NAS devices, comes with tappin configured, which is better way of sharing content on internet. Tappin also has smartphone apps and seamless integration to PC/Mac/Linux. I haven't tried, but I wanted to ask if it is possible to include that service somehow in the firmware released by you? Or if there is a simple way of installing tappin to the NAS drive running on lenny?

- Bimal

[Olivier]

I think the firmware given in first page is not a full firmware, it is just a patch to allow to reset ssh password and so allow to modify the system later.

Olivier

[Juzz]

Luctrev: How did you get around the udev requirement of a newer kernel when you updated to squeeze?

[Raniere]

Hello all and SuperSmash,

I follow the steps to install Debian and it work fine for more than a month.

Yesterday, when I turn on the NAS it was dead (the system light is blink blue and the hdd one is solid blue).

I can't connect with the NAS with ssh neither telnet. When I ping the nas I get "Destination Host Unreachable".

Can any one help?

[biggray]

Same thing, can someone help with this? Do you resolve your problem?

[Raniere]

Biggray,

did you see http://forums.seagate.com/t5/BlackArmor-NAS-Network-Storage/BA-110-and-Debian-not-booting/m-p/143813...

You can use a serial cable to interfere with the boot process. Once I don't know how to do that, I open the box following http://crapnas.blogspot.com.br/2010/04/opening-box.html, retrieve the HDD, connect the HDD in the pc of a friend and backup some files.
Now, I following http://nickolaszev.blogspot.com.br/2012/01/delete-everything-in-disk-even-gpt.html to format the HDD and latter I will test if NAS back to work. As soon as I get any news I will post a update.

Update:

Format the HDD work fine and the NAS return to original interface.