12345

[RuZleBiFf]

12345

[armandh]

possible drive failure
or whatever it is doing 20 seconds into the boot

[al562]

Hi RuZleBiFf,

Welcome to the NAS4Free forum. Below is information you may find helpful.

Please read and follow the Forum Rules & Guidelines and the FAQs.
By doing so you will:

• Understand what information you should provide when you ask a question or report a problem/bug. By providing all information upfront you will get faster and better answers; that's what you want right?
• Find the answer to your problem in the FAQs or use the Advanced search to search the forum.
• Help us understand your problem and allow us to provide an accurate answer/solution without asking additional questions.
• Help the community by keeping the forum clean, focused and professional.
• Remember to use WebGUI Tab> Help|Report Generator when creating new topics/threads.
• If you have not, then please read the latest Setup & User Guide.

This is simply not enough information to even venture a guess. What do you see on the servers' screen?

Regards,
Al

[alexey123]

RuZleBiFf , connect monitor to server and send screens from it. If menu is all right, not new messages, check dmesg --> 6) Shell, #dmesg.

[RuZleBiFf]

12345

[RuZleBiFf]

I could not get the image from dropbox to the forum, but here is the direct link.
Something is obviously wrong
https://www.dropbox.com/s/gynjdwmw9m8y2 ... reeNAS.JPG

[alexey123]

This is symptom about memory fault. Check memory over bios, if success try clean contacts with eraser

or

Not use alcohol for clean contacts

How many memory you have?

[raulfg3]

I use a copper brush (I use it to clean my iron solder, but usefull to clean contacts)

[RuZleBiFf]

12345

[RuZleBiFf]

12345

[alexey123]

How many ram you have?

[alexey123]

May be you lost one disk

[RuZleBiFf]

12345

[alexey123]

I have 2x1GB RAM

I don't know, file-browsing is working perfect for the first 20 seconds, and i only have 1 large array (2 disks, raid 0), so if 1 disk is down, the array should be wrecked.

Inspect /var/run/dmesg.boot - open it with Advanced|File Editor. You will have saved in cache copy, when your server was stopped.
Also try to boot with only 1G memory - remove first card from slot, then second card

[al562]

Hi RuZleBiFf,

Alexey is quite correct. Once you are sure memory is good (run memtest86 to test although physical test is good too), if it is still crashing, try booting with LiveCD or LiveUSB and see if it stays up.

Have re-written my 1. post, hope it's more informative now

Yes, now we have something to work with, thanks .

Regards,
Al

[ChriZathens]

The guys have a point about a faulty memory, but there is also another possibility, that the file system needs fsck and it stucks while trying to perform this on boot. It has happened to me in the past.
Your situation may be the same- I notice that system hangs while performing an fsck operation.
Go in disks|mount point, select to edit the mount point for your raid.
In there there is an option called File system check ( Enable foreground/background file system consistency check during boot process.)
If this option is checked un check it and try to reboot again and see if the system stays alive this time.
If you succeed this time, you should then manually umount and perform an fsck because it appears to be necessary.
P.S.: if you can't enter the webui at all, then try to use the live cd and do an fsck from there. Howto is in the wiki: http://wiki.nas4free.org/doku.php?id=faq:0001&s[]=fsck

[RuZleBiFf]

12345

[raulfg3]

FAQ nº 1 in wiki : http://wiki.nas4free.org/doku.php?id=faq:0001

[ChriZathens]

Glad I helped

P.S.: Such fsck problems are an additional reason I don' t regret I converted to zfs...