April 2, 200917 yr Well I just finished my first unraid build... During first boot it seems to stop at a line(S). I am unable to connect to //tower Table [sSDT](id 0002) - 50 Objects with 0 Devices 8 Methods 1 Regions tbxface-0596 [00] tb_load_namespace : ACPI Tables successfully acquired Followed by a blinking _ ... I am running the unraid official supermicro board(MBD-C2SEE-O LGA 775 Intel G43 ATX), with and adaptec 1430SA 4 port board (tried with out it) and a SansDisk micro cruzer 4gb flash drive (formated to fat at 3.77gb). I have not really attached any drives yet, though I did try one on the adaptec board without success.. Using version 4.4.2 downloaded from unraid website. Any ideas? What is happening? Since this is my first boot, I don't even know if its complete or not. I assume there is an issue because I cannot connect to //tower... Sorry since the server doesn't seem to be up I can't run a syslog... I am running memtest now...
April 2, 200917 yr Install at least one disk and see if its able to boot. Running unRAID with zero disks is not something I've ever seen done before.
April 2, 200917 yr Author I did connect a drive both on the adaptec and on the ICH10, same results unfortunately. Thanks for suggestion.
April 2, 200917 yr I would try some of the boot codes described here in the wiki: http://lime-technology.com/wiki/index.php/Boot_Codes specifically those involving "acpi" since it seems to freeze just after starting to initialize it. You might enable/disable it in the BIOS and see if that makes a difference as well. Joe L.
April 2, 200917 yr Author I think I may have found the issue... basic stuff as usual (I am the king of typos in my vbs/msi lol)... The CPU was overheating, at least in the bare supermicro bios it said "HOT". So I removed the CPU, cleaned, reapplied arctic silver and remounted the cooler. It probably was those blasted intel clips, for some reason I always have a problem with those things, as simple as they are... I am going to run memtest for 30min or so, then check temp and try a boot. Though it did get farther in the boot process after reseated the cpu. Well things were still running good this morning, a reboot and temp check was ok. So lesson learned.
Archived
This topic is now archived and is closed to further replies.