I tried beta 9 and couldn't get it to work.  Just tried beta 10 and same problem. 

I am using asus p5pe-vm mobo with sata promise pci.  Dead NIC on mobo so have netgear gigabit pci card. I have not had any problems with unraid 3.

 

Boots ok initially from flash but then get

Initializing USB storage driver.

Controller is probably using wrong irq

Device not accepting address 2 error 110.....

 

I have tried multiple usb settings without luck.  Any suggestions?

 

 

Since I was recently informed of this, I'll pass it on.  Make sure your USB drive has a volume label of "UNRAID" minus the quotes.  4.0 won't work properly otherwise.

 

The new version of unRaid uses the volume label on the flash drive to find the correct 'scsi' device to mount at /boot.

It  was much easier when SATA drives were not supported.  now, with their support, the device assignment is unpredictable depending on your specific hardware/motherboard.

On 3.0 it used to be that the flash drive was always /dev/sda.  With 4.0 and SATA controllers it could be something else and a hard-disk assigned /dev/sda.

Thanks.

It does.

Good tip, and very close to item 3 on the upgrade instructions, but not mentioned as a part of a new install.

 

/Rene

Just out of interest, does anyone with this motherboard have a similar issue?

I have the same MB & Promise controllers, but have been waiting on the sidelines with a working 3.1-beta2 setup, as I was busy rebuilding my primary PC.  With that behind me, however, I may give the 4.0-beta10 code a try this weekend.  I'll post my results.

I tried beta 9 and couldn't get it to work.  Just tried beta 10 and same problem. 

I am using asus p5pe-vm mobo with sata promise pci.  Dead NIC on mobo so have netgear gigabit pci card. I have not had any problems with unraid 3.

 

Boots ok initially from flash but then get

Initializing USB storage driver.

Controller is probably using wrong irq

Device not accepting address 2 error 110.....

 

I have tried multiple usb settings without luck.  Any suggestions?

 

 

 

Try this.  Edit your 'boot/syslinux.cfg' file and change the line that reads:

 

append initrd=bzroot rootdelay=10

 

to

 

append initrd=bzroot rootdelay=10 noapic

 

This worked 

I did not have apic support enabled in the bios.  I then changed boot/syslinux.cfg back to append initrd=bzroot rootdelay=10 without the noapic and enabled acpi apic support in the bios and was able to boot without any problem. 

jgs2n,

 

Glad you got your system up & running 

 

I just finished upgrading mine from 3.1-beta2 to 4.0-beta10 without a hitch (i.e., no need to modify syslinux.cfg).  Although, as Tom suggests in his installation instructions, all the drives initially came up "missing" and I had to reassign them on the Device tab.  Interestingly enough, however, all the scsi port numbers changed.

 

BillK