Jump to content

*SOLVED* New clean V6.1.0 install - Can't boot


efrhm

Recommended Posts

Hello',

I'm a 4.7 user. After performing a step by step clean install by "Upgrading to UnRAID v6" post, I can't boot up my system.

I didn't get a response to "grep --color lm /proc/cpuinfo" command, so I've checked and it seems that Intel dual core E2140 supports 64bit.

Other then that, I've tried 2 different flash drives. Both were formatted (One for FAT, the second for FAT32). Both made bootable.

I've checked the BIOS and the USB flash drive is marked as the first boot device.

I also tried clean pure version without my current key and *.CFG files. Did'nt helped.

Any advice?

Thanks

 

 

 

 

 

Link to comment

Hello',

I'm a 4.7 user. After performing a step by step clean install by "Upgrading to UnRAID v6" post, I can't boot up my system.

I didn't get a response to "grep --color lm /proc/cpuinfo" command, so I've checked and it seems that Intel dual core E2140 supports 64bit.

You should have gotten a response.  Do you feel certain the command was correctly typed?  That lm is a lowercase el plus em.

 

Other then that, I've tried 2 different flash drives. Both were formatted (One for FAT, the second for FAT32). Both made bootable.

I've checked the BIOS and the USB flash drive is marked as the first boot device.

I also tried clean pure version without my current key and *.CFG files. Did'nt helped.

Any advice?

Thanks

 

Can you tell us exactly how far it got, what was the last thing to appear on the monitor?

Link to comment

Two ideas -

 

* Buy another flash drive, make sure it's a good quality brand name one like Sandisk, etc, and format and prep and test it.  Perhaps the 2 flash drives you tried are not compatible somehow?

 

* Take one of your flash drives (not the v4.7 one), format it, run make_bootable, prep it with v6, but do NOT copy anything else to it.  We want to see if it can boot the boot menu first, then if it can boot a fresh new unRAID with no configuration at all.

 

Can you show us the contents of the root folder of your flash drive, and the contents of the config and syslinux folders?

Link to comment

One of the flash drives I'v used is a 16GB Sandisk mini Cruzer. The other one is brand less.

I've already done the thing you're suggest: format it again and copy only Ver 6.0 files. Didnt helped.

Please find attached snapshots of the content (with some old *.cfg )

root.PNG.9c8bdfb8d64cce3e0f5293ef9a3c243f.PNG

Link to comment

One of the flash drives I'v used is a 16GB Sandisk mini Cruzer. The other one is brand less.

I've already done the thing you're suggest: format it again and copy only Ver 6.0 files. Didnt helped.

Just to be absolutely complete, since you didn't mention it, you did run make_bootable, and there were no issues with it?

 

If so, you can take it and try booting any other machine you have (just make sure the machine is allowed to boot from USB before the hard drive).  It's safe, won't change anything on the system.  All you want is to see if you can get the boot menu first, then will it boot to an unRAID menu or dialog, then you can quit it.

 

And as he said, keep rechecking/correcting the BIOS boot order.

Link to comment

One of the flash drives I'v used is a 16GB Sandisk mini Cruzer. The other one is brand less.

I've already done the thing you're suggest: format it again and copy only Ver 6.0 files. Didnt helped.

Just to be absolutely complete, since you didn't mention it, you did run make_bootable, and there were no issues with it?

 

If so, you can take it and try booting any other machine you have (just make sure the machine is allowed to boot from USB before the hard drive).  It's safe, won't change anything on the system.  All you want is to see if you can get the boot menu first, then will it boot to an unRAID menu or dialog, then you can quit it.

 

And as he said, keep rechecking/correcting the BIOS boot order.

 

If I remember correctly, the user has to hit a key to actually config the flash drive.  Just executing the program does not automatically modify the flash drive to be bootable.  And you have to run the program from the flash drive as 'administrator'.  If you don't evoke with administrator privileges, the drive will NOT be modified! 

Link to comment

I can boot from the Flash drive on other,  windows, machine.

Weird I can't boot from any USB port on my server (unless its the old 4.7 ver. on the old 256MB flash drive)

Any more ideas?

 

Let make sure I understand what you said here:  You can boot from the new flash drive on your windows computer but the same flash drive does not boot in your server?  If this is the case, I see some things to look at. 

 

First, is that new flash drive by any chance a USB3 drive?  It may be that your older hardware and/or BIOS is having an issue with USB3 hardware.

 

Second thing is double check is the BIOS and its settings.  Since you are coming from version 4.7, I assume that this is old hardware.  Are there multiple options to boot from USB?  Another thing is that it is possible that the BIOS is looking for something that is formatted in FAT and not FAT32.  (I can't remember exactly how large a partition FAT can format.)  You might check to see if the MB Manufacturer has released an update to the BIOS. 

 

Along these same lines have a look at the Booting up section about half way down this page:

 

    http://lime-technology.com/getting-started/

 

With some older MB, there were a number of options of the way a BIOS looked at USB peripherals when using them to boot from. 

 

EDIT: fixed first sebntence

Link to comment

Was this post a typo?

I can boot from the Flash drive on other,  windows, machine.

Weird I can't boot from any USB port on my server (unless its the old 4.7 ver. on the old 256MB flash drive)

Any more ideas?

because your post just before that was

I've run make_bootable again on another machine I have.

Well, it didn't boot from the flash_drive on a windows machine . Probably I'm doing something wrong.

Which is it?
Link to comment

A shot in the dark here.. but some thing stupid I did the other day..

I ran make_bootable from the the d/l source files instead of the actual make_bootable file on the flash..

Two windows open and I used the wrong file in the wrong window more than once.

Cost me a few hours trying to figure that one out.

Link to comment

I guess I have an old hardware (BTW, new Flash drives I've used are not USB3).

I've decided to return to Ver 4.7 on this machine, rebuild the parity, let my family be happy again...  and in a few weeks time build a modern machine running Ver 6.

HOWEVER, two of my data HD are reported missing now. Configuration isn't valid. These HD are shown on the BIOS.

What is the safest way to get everything working again?

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...