Unbrick a Bricked Lacie Network Space 2

kouyio
Posts: 7
Joined: Sun Jul 31, 2011 9:32 am

Re: Unbrick a Bricked Lacie Network Space 2

Post by kouyio » Tue Jul 17, 2012 10:17 pm

pispo wrote:I want to know in which version of linux this process has been tested (plz livecds) and what are the concrete commands.
I think I used an Ubuntu Desktop distro. At the time it was the 8.04 I think.

You can grab it here: http://mirror.anl.gov/pub/ubuntu-iso/DV ... 4/release/

Good luck!

pispo
Posts: 2
Joined: Fri Jun 03, 2011 6:14 pm

Re: Unbrick a Bricked Lacie Network Space 2

Post by pispo » Wed Jul 18, 2012 11:22 am

I want to know if someone knows how to convert an hd "logical_block_size" from 4096 to 512. I two Seagate ST2000DL001 (twins). Linux reports that /sys/block/sbX/queue/logical_block_zise is 512 and the other 4096. I searched on Internet and there are people that used Window's diskpart and GPT to force the logical block size. I tried it but without success.

I need to change the blocksize becase I think that is the problem restoring the NS2.

kouyio
Posts: 7
Joined: Sun Jul 31, 2011 9:32 am

Re: Unbrick a Bricked Lacie Network Space 2

Post by kouyio » Wed Jul 18, 2012 11:41 am

You may want to try something like this:

Code: Select all

fdisk -b sectorsize
Check the fdisk manual here: http://linux.die.net/man/8/fdisk

dies3l
Posts: 5
Joined: Thu May 05, 2011 11:10 pm

Re: Unbrick a Bricked Lacie Network Space 2

Post by dies3l » Sun Jul 29, 2012 12:23 am

Glad to see other people playing with this device! :)

I had some trouble months ago and now I decided to solve it, reinstalling all partitions.

I tried the script proposed by kouyio, but I can't create the correct partition table, I think cause to different unit (sector against cylinders).
I tried also to create the partitions manually following http://downloads.lacie.nas-central.org/ ... ntable.txt but no lucky in that.

Here is my log (take a look at the printed partition table):

Code: Select all

Installing mbr
--------------
1+0 record dentro
1+0 record fuori
512 byte (512 B) copiati, 0,0621207 s, 8,2 kB/s
 -> DONE
Formatting HD (1/2)
-------------------
 -> DONE
Formatting HD (2/2)
-------------------
 -> DONE
HD formatted!
-------------

Comando (m per richiamare la guida): 
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 testine, 63 settori/tracce, 121601 cilindri, totale 1953525168 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificativo disco: 0x9b7e53f1

Dispositivo Boot      Start         End      Blocks   Id  System
/dev/sdb1              63     4016249     2008093+   5  Esteso
/dev/sdb2         4016250  1953525167   974754459   83  Linux
/dev/sdb5            2111     4016249     2007069+  83  Linux

Comando (m per richiamare la guida): 
Installing partition images
---------------------------
16002+0 record dentro
16002+0 record fuori
8193024 byte (8,2 MB) copiati, 0,108045 s, 75,8 MB/s
16002+0 record dentro
16002+0 record fuori
8193024 byte (8,2 MB) copiati, 0,144963 s, 56,5 MB/s
1702827+0 record dentro
1702827+0 record fuori
871847424 byte (872 MB) copiati, 9,38674 s, 92,9 MB/s
1751022+0 record dentro
1751022+0 record fuori
896523264 byte (897 MB) copiati, 6,8022 s, 132 MB/s
16002+0 record dentro
16002+0 record fuori
8193024 byte (8,2 MB) copiati, 0,0689146 s, 119 MB/s
 -> DONE
Make swap partition
-------------------
Setting up swapspace version 1, size = 2007064 KiB
nessuna etichetta, UUID=4915e0b6-f056-4347-bcbb-e5e592a18463
 -> DONE
Format partition 2
------------------
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze       
Lettura informazioni sullo stato... Fatto
xfsprogs è già alla versione più recente.
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
mkfs.xfs: /dev/sdb2 appears to contain an existing filesystem (xfs).
mkfs.xfs: Use the -f option to force overwrite.
 -> DONE
