Problem finding Nas after upgrading to new firmware version

[fvdw]

Ok thats hopeful news.
Lets try to install firmware on sda1, 2 and 7 using fvdw-sl console
When connected with standalone kernel give the command

Code: Select all

fvdw-sl-programs

And choose option write firmware image to disk from the menu that will appear. Do NOT select install firmware option.
The function wil ask you if you want to write to each partition. In your case I advice to write it to sda1 sda2 and sda7.
When finished reboot the nas.

Ps as also nas database was corrupt your shated folders may not be visible if the nas boots. Don't worry they will still be there. We will come to that later

[leone101]

i did it all....just i rewrite firmware for first partition on sda1 sda2 sda7 .....when asked for second i was not sure to write it too....so i jumped....
now the nas is rebooted and is working lot but not as before that was continously redoundant ....
on the assistant now i see also ip of nas 192.168.1.17 but if from assistant i try to "go to web interface" it doesn t enter inside
now what is next step?
should i also rewrite on second partition also firmware or is just normal to have for first one i already did?

[fvdw]

If I understand you correctly, you have written firmware to sda1 and sda7.
If that is the case then it is ok as nas now boots from sda7.
As the nas has now an ip address try to connect with ssh client ( putty) using that ip address. I assume you have done that in the past. Username is root and password is giveit2me.
When connected give command cat boot.log
So in this case do not use standalone kernel but boot nas normally and connect with ssh client.

[leone101]

yesterday i unplugged nas and pc because of really bad weather and today i tried to use assistant to check ip......and i also tried to use putty....
it seems again there is old problem with HD working in redondande way led light is blue but not blink.
i tried to redo the same install operation you asked me with standalone kernel before on partition....but when i try to make it again it says :
Mounting sda5 failed
Can not temporary store firmware images,
The script will exit.
Installation incomplete

i think because in that sda5 it stores temporanely firmware files that after have to be installed on sda1....sda2....and sda7 and could be it full and this is why it can't go over and retry install operations like yesterday??

[fvdw]

Thats not good, how did you shut down the nas?
Apparently you tried again to write firmware image to disk.
And it failed because sda5 could not be mounted
If sda5 could not be mounted after shutdown I think we are facing here a failing harddisk. We need to start again to see if something can be saved
Load the standalone kernel an try to repair filesystem on sda5

Code: Select all

e2fsck -fy /dev/sda5

Of course first download the mini glibc and tools files using fvdw-sl- programs
If repair succeeds try to mount /dev/sda5 on /sda5 and check content of /sda5/etc using ls command

[leone101]

i switched it off just a night.....plugging it off because it has not any power button.
this is result of what u asked me

root@fvdw-sta-kirkwood:/ # e2fsck -fy /dev/sda5
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda5: recovering journal
Error reading block 66163 (Attempt to read block from filesystem resulted in short read). Ignore error? yes

Force rewrite? yes

Clearing orphaned inode 32816 (uid=0, gid=0, mode=0100666, size=0)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Unconnected directory inode 32836 (/tmp/var/log/???)
Connect to /lost+found? yes

Unconnected directory inode 32838 (/tmp/var/spool/???)
Connect to /lost+found? yes

Unconnected directory inode 32839 (/tmp/var/spool/???)
Connect to /lost+found? yes

Pass 4: Checking reference counts
Inode 32783 ref count is 4, should be 5. Fix? yes

Inode 32794 ref count is 2, should be 4. Fix? yes

Unattached inode 32833
Connect to /lost+found? yes

Inode 32833 ref count is 2, should be 1. Fix? yes

Unattached inode 32834
Connect to /lost+found? yes

Inode 32834 ref count is 2, should be 1. Fix? yes

Unattached inode 32835
Connect to /lost+found? yes

Inode 32835 ref count is 2, should be 1. Fix? yes

Inode 32836 ref count is 3, should be 2. Fix? yes

Inode 32838 ref count is 3, should be 2. Fix? yes

Inode 32839 ref count is 3, should be 2. Fix? yes

Unattached inode 32840
Connect to /lost+found? yes

Inode 32840 ref count is 2, should be 1. Fix? yes

Unattached inode 32841
Connect to /lost+found? yes

Inode 32841 ref count is 2, should be 1. Fix? yes

Pass 5: Checking group summary information
Block bitmap differences: +(43578--43580) +(43583--43589) +(131592--131593) +132141
Fix? yes

Free blocks count wrong for group #1 (32181, counted=32171).
Fix? yes

Free blocks count wrong for group #4 (32218, counted=32215).
Fix? yes

Free blocks count wrong (189071, counted=189058).
Fix? yes

Inode bitmap differences: +(32833--32841)
Fix? yes

Free inodes count wrong for group #4 (8136, counted=8127).
Fix? yes

Directories count wrong for group #4 (29, counted=32).
Fix? yes

Free inodes count wrong (49052, counted=49043).
Fix? yes


/dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda5: 109/49152 files (0.0% non-contiguous), 7550/196608 blocks
root@fvdw-sta-kirkwood:/ # mkdir /sda5
root@fvdw-sta-kirkwood:/ # mount /dev/sda5 /sda5
root@fvdw-sta-kirkwood:/ # cd /sda5
root@fvdw-sta-kirkwood:/sda5 # ls
etc lost+found tmp var
installer.log nas_conf_db_ok.xml usr writer.log
root@fvdw-sta-kirkwood:/

directories are present

[fvdw]

Reboot the nas

[leone101]

i did it

[fvdw]

And what is the result?

[leone101]

As before....redounding working of hd....could i try to redo process on sda1 sda2 and sda7 letting program free space on sda5 and including in procedure this time also the second partition of the hd that i didn't included the first time i tried installation of firmware?