Fail to get an IP from DHCP server after installing fvdw-sl

[fvdw]

I edited my last post

[Draftmancorp]

I edited my last post

yes.:

Code: Select all

login as: root
root@192.168.0.189's password:
root@Norman_Nas:/ # e2fsck /dev/sek5
e2fsck 1.42.11 (09-Jul-2014)
/dev/sek5 has gone 15294 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sek5: 89/52304 files (2.2% non-contiguous), 7673/208845 blocks
root@Norman_Nas:/ # e2fsck /dev/sek7
e2fsck 1.42.11 (09-Jul-2014)
/dev/sek7 has filesystem last checked time in the future, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sek7: 5705/64000 files (6.9% non-contiguous), 43804/64000 blocks
root@Norman_Nas:/ #


[fvdw]

:crazy aldo ok
So why is this nas not booting. :scratch
What you could remove all disk from old 5big2 and put this disk in slot 1 and see if the old 5big2 boots.
But there eas something with this old nas, I dont remember what was the problem ?

[Draftmancorp]

:crazy aldo ok
So why is this nas not booting. :scratch
What you could remove all disk from old 5big2 and put this disk in slot 1 and see if the old 5big2 boots.
But there eas something with this old nas, I dont remember what was the problem ?

neeh.... i don't know if this work, if you remember my old nas have a HW problem like memory fault or similar, years ago we write firmware somwhere... i don't rember exactly what we did but was a spectacular job :hail :applause

So i think is not a try to do...?

PS.: i remember that we write all partition one at one by hand and installing firmware with putty.
a week of fire :snicker

[fvdw]

Did we use a special kernel? With L2 cache disabled?

[fvdw]

Other idea, maybe the power supply of your new 5big2 is unstable or to low power because of a defect, you could swap the powrr supply and use the one from your old 5big2 to see if that solves it

[Jocko]

Hi

I also thought about that but if the new 5big2 corrupts disks the disk of your old 5big2 might get corrupted.
Lets first again start the standalone kernel and have a look at boot.log on /dev/sda7

Why do not try the opposite case? extract all disks from the old 5big2 and put the new disk
if it is ok that would mean there is somewhere an hardware issue with the new 5big2

[Draftmancorp]

Did we use a special kernel? With L2 cache disabled?

oh man...good question. (i don't understand nothing about this side of informatics)
here some quote from our (your) job:

Code: Select all

- tftp -r fvdw-sl-installer.sh -l fvdw-sl-installer -g 192.168.1.ip del computer.
- chmod 755 fvdw-sl-installer
- /fvdw-sl-installer 192.168.1.ip del pc
- rispondere alle domande: (queste non sono in ordine)
- is a bns2? yes
- unique ID of my device? sda
- is original Lacie firmware? yes
- create a backup (no)
- GPT compatibile (no)
- bigger then 2tb (dipende) ecc
- una volta finito tutto quanto, restera la schermata blu con in centro 100%
- sotto scrivere:
- tftp -r UIMAGE-26394-NWSP2CL-106 -l UIMAGE-26394-NWSP2CL-106 -g 192.168.1.ip del pc
- dd if=UIMAGE-26394-NWSP2CL-106 of=/dev/sda6
- reboot -f

in putty SSH digita l'ip del Lacie.
user: root
password: giveit2me

Partendo da sinistra del Lacie gli slot saranno numerati così
Slot 1 -> sda
Slot 2 -> sdb
Slot 6 -> sdc
Slot 4 -> sdd
Slot 5 -> sde

Qui sotto creiamo ad esempio la partizione per il lacie sul disco Slot 2 (quindi -> sdb)

- gdisk /dev/sdb (per il disco 3 sarà sdc, ecc) (per uscire da gdisk CTRL + C)
- vengono visualizzate le info del disco
- d (per cancellare) se non vede partizioi GPT ma MBR, poi "o" poi yes, e poi "n" e proseguire da giù "nuova partizione"
- 10
- d
- 9
- ecc ecc 8 - 7 - 6 - 5 - 4 - 3 ecc fino a quando non dice NO PARTITION

"nuova partizione":
- n
- 1
- invio
- invio
- invio
- p
- assicurarsi che ci sia solo una partizione.
- w
- yes
- gdisk -l /dev/sdb(sda, sdb,sdc,sdd,sde)
- mke2fs -j -m 1 /dev/sdb1 (sda1, sdb1,sdc1,sdd1,sde1)
- se esce "/dev/sdb1 is mounted; will not make a filesystem here!" digita "umount /dev/sdb1" poi ripeti mke2fs -j -m 1 /dev/sdb1
- vedrai pian piano writing inode tables: XXXX/XXXX (ci vorrà qualche minuto)
- vedrai Writing inode tables: done
- vedrai Creating journal (XXXXX blocks): done
- vedrai Writing superblocks and filesystem accounting information: done (più lento)
- reboot -f
-done

- cp /share/1000/public/nas_conf_db.xml /rw_fs/etc/nas_conf_db.xml

Put the zip archive in the share public and extract it there.
Connect with putty and do following on Linux command line

Code:
- mkdir /sda1 (se dice already exist ok andare avanti)
- mount /dev/sda1 /sda1
- tar -xvf /share/1000/public/fvdw-sl-14-1-5big2-17may2013.tar -C /sda1

when ok, give commands
Code:
- umount /sda1
- touch /lacie-boot/sda1boot
- reboot -f


After that reboot the nas

- rm -f /lacie-boot/sda1boot
- reboot -f

- mettere l'immagine.img nella cartella public
- dd if=/share/1000/public/fvdw-sl-14-1-5big2-17may2013.img of=/dev/sda1
- touch /lacie-boot/sda1boot
- sync
- reboot -f


May you understand something and remember better :evilwink
PS.: many annotation are mine in italian, for help myself that time.

[Draftmancorp]

Hi Why do not try the opposite case? extract all disks from the old 5big2 and put the new disk
if it is ok that would mean there is somewhere an hardware issue with the new 5big2

I can, if you can reassure me that this don't wipe my data :lmao
or modify file in 1st disk with boot stuff. :snicker

[Jocko]

There is no risk with your data as you remove all its disks before putting the new disk