what I'm doing wrong?

Mijzelf
Posts: 6251
Joined: Mon Jun 16, 2008 10:45 am

Re: Unbrick a Bricked Lacie Network Space 2

Post by Mijzelf » Sun Jul 29, 2012 12:52 pm

Code: Select all

Dispositivo Boot      Start         End      Blocks   Id  System
/dev/sdb1              63     4016249     2008093+   5  Esteso
/dev/sdb2         4016250  1953525167   974754459   83  Linux
/dev/sdb5            2111     4016249     2007069+  83  Linux
Apparently something went wrong when creating logical partition sdb5 in extended partition sdb1. It should have been about 256MB, when I remember well, but now it's 2TB, leaving no room for the partitions 6,7,8,9 and 10.

I suppose fdisk has done something unexpected. You can remove the >/dev/null in the script:

Code: Select all

echo "Formatting HD (2/2)"
echo "-------------------"
fdisk $1 >/dev/null <<EOF
and re-run the script. Possibly the output will tell what went wrong.

Starget
Posts: 5
Joined: Fri Dec 07, 2012 9:34 pm

Re: Unbrick a Bricked Lacie Network Space 2

Post by Starget » Sun Dec 09, 2012 5:13 pm

Hello Mijzelf

Its fair to three days following that on the box and I do not understand, not created partitions Sdx 6 7 8 9 10
I do not understand exactly where the problem and I have the same errors that are hard but dies3l WD 1TB

Please Help.

Mijzelf
Posts: 6251
Joined: Mon Jun 16, 2008 10:45 am

Re: Unbrick a Bricked Lacie Network Space 2

Post by Mijzelf » Tue Dec 11, 2012 9:05 am

@Starget: I must admit that I don't understand what you're saying/asking.

Starget
Posts: 5
Joined: Fri Dec 07, 2012 9:34 pm

Re: Unbrick a Bricked Lacie Network Space 2

Post by Starget » Thu Dec 13, 2012 5:49 pm

When I launch that command line, the partition 6,7,8,9,10 dont get created properly, ad I don't know why, could you help?

Mijzelf
Posts: 6251
Joined: Mon Jun 16, 2008 10:45 am

Re: Unbrick a Bricked Lacie Network Space 2

Post by Mijzelf » Fri Dec 14, 2012 11:29 am

You mean, the same problem as dies3l rapports? Have you tried my suggestion I answered him? If yes, what was the output?

Starget
Posts: 5
Joined: Fri Dec 07, 2012 9:34 pm

Re: Unbrick a Bricked Lacie Network Space 2

Post by Starget » Sat Dec 15, 2012 9:38 pm

Hello Mijzelf

Thank you for reply, I managed to create all partitions with unbutu 8.4: p

my box and network space max: p

The box flashes blue every 1 second I do not know what fair: x

Thank you for your help.

Stan

Mijzelf
Posts: 6251
Joined: Mon Jun 16, 2008 10:45 am

Re: Unbrick a Bricked Lacie Network Space 2

Post by Mijzelf » Sun Dec 16, 2012 12:36 pm


Starget
Posts: 5
Joined: Fri Dec 07, 2012 9:34 pm

Re: Unbrick a Bricked Lacie Network Space 2

Post by Starget » Sun Dec 16, 2012 1:46 pm

Hello I followed the instructions but it does not work like ):

My Box Lacie Network Space Max.

sovtis
Posts: 5
Joined: Sun Mar 17, 2013 4:08 pm

Re: Unbrick a Bricked Lacie Network Space 2

Post by sovtis » Sun Mar 17, 2013 4:26 pm

Hi!
I have been trying to put 2 TB Seagate drive to NS2 instead of 1 TB working disk. I managed to get so far that NAS is seen as 192.168.0.22 and initial web screen is available with FW 1.2.93. Alas same situation as kouiyo earlear there is 0 MB space left assuming the sda2 formatting is not compatible with NAS. So next step is to enable ssh in NAS to get remote access to NAS and format with it's own formatting command. I created id_rsa keys and copied it to sda8 /root/.ssh/authorized_keys and tried to connect via mac and ubuntu but always I get Permission denied. I quess ssd is enabled since its asking password. Tried with 6 char password and without passworn, just empty and various methos in ssh calls but always same. Any ideas? I used -vvv option to debug ssh but I do not known much about ssh and mechanisms under that. Maybe someone spots the error? There should be valid public key indo in .ssh/authorized_keys and ssh is enabled in NAS. Why ssh is not accepting password so that I could try formatting in NAS and use double size of new 2TB disk.

