General NAS-Central Forums

Welcome to the NAS community
It is currently Thu Sep 21, 2017 1:31 am

All times are UTC




Post new topic Reply to topic  [ 129 posts ]  Go to page Previous  1 ... 5, 6, 7, 8, 9
Author Message
PostPosted: Mon Aug 17, 2015 11:35 am 
Offline

Joined: Sun Aug 16, 2015 10:12 pm
Posts: 2
fvdw wrote:
this because gmail addresses are by default on the black list (ant spam measure), send an e-mail to admin@plugout.net with the e-mail address you want to use and we can create an exception


I also tried my GMX address but got the same problem. I guess the same reason? Ok I will send an email now.

Thanks.


Top
 Profile  
 
PostPosted: Thu Sep 17, 2015 7:32 am 
Offline

Joined: Thu Apr 04, 2013 7:32 am
Posts: 6
Dear dmiyabara,

I have a problem with my Lacie Cloudbox that seems to be very similar to the one you had.
As it is challenging to read the entire discussion and know what worked and what didn't, could you maybe provide a summary of how you got your Cloudbox working again?

Thanks and best regards,
spinflip.


Top
 Profile  
 
PostPosted: Thu Sep 17, 2015 11:39 pm 
Offline

Joined: Thu Jul 09, 2015 9:33 pm
Posts: 61
Hi spinflip,

you may find the answer to your questions in this link:

http://forum.nas-central.org/viewtopic.php?f=277&t=17409&start=60

Best regards,
dmiyabara


Top
 Profile  
 
PostPosted: Fri Sep 18, 2015 12:20 pm 
Offline

Joined: Thu Apr 04, 2013 7:32 am
Posts: 6
Thank you so much, dmiyabara!

BTW, before you went through this whole procedure with fvdw-sl console, did you try to do a reset to factory settings? (After the repair you found all your data in a folder called "Recovery".) Do you think it's more secure to do the procedure without doing the reset? I'm afraid that the reset might mess up with my data on the drive, and probably it won't work anyway...


Top
 Profile  
 
PostPosted: Fri Sep 18, 2015 2:59 pm 
Offline

Joined: Thu Jul 09, 2015 9:33 pm
Posts: 61
I tried the reset procedure and the first time it worked perfectly. But when my Lacie came to fail for the second time, I did the reset procedure, but it has not worked. For this reason I was looking for a solution and found this forum who helped me and allowed me to restore my Lacie Cloudbox.


Top
 Profile  
 
PostPosted: Sun Sep 20, 2015 10:30 am 
Offline

Joined: Thu Apr 04, 2013 7:32 am
Posts: 6
Hello,

I've connected to my Cloudbox via the fvdw-sl console and got the following information:
Code:
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Warning! Secondary partition table overlaps the last partition by
4294967296 blocks!
Try reducing the partition table size by 17179869184 entries.
(Use the 's' item on the experts' menu.)
Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 48EB39C7-FA39-4315-9B4C-B7E4FE438E83
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1565565838
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048            4095   1024.0 KiB  EF02  grub_core
   2            4096          397311   192.0 MiB   8300  boot_rescue
   3          397312          399359   1024.0 KiB  8300  nv_data
   4          399360         3545087   1.5 GiB     FD00  root_1
   5         3545088         6690815   1.5 GiB     FD00  root_2
   6         6690816         8787967   1024.0 MiB  FD00  var
   7         8787968         9312255   256.0 MiB   FD00  swap
   8         9312256      5860533134   2.7 TiB     FD00  user_data

Unfortunately, I am not at all an expert with partition tables etc. If I understand correctly the number in "last usable sector is 1565565838" is way too low while the end sector of the last partition 8 corresponds well to the 3TB of my drive. Should I just change that number of last usable sector? If yes, how? And is it secure for my data? If the problem lies only in the secondary parition table (which as far as I understand is some kind of backup of the real partition table), maybe the problem is not so severe?

How should I proceed now in order to hopefully get my Cloudbox back working without losing my precious data? It seems that in my case the problem lies in a corrupted partition table, and it's not clear to me that I should I apply the same procedure as dmiyabara... Any hints?


Top
 Profile  
 
PostPosted: Mon Sep 21, 2015 8:02 pm 
Offline

Joined: Thu Apr 04, 2013 7:32 am
Posts: 6
Today I have tried the procedure that has worked for dmiyabara. After the message "Kernel starting", the LED of my Cloudbox was sometimes blinking fast or slowly in blue, but after half an hour or so the LED turned solid red, so no success.

Should I fix the partition table first? How? Any help is welcome...

Update: I restarted my Cloudbox yesterday night and this morning the LED was flashing fast in blue (no red solid light this time), but I was unable to load the Dashboard or connect via LNA...


Top
 Profile  
 
PostPosted: Thu Nov 10, 2016 2:25 am 
Offline

Joined: Thu Jul 09, 2015 9:33 pm
Posts: 61
Hi I'm back and with bad news... my Lacie Cloudbox bricked again... and after a few attempts to repair it, I couldn't bring it back to life, so new year, old bugs...

Tried to use the Uboot and the commands below:

Code:
setenv root_part 5
ide reset
setenv image /boot/uImage
run nexus_load_image
run nexus_bootargs
bootm


But the blue light keep blinking every 2 seconds... and no way to find the Lacie in my network... tried the code
Code:
setenv root_part 3, 4 and 5
. And all goes to the same blue light and after waiting 24 hours, nothing, just blinking every 2 seconds.
Tried the reset operation and after a few seconds, the solid red light.

Used the Kirkwood:
Code:
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 2AF8D378-680C-490D-AAC1-8AA7C45A0B51
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048            4095   1024.0 KiB  EF02  grub_core
   2            4096          397311   192.0 MiB   8300  boot_rescue
   3          397312          399359   1024.0 KiB  8300  nv_data
   4          399360         3545087   1.5 GiB     FD00  root_1
   5         3545088         6690815   1.5 GiB     FD00  root_2
   6         6690816         8787967   1024.0 MiB  FD00  var
   7         8787968         9312255   256.0 MiB   FD00  swap
   8         9312256      3907029134   1.8 TiB     FD00  user_data
root@fvdw-sta-kirkwood:/ #

The gdisk command show very similar numbers when I tried to restore it for the first time.

So what to do next? Anyone have an idea what should I do?

Thanks,
Dalton


Top
 Profile  
 
PostPosted: Thu Nov 10, 2016 2:48 am 
Offline

Joined: Thu Jul 09, 2015 9:33 pm
Posts: 61
While I was waiting for an answer I'm trying this code:

Code:
setenv ipaddr ${ipaddr}
setenv serverip ${serverip}
ide reset
setenv root_part 4
setenv image /boot/uImage
run nexus_load_image
run nexus_bootargs
setenv bootargs ${bootargs} netconsole=6666@${ipaddr}/,6666@${serverip}
bootm


EDIT: After a short night... no good :(


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 129 posts ]  Go to page Previous  1 ... 5, 6, 7, 8, 9

All times are UTC


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group