Hey everyone.

 

I'm currently testing unRaid with 2x2TB hdds.

The motherboard I'm using started 4-5h after the first start to beep some errors.

It is an AMI Bios and from what i can tell it sounds like "1 short high beep, followed by 1 short low beep"

 

No Rhythm. Just beeping some times. There are hours when nothing happens, and sometimes it beeps for minutes...

 

I really can't tell what went wrong.

And since it is linux based, i really can't help my self as a windows user.

 

Can anyone suggest a solution?

Motherboard battery is full.

 

Is there any system analysing tool for linux or maybe even unRaid?

Something that maybe could figure out, why it is randomly beeping.

 

 

Thanks in advance

 

The High/Low beeping sounds like it might be intending to be an alarm/siren.

 

What alarms and alarm thresholds do you have setup in BIOS?

It could be cpu temp related.

It could be system temp related.

It could be Power Management temp related.

It could be fan rpm related.

It could be voltage threshold related.

 

 

 

From what I know, it could be anything up to a CPU error or damaged RAM

 

If you have any idea, let me know.

 

(There are no tresholds set in bios)

 

 

Hum,

 

maybe there are any diagnosis tools?

 

 

 

When I boot the server, there is the standard high beep sound known from every PC boot.

And 20-30sec later there are 3 more beeps. (1 low, 2 high - with a delay of 2-3 seconds each)

Is this intented? Has everyone else those other beeps?

This is the normal beep sequence at unRAID boot.

Hm. Good to know :-)

 

Today there weren't anymore unusual beeps like the days before.

I'll stick close to it and report any issues, that are worth it.

 

Overall it looks like unRAID can handle Asus N4L-VM DH quite well.

I have had some trouble finding out how to boot from usb, but this belongs to AMI BIOS, not to the motherboard itself

 

In case anyone will ever read this:

 

simply boot to bios. switch to the boot order section and change: the hdd disc sequence first.

once you have set it to 1. USB 2. HDD 3. HDD...  you can go into the boot priority menu and directly select "FROM USB" instead of the HDD.

 

 

It is an AMI Bios and from what i can tell it sounds like "1 short high beep, followed by 1 short low beep"

 

No Rhythm. Just beeping some times. There are hours when nothing happens, and sometimes it beeps for minutes...

 

This is NOT Normal. So after the system is booted, if you hear any additional beeps, something is occurring that shouldn't.

pls confirm or deny:

 

once unRAID is booted:

pc speaker beeps are triggered only by bios itself.

 

because i will go nuts, if the real beep reasons are errors from unRAID (where i probably can easily read the reason)

when i start looking for errors in my hardware

 

hello again.

 

 

my random beeping still exists.

there were 2-3 days where nothing beeped

 

and now its occurring again.

from my point of view it occurs completely randomly

my computer is really cool now. (drives at 40°C, CPU ~43°C, GPU even lower)

system boots as intented. initial beeps included.

after booting everything (Point of View: software) seems to work smooth, even if it is beeping.

 

last time it beeped where tonight while my HDDs got precleared

array was offline.

 

always 1 high beep, 1 low beep in combination, every 10-60 seconds for 4-5 minutes

 

 

same thing happened some minutes ago.

this is what my syslog from unMenu is telling me:

 