Feeling desperate since whole weekend has gone in this - well it's been educational also.

buntu@ubuntu:~$ ssh -vvv -i /media/OV/id_rsa.pub 192.168.0.22
OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.0.22 [192.168.0.22] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/media/OV/id_rsa.pub" as a RSA1 public key
debug1: identity file /media/OV/id_rsa.pub type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /media/OV/id_rsa.pub-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1
debug1: match: OpenSSH_5.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
debug2: fd 3 setting O_NONBLOCK
debug3: load_hostkeys: loading entries for host "192.168.0.22" from file "/home/ubuntu/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /home/ubuntu/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-dss-cert-v00@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_setup: found hmac-md5
debug1: kex: server->client aes128-ctr hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 135/256
debug2: bits set: 511/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA f7:fc:48:99:5b:95:5d:a8:2f:23:bc:9b:c6:a0:d1:81
debug3: load_hostkeys: loading entries for host "192.168.0.22" from file "/home/ubuntu/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /home/ubuntu/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug1: Host '192.168.0.22' is known and matches the RSA host key.
debug1: Found key in /home/ubuntu/.ssh/known_hosts:1
debug2: bits set: 521/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /media/OV/id_rsa.pub (0x227a0868)
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug3: start over, passed a different list publickey,password,keyboard-interactive
debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /media/OV/id_rsa.pub
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug2: we did not send a packet, disable method
debug3: authmethod_lookup keyboard-interactive
debug3: remaining preferred: password
debug3: authmethod_is_enabled keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug3: userauth_kbdint: disable: no info_req_seen
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred:
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
ubuntu@192.168.0.22's password:
debug3: packet_send2: adding 64 (len 51 padlen 13 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
Permission denied, please try again.
ubuntu@192.168.0.22's password:
debug3: packet_send2: adding 64 (len 57 padlen 7 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
Permission denied, please try again.
ubuntu@192.168.0.22's password:
debug3: packet_send2: adding 64 (len 51 padlen 13 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey,password,keyboard-interactive).

ubuntu@ubuntu:~$ ssh 192.168.0.22
ubuntu@192.168.0.22's password:
Permission denied, please try again.
ubuntu@192.168.0.22's password:
Permission denied, please try again.
ubuntu@192.168.0.22's password:
Permission denied (publickey,password,keyboard-interactive).

sovtis
Posts: 5
Joined: Sun Mar 17, 2013 4:08 pm

Re: Unbrick a Bricked Lacie Network Space 2

Post by sovtis » Mon Mar 18, 2013 9:58 pm

Hi
I think it was that I did not use my private key only public so when I added both public and private to .ssh/authorized_keys I got ssh connection and was able to reformat /sda2 and as instructed and voilá I got 2 TB networkspace2. Now fingers crossed for FW2.2.8 update is now at 49 % so wait and see what happens.

Thanks to all that have added some info about this routine. :D

yes, 100 % success. Well SSH was lost as expected but 2 TB is in use!

Spawn12336
Posts: 1
Joined: Sun Aug 10, 2014 4:09 pm

Re: Unbrick a Bricked Lacie Network Space 2

Post by Spawn12336 » Sun Aug 10, 2014 4:15 pm

OK, I have been at this since last night. After about 6 hours for tinkering, I was finally able to get a new 4TB drive in and partitioned so that the NS2 will boot up. Unfortunately I am now at the point kouyio was at with the drives both showing as 0TB on the slider. I think I have enabled ssh on the drive (edited the files on SDB8 directly, and added a key to the /root/.ssh/aothorized_keys folder), but I am at a complete loss as to how to actually log in to the drive??!? I am on a mac. Please help. My 2TB is full, so I need the new drive.

Thanks

Post Reply