Issue after upgrading lacie firmware

[fvdw]

I assume you used the new version of xfs_repair. I think it will use the swap, you need to start it with the -m option I guess. The output doesn't show that it aborts because of memory shortage, it seem you need to remove the log before xfs_repair can continue. This prefetch remark to reduce memory footprint you can also use, seems you need to use -P option. (Note that this is a capital).

You coul also try what the old version does when swap is available

[turmeric]

Something magical happened... You remember that I was not able to mount my drive...

Out of desperation I tried it once again... and suddenly it works :hammerhead

Code: Select all

find /mountpoint

Is running now for minutes and shows me full content of my NAS, such as

Code: Select all

/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8357.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8669.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8590.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8610.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8427.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8714.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8567.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8402.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8374.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8569.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8377.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8670.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8628.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8747.JPG
/mountpoint/shares/3/_Genie Timeline/0/D/timelapse/20140609/Take 4/DSC_8525.JPG


So somehow something mus have happend - maybe the additional memory was helpful for that? No idea...

However, since I can see my data now - would I just try to start my NAS again 'normally', or do I risk that I might get corrupted result again?

[fvdw]

:punk
I saw in you earlier attempt to run xfs_repair that it wrote a new sperblock before it ran out of memory. Maybe that was enough. Wheter or not the sawp is the reason. You could test by trying to mount it after stopping the swap. (swapoff /dev/sej).

If mount goes ok and all data is available then I think you could use the nas normally. If you have ssh access then you could check out if the lacie firmware contains xfs programs to check the file system

[turmeric]

Okay, I try to login via SSH - what user would I use and what password?

Tried as admin with the password I used via webinterface, however that does not work...

[fvdw]

If it is the lacie firmware that you are using ?
Then you need to investigate on the internet (Nas-central).
I am sorry but I don't use that firmware so I do not know these details

If it is the fvdw-sl firmware then username: root, password: giveit2me

[turmeric]

Hi all,

sorry for not getting back earlier here as I was out of town...

After all, I tried to startup the 5big as usual - nothing changed (what most probably is not a surprise). SSH access - with the credentials that I got on the net and from LACIE support - did not work.

So I now wanted to start again with fvdw-sl firmware. As soon as I try to run xfs_repair or mount (chmod after upload done) - what worked before (even for the mount at the end) - nothing happens. Basically, I get disconnected and have to login again.

It seems, that the one time I started up the NAS with the LACIE Firmware must have changed something...?

Thanks,
turmeric