February 15, 201016 yr I've been reading for the last few hours on how to get around my problem and i still cannot come up with a solution. I am able to boot from my USB Flash Drive (SanDisk Cruzer Micro 2GB) only when its formatted to FAT. Once it boots i am able to select either unraid OS or memtest86+ When i select Unraid it goes like this: Loading bzimage.................................. Loading bzroot.............................................................. And that's basically it. it just keeps creating more .. while it tries to load bzroot. not sure what the problem could be as this is a new USB drive. Things i've already tried/done Re-formatting the Flash drive and re-loading everything Re-downloading syslinux and Unraid Server removed U3 Software using U3 Un-installer Fast boot disabled Serial ports disabled parallel ports disabled audio ports disabled Swapping memory banks (1gb = 2x512mb) I'm running out of ideas! help please Motherborad = MSI KT3 Ultra-2
February 15, 201016 yr Author Not sure what i did, but it finally worked. walking through setup as we speak
February 15, 201016 yr I've been reading for the last few hours on how to get around my problem and i still cannot come up with a solution. I am able to boot from my USB Flash Drive (SanDisk Cruzer Micro 2GB) only when its formatted to FAT. Once it boots i am able to select either unraid OS or memtest86+ When i select Unraid it goes like this: Loading bzimage.................................. Loading bzroot.............................................................. And that's basically it. it just keeps creating more .. while it tries to load bzroot. not sure what the problem could be as this is a new USB drive. Things i've already tried/done Re-formatting the Flash drive and re-loading everything Re-downloading syslinux and Unraid Server removed U3 Software using U3 Un-installer Fast boot disabled Serial ports disabled parallel ports disabled audio ports disabled Swapping memory banks (1gb = 2x512mb) I'm running out of ideas! help please Motherborad = MSI KT3 Ultra-2 Run memtest86+ for awhile. Make sure you have no memory errors! If your memory is OK, then you could try a different flash key. Maybe your mobo will like different brand flash key.
February 15, 201016 yr Not sure what i did, but it finally worked. walking through setup as we speak I just noticed your post Anyway, you should still run a memory test, get that out of the way.
February 15, 201016 yr Author having problems with my PCI ethernet card now and i'm unable to get onto my network because it can't recognize the Ethernet device, picked up a new one so I'm about to throw that in the specific error i'm getting with my NIC card is eth0: Error fetching interface information: Device not Found
February 15, 201016 yr Author Just an update. Everything is now running OK. My Raid controller along with my 3 (2tb WD) Hard drives are on the way. This way i can test out the mobo + check parity to make sure everything is running good before i continue to upgrade purko: running a full memtest as we speak.
February 15, 201016 yr Author memtest came back with 0 errors, once my harddrives + raid controller arrive i will be testing and posting logs of my setup in the motherboard section
February 16, 201016 yr Does your system still take a while to boot when you boot it up? I've had this happen with my original USB flash (turned out to be a dud flash). Once I replaced it, the system booted quite quickly. Maybe try a new USB flash? Also, I'd run a memtest overnight just to be sure.. Your post between starting/stopping a memtest is only about 90 minutes, which is ok for a few passes, but I'd run it overnight just to make sure (something I like to do to really test the ram).
February 16, 201016 yr Author Does your system still take a while to boot when you boot it up? I've had this happen with my original USB flash (turned out to be a dud flash). Once I replaced it, the system booted quite quickly. Maybe try a new USB flash? Also, I'd run a memtest overnight just to be sure.. Your post between starting/stopping a memtest is only about 90 minutes, which is ok for a few passes, but I'd run it overnight just to make sure (something I like to do to really test the ram). It does, takes me about 3 minutes or so to fully boot up, weird because i picked up this SanDisk today since my Sony Mem stick didn't seem to work properly. Is it possible to change the memory stick further down the road while keeping my settings/data? I'd like to initially test out a 3 HDD configuration to get a feel for unraid and see if i'll be sticking with it or not Started a memory test now. Will be up at 7AM to check it out before i head out to work
February 16, 201016 yr Is it possible to change the memory stick further down the road while keeping my settings/data? Yes. Just copy the contents, including config folder. See this: http://lime-technology.com/wiki/index.php?title=FAQ#How_do_I_update_files_on_my_flash_drive.3F
February 19, 201016 yr Author Parity has been computed, it took forever! now i'm checking parity and its taking a while too. I'm only running at 34,4xxx KB/sec. Should be done in about 900 Minutes is this normal? I'm running three 2 TB Drives Off a Promise SATA300 TX4
February 19, 201016 yr Parity has been computed, it took forever! now i'm checking parity and its taking a while too. I'm only running at 34,4xxx KB/sec. Should be done in about 900 Minutes is this normal? I'm running three 2 TB Drives Off a Promise SATA300 TX4 Yes, it is normal... and about twice as fast a rate as on my older PCI based server.
February 19, 201016 yr That seems slow to me, but then again you're running it off the PCI Bus. To give you an idea of how the PCI Bus is limiting you ... I'm running 3 2TB WD Green drives (2 Data and 1 Parity) off the built-in SATA connectors (ICH9?) and my initial speed is 100,000 - 110,000 K/s with a completed overall average of 75,274 K/sec
February 19, 201016 yr That seems slow to me, but then again you're running it off the PCI Bus. To give you an idea of how the PCI Bus is limiting you ... I'm running 3 2TB WD Green drives (2 Data and 1 Parity) off the built-in SATA connectors (ICH9?) and my initial speed is 100,000 - 110,000 K/s with a completed overall average of 75,274 K/sec I'm limited by the bandwidth of the PCI bus. I've got 11 drives, and a total bandwidth of 133MB/s. Divide that by 11 drive and each gets 12Mb/s MAX possible. I think the two SATA drive connectors on the MB might not share the bandwidth with the PCI bus, even so, 9 drives have to share the 133 MB/s = 14 MB/s max per drive... Joe L.
February 22, 201016 yr Hi mate. Not sure if you've tried this, but I came across this problem with my SanDisk 2GB Cruizer (In in the packaging). Try formatting it in Windows using a different "Allocation unit size" for FAT16 file system. To do ths, follow the steps below: 1). In Windows, go to Computer Management (Or Start > Run > type: "compmgmt.msc") > Disk Management 2). Right-click on the USB drive and select Format... 3). For the "Volume label:" make sure it is labeled "UNRAID", all upper case and excluding the quotation marks 4). For "File system:" select "FAT" 5). For "Allocation unit size", I'd try first 1024 or 512 6). As suggested earlier, get the latest syslinux.exe and issue a "syslinux x: /ma" under CMD, x: being your USB drive letter. 7). Get a fresh download of the OS, extract and copy to your USB Drive. Its funny you mention this, because I had to do the steps above in order to get mine going. Once you've verified that the required on board hardware which isn't required for unRAID is disabled and the correct USB boot options are enabled (Ie: USB ZIP, USB HDD, USB CDROM, USB etc...) in BIOS, it should boot up and will work like a charm. If all else fails, use a USB Drive Tester (Free to download, just Google USB Drive Tester and download). That will to a thorough sector-by-sector integrity check of your USB drive to detect for any corrupt sectors, which might be hampering your boot up for the unRAID OS to start up properly. Good Luck!
February 23, 201016 yr Me again, for Steps 5 & 6, I have the corrections below: 5). For "Allocation unit size", it should be left "Default" 6). As suggested earlier, get the latest syslinux.exe, you have to issue the command in CMD as "syslinux -ma x:" under CMD, x: being your USB drive letter. My apologies.
Archived
This topic is now archived and is closed to further replies.