Reboot on Volume Import

[Peacebrother]

Hello,

I have a problem with my NAS System. After my Holiday, I started my NAS and it hung in the boot process. I decided to make a clean install on my USB Stick.

After this, I would import my ZFS Raid Volume but the system crashes and made a reboot. I can't read the text on the monitor, but it rans down the screen.

I have tried it with another USB Stick and with different FreeNas Versions - 9.3, 9.3.1, 9.10.1.

Does anybody knows what the problem could be?

Thanks

Thomas

—------------------------

Hallo zusammen,

Ich habe leider Folgendes Problem:
Als ich nach unserem Urlaub mein NAS wieder Hochfahren wollte hing es beim Hochfahren. Ich habe daraufhin einen Clean Install auf dem USB Stick durchgeführt.

Nachdem ich nun mein altes Volume (ZFSRaid) wieder importieren möchte, stürzt das NAS jedesmal ab und Bootet neu. Den Text auf dem Bildschirm kann ich leider nicht lesen, da er zu schnell vorüberläuft.

Ich habe auch schon die Installation auf einem neuen USB Stick probiert mit dem gleichen Ergebnis.

Mit folgenden FreeNas Versionen habe ich es auch getestet 9.3.1 und 9.10.1

Könnte mir bitte jemand eine Rat geben, wo der Fehler liegen könnte?

Falls noch Informationen Fehlen bitte melden.

Danke schonmal

Gruß Thomas

 

[danb35]

Hier wird meistens Englisch geschrieben. Wenn Sie lieber Deutsch schreiben, waere es besser in dieses Forum: https://forums.freenas.org/index.php?forums/german-deutsch.31/

 

[Peacebrother]

Thanks for the hint. I have edited the post.

 

[danb35]

Reboot on pool import sounds like a damaged pool, which is a Bad Thing (tm), but I've also seen it result from insufficient RAM. What are your hardware details?

 

[Peacebrother]

I have the following specs:

Asus Motherboard H87I-Plus
Pentium G3220
2x 4GB DDR3 1333 Corsair Memory
2x WD Red 2GB

Did you need more Infos?

 

[danb35]

That RAM is at the minimum, but should be adequate. You aren't using deduplication on your pool, are you?

 

[Peacebrother]

No, I don't use deduplication.

 

[Peacebrother]

Is it possible to boot BSD from a live CD like Freesbie to try to access to the ZFS Volume?

Or is this not a good idea?

 

[Ericloewe]

I don't see why not.

 

[Peacebrother]

I tried Memtest with a live CD. It has located a damaged memory module. I removed the damaged one, and tried to import the volume again. It was the same than before. :-(

But I have succeeded to take a photo from the screen, before the machine restarts.

Does anyone knows what the problem could be?

Thank you.

 

[Robert Trevellyan]

2x 4GB DDR3 1333 Corsair Memory

located a damaged memory module. I removed the damaged one, and tried to import the volume again. It was the same than before

Crashing on volume import may be a sign of a corrupted pool or insufficient RAM. In your case, both are possible, since you were running with bad RAM, and you now have only 4GB (half of the minimum).

 

[Peacebrother]

Tomorrow, I will get 16GB of fresh Memory .

I really hope this is the problem. I report the results.

Thank you

 

[Peacebrother]

I installed the new Memory (16GB Kingston) and it was the same than before. :-(

How can I find out whether the zfs pool is corrupt? And how can I fix it?

 

[Robert Trevellyan]

Please post the output of zpool import -Fn between code tags.

 

[Peacebrother]

This is the output from the command:

Code:

   pool: Daten																 
	 id: 7883946912849675898													
  state: ONLINE																 
status: The pool was last accessed by another system.						 
action: The pool can be imported using its name or numeric identifier and	 
		the '-f' flag.														 
   see: http://illumos.org/msg/ZFS-8000-EY									 
config:																		
																				
		Daten										   ONLINE				 
		  mirror-0									  ONLINE				 
			gptid/fc6b531d-26cd-11e3-b98e-60a44c6505d7  ONLINE				 
			gptid/fce10dbf-26cd-11e3-b98e-60a44c6505d7  ONLINE

 

[Robert Trevellyan]

This is the output from the command

Did you use uppercase 'F'?

My hypothesis is that your pool was corrupted by running with bad RAM. Please post the output of zpool import -Fn Daten. If necessary, also add a lowercase 'f'. The goal here is to find out whether ZFS sees any possibility of recovery by rolling back recent transactions, which is what the 'F' is for. The 'n' means "don't actually do it, just tell me what would happen".

 

[Peacebrother]

This is the output from the command line

Code:

[root@freenas ~]# zpool import -Fn Daten										
cannot import 'Daten': pool may be in use from other system, it was last accesse
d by freenas.local (hostid: 0x3bc7553c) on Sun Aug 21 03:17:45 2016			 
use '-f' to import anyway

If I add f

Code:

[root@freenas ~]# zpool import -Fnf Daten

The system crashes and reboot. See the picture from the screen in my older Post.

 

[Ericloewe]

The system crashes and reboot.

Oh, that's bad. So it crashes even during the dry run.

I'd probably consider the pool a goner.

 

[Robert Trevellyan]

If I add f ... The system crashes and reboot

I think your pool is lost.

You could try importing it with only one of the two disks connected, but I doubt that will make any difference.

Assuming that fails, I think all you can do is try to recover individual files from one of the disks using something like photorec.

 

[SweetAndLow]

I think your pool is lost.

You could try importing it with only one of the two disks connected, but I doubt that will make any difference.

Assuming that fails, I think all you can do is try to recover individual files from one of the disks using something like photorec.

Photorec does nothing on a zfs filesystem.

Sent from my Nexus 5X using Tapatalk