Nas Died

Re: Nas Died

Postby Jocko » Wed Mar 08, 2017 2:21 pm

Yes it is the right file
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Nas Died

Postby poilopil » Thu Mar 09, 2017 7:56 am

so i choose the file and now its showing in console: waiting for u-boot.
also the asistant exe cant find any nas.
But i can ping the NAS and it gives a response.
What 2 do next ?
poilopil
 
Posts: 25
Joined: Wed Feb 01, 2017 2:22 pm

Re: Nas Died

Postby fvdw » Thu Mar 09, 2017 8:15 am

poilopil wrote:so i choose the file and now its showing in console: waiting for u-boot.
also the asistant exe cant find any nas.
But i can ping the NAS and it gives a response.
What 2 do next ?

:disapprove
You should have switched off your nas before launching the standalone kernel and only switch it on when you have the window "waiting for uboot".

It is all written in the help files that come with the console and displayed in the main window of the fvdw-sl console. We are willing to help you but really you should do some more effort and careful reading of the instructions ;)
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Nas Died

Postby Jocko » Thu Mar 09, 2017 8:42 am

Jocko wrote:Hi poilopil,

The first thing to do before removing a disk or anything else is to detect the current raid state.

So first download the fvdw-sl console (viewtopic.php?f=7&t=2691). Please read fully the topic (and even twice time).
I confirm fvdw's post.
Whereas I gave this information at the beginning of the topic, you quickly posted the asking
poilopil wrote:OK how do i connect my NAS to my pc ? or put in network ?
Which shows you did not read instructions!
You are not a child so make a little effort
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Nas Died

Postby poilopil » Thu Mar 09, 2017 10:13 am

yes it works :) sorry for my not reading actions but i am not that good with pc's and stuff.
im getting the gpt partition table question now.
I see my 5big doesnt support it so i choose NO ? right?
it has disks from 1tb so 5 x 1tb
poilopil
 
Posts: 25
Joined: Wed Feb 01, 2017 2:22 pm

Re: Nas Died

Postby Jocko » Thu Mar 09, 2017 10:47 am

With 1Tb disks there is no need to use a gpt partition table (and also 5big1 does not support it on sda disk)

So choose No
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Nas Died

Postby poilopil » Thu Mar 09, 2017 11:17 am

so it wasnt succesfull here is the log:

logical (5 or over)
p primary partition (1-4)
Invalid partition number for type 'e'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type '2'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type '1'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type 'n'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type '2'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type '3'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type 'n'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type '3'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type '3'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type 'n'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type '3'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type '4'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type 'n'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type '4'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type '1'
Command action
l logical (5 or over)
p primary partition (1-4)
Invalid partition number for type 'w'
Command action
l logical (5 or over)
p primary partition (1-4)
creating ms-dos partiton table succeeded
format partition 5
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
32128 inodes, 128456 blocks
1284 blocks (1.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67371008
16 block groups
8192 blocks per group, 8192 fragments per group
2008 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729

Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 25 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
formatting sda5 succeeded
writing kernel to partition 6
mounting sda 5 succeeded
getting kernel from tftp server
writing kernel to partition 6
3996+1 records in
3996+1 records out
2046104 bytes (2.0MB) copied, 0.629709 seconds, 3.1MB/s
writing kernel to partition 6 succeeded
Getting firmware image from tftp server
firmware disk image uploaded succesfully\n
Unpacking firmware image from archive
firmware disk image extracted succesfully\n
Adapting firmware image for 5big1\n
Transfer of firmware correction from tfp server succeeded, starting pacthing of firmware image
mounting firmware image succeeded
./
./etc/
tar: can't make dir ./etc: Input/output error
./etc/init.d/
tar: can't create directory './etc': Input/output error
tar: can't make dir ./etc/init.d: Input/output error
./etc/init.d/insert-modules
tar: can't create directory './etc/': Input/output error
tar: can't remove old file ./etc/: Input/output error
correcting firmware image for 5big1 failed


what now ?
poilopil
 
Posts: 25
Joined: Wed Feb 01, 2017 2:22 pm

Re: Nas Died

Postby Jocko » Thu Mar 09, 2017 11:43 am

That means install script failed to delete fully the original partition table.

So if you still have a telnet window opened, do these commands to remove manually the table before installing again version 16.1:
- load gdisk binary
Code: Select all
busybox tftp -r gdisk -l /sbin/gdisk -g ip-pc
   chmod 755 /sbin/gdisk
(ip-pc is your laptop ip)
- run gdisk /dev/sda

Then on the gdisk menu, do : x+enter; z+enter confirm by typing y+enter (twice : to delete any table)
Check if you have no longer partition : gdisk -l /dev/sda

If yes you can again try to install fvdw-sl. If you do not have restarted the NAS install is still available. So on the telnet window do
Code: Select all
 /fvdw-sl-installer ip-pc
(ip-pc is your laptop ip)

Otherwise, you need to stop the NAS and run again the install process from the beginning
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Nas Died

Postby poilopil » Thu Mar 09, 2017 12:13 pm

i put into the telnet client

busybox tftp -r gdisk -l /sbin/gdisk -g 192.168.10.22 chmod 755 /sbin/gdisk

but just get the below result:
usage: tftp options host
transfer a file from/to tftp server
-1file local file
etc

think the command syntax isnt right?
poilopil
 
Posts: 25
Joined: Wed Feb 01, 2017 2:22 pm

Re: Nas Died

Postby poilopil » Thu Mar 09, 2017 12:16 pm

i copied paste now from the site into telnet window
now i get :

invalid option --1
poilopil
 
Posts: 25
Joined: Wed Feb 01, 2017 2:22 pm

PreviousNext

Return to Lacie 5Big Network vs1

Who is online

Users browsing this forum: No registered users and 2 guests

cron