Sep 17 11:30:24 Tower kernel: e1000e: eth0 NIC Link is Down
Sep 17 11:30:25 Tower ifplugd(eth0)[1229]: Link beat lost.
Sep 17 11:30:26 Tower kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Sep 17 11:30:26 Tower kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep 17 11:30:26 Tower ifplugd(eth0)[1229]: Link beat detected.
Sep 17 11:30:31 Tower kernel: e1000e: eth0 NIC Link is Down
Sep 17 11:30:32 Tower ifplugd(eth0)[1229]: Link beat lost.
Sep 17 11:30:32 Tower kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Sep 17 11:30:32 Tower kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep 17 11:30:33 Tower ifplugd(eth0)[1229]: Link beat detected.
Sep 17 11:30:36 Tower kernel: e1000e: eth0 NIC Link is Down
Sep 17 11:30:37 Tower ifplugd(eth0)[1229]: Link beat lost.
Sep 17 11:30:38 Tower kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Sep 17 11:30:38 Tower kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep 17 11:30:38 Tower ifplugd(eth0)[1229]: Link beat detected.
Sep 17 11:30:42 Tower kernel: e1000e: eth0 NIC Link is Down
Sep 17 11:30:43 Tower ifplugd(eth0)[1229]: Link beat lost.
Sep 17 11:30:44 Tower kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Sep 17 11:30:44 Tower kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep 17 11:30:44 Tower ifplugd(eth0)[1229]: Link beat detected.
Sep 17 11:30:48 Tower kernel: e1000e: eth0 NIC Link is Down
Sep 17 11:30:48 Tower ifplugd(eth0)[1229]: Link beat lost.
Sep 17 11:30:50 Tower kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Sep 17 11:30:50 Tower kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep 17 11:30:51 Tower ifplugd(eth0)[1229]: Link beat detected.
Sep 17 11:32:05 Tower kernel: e1000e: eth0 NIC Link is Down
Sep 17 11:32:05 Tower ifplugd(eth0)[1229]: Link beat lost.
Sep 17 11:32:07 Tower kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Sep 17 11:32:07 Tower kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep 17 11:32:08 Tower ifplugd(eth0)[1229]: Link beat detected.
Sep 17 11:32:18 Tower kernel: e1000e: eth0 NIC Link is Down
Sep 17 11:32:18 Tower ifplugd(eth0)[1229]: Link beat lost.
Sep 17 11:32:19 Tower kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Sep 17 11:32:19 Tower kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep 17 11:32:20 Tower ifplugd(eth0)[1229]: Link beat detected.
Sep 17 11:32:23 Tower kernel: e1000e: eth0 NIC Link is Down
Sep 17 11:32:23 Tower ifplugd(eth0)[1229]: Link beat lost.
Sep 17 11:32:25 Tower kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Sep 17 11:32:25 Tower kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep 17 11:32:25 Tower ifplugd(eth0)[1229]: Link beat detected.
Sep 17 11:32:31 Tower kernel: e1000e: eth0 NIC Link is Down
Sep 17 11:32:31 Tower ifplugd(eth0)[1229]: Link beat lost.
Sep 17 11:32:33 Tower kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Sep 17 11:32:33 Tower kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep 17 11:32:33 Tower kernel: e1000e: eth0 NIC Link is Down
Sep 17 11:32:35 Tower kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Sep 17 11:32:35 Tower kernel: 0000:02:00.0: eth0: 10/100 speed: disabling TSO
Sep 17 11:32:35 Tower ifplugd(eth0)[1229]: Link beat detected.

 

my network card is able to run at 1000 mbit, but seems to be forced to run at 100 because the router is 100mbit only.

non the less, that shouldnt be a problem or the reason for those beeps i guess.

 

 

right now the only thing i could imaging to be the reason is a defect within my CPU or motherboard that sometimes leads to miscalculations.

cables should be fine, since i dont move anything and there is no beep for hours/days

but without any manipulation from my side, it starts, beeps for a short time stops it afterwards.

 

 

i really hope my english is good enough to explain myself here. if anything is not understandable, let me know

 

if you have any idea what could course this, please just write them down here

Your syslog showed the reason for the "beeps."  The network connection is being lost and then re-established, again, and again.

 

You have either a loose connection on the network cable, or a bad network cable, or a bad router port, or an incorrectly wired network cable (using the telephone standard instead of the LAN standard pairing of conductors)

 

Simple test.  Un-plug the network cable...wait a few seconds, then plug it in again... I think you'll hear the same beeps.

 

Joe L.

 

 

 

 

this IS THE REASON! thank you!

this explains why i cannot reach the web interface directly after the beeps

 

last time it beeped (again the 100x time today) my wife said "i feel really sorry for you ". she never says that! (telling you that i were really frustrated here.)

 

the unRAID server beeps, even when i'm sleeping. so i guess there is no loose cable contact here

--> meaning either the onboard network card won't work (well i dont know if i should by a new one for 5$ or maybe some intel for 25$. if there are real performance differences maybe you could let me know)

--> or it is my good old 100mbit fritzbox. but my gigabit router should come sooner or later.

--> the cable is maybe badly isolated to that other wires could cause this. i will by a new one to be sure. (same question: i need 15 meters, how much do i need to invest here? cat5e or Cat6 should be good enough, right?)

 

 

 

thx Joe for translating my logfile

the unRAID server beeps, even when i'm sleeping. so i guess there is no loose cable contact here

It could just be a tiny amount of corrosion in the connector, or a bad crimp on the connector end (either end of the cable), and microscopic vibrations could cause it to lose connectivity, even as you sleep.

 

In any case, you are on your way to figuring it out.

 

Good luck.

 

Joe L.