Networkspace 2 not working - understand what fvdw-sl can do

[Jocko]

:pound
for today it is enough and time to go to bed on my side :z)

Tomorrow you will need a memory stick ~1GB (we go to format it)

[schlum]

got the memory-stick ready.

in which filesystem shall I format it ?

then I will restart the whole process and once connected I assume I will have to identify the stick and then use it as swap. I assume I will have to plug the stick in the NAS box, not in my PC right ?

[Jocko]

Hi Schlum,

You may follow this howto viewtopic.php?f=26&t=2247&hilit=xfs_repair&start=20#p19210.

Do a hot-plug with you memory stick, then do first

Code: Select all

udevstart

and you should see a sdb line in

Code: Select all

cat /proc/partitions

So replace any 'sej' by 'sdb' in the howto

[schlum]

Thanks Jocko.

I did that, and run xfs_repair.
cursor blinked for probably a minute and then error message:

Code: Select all

root@fvdw-sta-kirkwood:/ # cat /proc/partitions
major minor  #blocks  name

  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0 1953514584 sda
   8        1          1 sda1
   8        2 1951503907 sda2
   8        5     256977 sda5
   8        6       8001 sda6
   8        7       8001 sda7
   8        8     851413 sda8
   8        9     875511 sda9
   8       10       8001 sda10
   8       16    1984512 sdb
   8       17    1983488 sdb1
root@fvdw-sta-kirkwood:/ # swapon /dev/sdb1
swapon: /dev/sdb1: Invalid argument
root@fvdw-sta-kirkwood:/ # swapon /dev/sdb
swapon: /dev/sdb: Invalid argument
root@fvdw-sta-kirkwood:/ # mkswap /dev/sdb1
Setting up swapspace version 1, size = 2031087616 bytes
UUID=fc3cbdd8-b769-4670-a270-d9a3ec081413
root@fvdw-sta-kirkwood:/ # swapon /dev/sdb1
root@fvdw-sta-kirkwood:/ # tftp -l  glibc-mini-mkfs.xfs-25feb14.tar -r  glibc-mini-mkfs.xfs-25feb14.tar -g 192.16
8.1.109
glibc-mini-mkfs.xfs- 100% |****************************************************************|  2519k  0:00:00 ETA
root@fvdw-sta-kirkwood:/ # tftp -l xfs_repair -r xfs_repair -g 192.168.1.109
xfs_repair           100% |****************************************************************|   622k  0:00:00 ETA
root@fvdw-sta-kirkwood:/ # chmod 755 /xfs_repair
root@fvdw-sta-kirkwood:/ # /xfs_repair -n /dev/sda2
/xfs_repair: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
root@fvdw-sta-kirkwood:/ # tar -xf glibc-mini-mkfs.xfs-25feb14.tar -C /
root@fvdw-sta-kirkwood:/ # /xfs_repair -n /dev/sda2
Phase 1 - find and verify superblock...
superblock read failed, offset 0, size 524288, ag 0, rval -1

fatal error -- Input/output error
root@fvdw-sta-kirkwood:/ #


[Jocko]

:?
After some searches, this would mean it is almost for sure a hardware error.
So extract the disk and plug in a laptop and try a diagnostic tool from the disk vendor.

[Jocko]

You will find tools here: http://www.seagate.com/fr/fr/support/do ... /seatools/

[schlum]

thanks very much Jocko, that is what I downloaded.

not much time available these days, but I ran almost all the tools available in the software, and all gave me a "pass", not fail.

But then, I put it back in the NWS2, and there, bad news, the kernel does not load any more, and the terminal waits for u-boot signal. The led blinks 2 seconds in red/blue, and then get fixed blue (not blinking) and nothing else.....

When using some recovery softwares, demo version, I can still see all the partition as the original ones, but no luck in getting a listing of files (after a few hours, generally the HDD freezes), and now I do not see a way to access the xfs paritition.

I am going to try a last time with Knoppix and trying to run xfs_repair, based on your past instruction, i.e. without mounting sda2.

If not, I think I ran out of luck.
Is there still a way I can reformat the disk to run either firmware, Lacie's or fvdw-sl, or without the console working, is it a "no go" ???

Thanks for all your help during the process. If I get something positive out of Knoppix, I'll let the forum know.
Cheers.

[schlum]

ok, some update:

to me it looks like the disk has some kind of hardware problem.

I was able to see its partitions again in Knoppix, and was again able to explore a bit the xfs partition. But at some point, the disk hanged/froze. Then I uploaded xfs_repair in Knoppix, and was able to run it identifying the correct partition as you indicated, and without mounting it. It started loading the same output: "Phase 1 - find and verify superblock..." and froze. And then, I had an epiphany, since I wanted to mount the partition again to see if I could copy some data from it (though I had tried it many times before without success): I turned off the power on the HDD and turned it on again.

And the terminal window started filling like shit ! xfs_repair was doing its stuff !!!

Not sure it helped though, but I understood that, when the HDD hang, it was enough turning the power down and switching it back on, and the HDD will follow up with the hanged process. So, by doing that, I was finally able to copy the most important data on my HDD onto my PC !!!
:woohoo

I am curious though as to which kind of problem can cause the HDD to freeze quite rapidly after a certain number of instructions, but then allow it to get back to the frozen process after a power shutdown and power on... Could it be a physical problem (but I do not hear any clicking sound)? or a power problem from the HDD Case (doubt it, because the problem was the same as in the NWS2 box) ? or would it be due to the filesystem ?

any how, is there a way I can use back the HDD when I am done saving all the data, since now it looks like the console will not work any more as it did in the past (I will try doing it again tonight, maybe the xfs_repair command helped somehow and I can load again the kernel onto it...) ? like formatting everything, partition it in a certain way and install Lacie or fvdw-sl firmware ? or is it all depending on first being able to connect with the console ?

Thanks very much for the help during the whole process, it ultimately made me more comfortable with linux command / permissions and it definitely was decisive to help me getting my data back.

cheers.

[Jocko]

Hi schlum,

I am curious though as to which kind of problem can cause the HDD to freeze quite rapidly after a certain number of instructions, but then allow it to get back to the frozen process after a power shutdown and power on... Could it be a physical problem (but I do not hear any clicking sound)? or a power problem from the HDD Case

controller card on your HDD is damaged (for example memory issue), this can explain your issue.

You can read this pagehttp://www.hddzone.com/seagate_pcb_swap_replacement_guide.htmlIf it is not an old disk, change it may be worth (without any guarantee !)

But look at the price of a controller PCB and for a new disk...