I have installed an UNRAID version 4.4.3 on a cruzer mini 256. This same flash worked fine on an ASUS AN8 board with  an older software version. Now that I have changed to Abit AB9 Pro I cannot see network. I did a clean install of the UNRAID software, upgraded to the latest BIOS - 22.

 

When I go into root and try ifconfig eth0 I get everything except the network address.

 

Please help get my //tower working! 

I have installed an UNRAID version 4.4.3 on a cruzer mini 256. This same flash worked fine on an ASUS AN8 board with  an older software version. Now that I have changed to Abit AB9 Pro I cannot see network. I did a clean install of the UNRAID software, upgraded to the latest BIOS - 22.

 

When I go into root and try ifconfig eth0 I get everything except the network address.

 

Please help get my //tower working! 

If your motherboard has more then on LAN port, make dure you are plugged into the correct one.

 

What do you see if you type

ls -l /boot

 

What do you see when you type

mount

 

Joe L.

Can you access it thru Http://<IP Address> ? I have the same problem before if you can access it thru your IP <192.168.XX.XX> you need to change something on your router if you are using one.

 

 

If your motherboard has more then on LAN port, make dure you are plugged into the correct one.

 

What do you see if you type

ls -l /boot

 

total 0

What do you see when you type

mount

 

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

usbfs on /proc/pub/usb type usbfs (rw)

 

 

 

If your motherboard has more then on LAN port, make sure you are plugged into the correct one.

 

What do you see if you type

ls -l /boot

 

total 0

What do you see when you type

mount

 

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

usbfs on /proc/pub/usb type usbfs (rw)

 

 

Basically, you have no network because your flash drive was not identified as the UNRAID volume.  It therefore was not mounted at /boot  (there should have been lots of files listed, there were none, and it is not listed as being mounted either)  Since it was not mounted, unRAID could not read the network.cfg file to load the network card driver as appropriate.

 

Type

ls -l /dev/disk/by-label

 

What do you see?  It should look similar to this if the UNRAID label exists and is recognized.

ls -l /dev/disk/by-label

total 0

lrwxrwxrwx 1 root root 10 Aug 23 19:01 UNRAID -> ../../sda1

 

If you get the flash drive to mount properly, you will get your connectivity back.  (It will mount when its label is in /dev/disk/by-label)

It will get there when the BIOS properly recognizes the partitioning on the flash drive and finds a volume label = UNRAID

 

Joe L.

 

This is what I get:

 

lrwxrwxrwx 1 root root 10 Sept 29 10:35 Movies_o_-_z -> ../../hdb1

 

"Movies_o_-_z" is the name of a a HD that I am reusing...

 

I have tried this on two different USB drives with the same result. Like I mentioned previously, the original flash drive worked before on a different system...

 

 

Also, when I run the ethtool eth0 command I get the appropriate speed/duplex. When I unplug the cable that information is changed. So, I think that the unRaid sees my network?

Since AB9 Pro has two NICs do I have to disable one of them for this board to function? I have read that people were having "issues" with one of the network connectors.

 

You don't have to disable the uniused, NIC.

 

Generally it is my habit to disable any hardware I'm not using and free up IRQ's,.

 

I.e. serial, parallel, FDC, unused NICS, etc, etc.

Apparently, you have ignored the basics of I said earlier.

 

The USB flash drive MUST be mounted at /boot for unRAID to find its configuration files.  If it is not mounted, nothing will work for the unRAID software... regardless if you think you have plugged the ethernet cable into the correct connector on the motherboard.

 

To identify the USB flash drive, unRAID looks in the /dev/disk/by-label directory to find it.  Since it did not find it, it did not mount it, and your unRAID server is not running the emhttp process that serves up web-pages because the "config" folder with the "go" script that would start it is not there..  (the disk with the UNRAID label was not there in your listing of /dev/disk/by-label, resulting in this whole problem.)

 

I know you said you did a fresh install onto your flash drive.  Did you set the volume label to UNRAID?  (Yes, it might have been set when you did the original install, but wiped away when you did the "fresh install")

 

To get any more help from anyone, you will need to supply a copy of the syslog... but... you cannot copy it to /boot as usually instructed, since your flash drive is not mounted there...  best you can do for now is cut and paste sections from it from the telnet window.

 

So... back to basics...

Did you use the HP tool to format your flash drive? (your old MB BIOS might have been able to figure out the partitions, perhaps the new one cannot)

 

Did you set the volume label to UNRAID?  (six characters, all upper case)

 

somebody with the same motherboard might be able to help you with any BIOS options.

 

Until you can get the flash drive to mount properly on /boot, you will never see any web-page on //tower.

 

You might try this command, and see if the USB drive partition is even seen by the Linux kernel.

cat /proc/partitions

 

If it is, and you can see by its size it is "sda1"  (first partition on /dev/sda) then try this and let us know what it says:

vol_id /dev/sda1

 

(Obviously, if your flash drive shows up in the partition listing  as sdb, or sdc, substitute the appropriate drive in the above command. Make sure you request the volume ID of the first partition by using the partition with the number "1" at the end of its name.)

 

You might try unplugging the hard disks for now and see if the flash drive can then be seen... it might be anything, from a bad USB header, to a bad cable, to improper memory voltage settings...  but until the flash drive is mounted at /boot... you will get nowhere.

 

Joe L.

Joe,

 

Thank you very much for the suggestions.

 

Did you use the HP tool to format your flash drive?

I used the regular format technique from Windows. Then I ran syslinux.exe.  I am not aware of HP tool. I did not see it in the original instruction. Please forgive my novice ways. I am not a Linux user, just Windows and Mac.

 

Did you set the volume label to UNRAID?  (six characters, all upper case)

Yes.

 

I will try the other suggestions and report back on Thursday. Very frustrating...

 

 

 

Joe,

 

Thank you very much for the suggestions.

 

Did you use the HP tool to format your flash drive?

I used the regular format technique from Windows. Then I ran syslinux.exe.  I am not aware of HP tool. I did not see it in the original instruction. Please forgive my novice ways. I am not a Linux user, just Windows and Mac.

 

Did you set the volume label to UNRAID?  (six characters, all upper case)

Yes.

 

I will try the other suggestions and report back on Thursday. Very frustrating...

 

 

 

You probably did not look in the wiki... http://lime-technology.com/wiki/index.php?title=Unofficial_Documentation

 

There are specific and more detailed instructions there on setting up the USB flash drive at this link.

http://lime-technology.com/wiki/index.php?title=USB_Flash_Drive_Preparation

 

Joe L.

It's probably as Joe stated, the UNRAID flash is not being mounted on /boot.

You can tell this by doing

mount

 

You should see a line like this (but may be a different drive).

 

/dev/sdd1 on /boot type vfat (rw)

 

 

Also when the system boots up, it will try to initialize the network adapter.

If it does not find the network.cfg, it will leave some errors on the screen.

You are correct. I did not resort to HP utility to format the flash drive. But, the other steps I followed meticulously, with the exception of -ma, same as the last time when this drive worked.

 

I am assuming that since the unRaid loaded to a point of the login screen that the drive itself is functional. Am I mistaken in that?

 

I can try the HP tool and see if that makes a difference. I am not in front of the PC now, but I wish I was...

 

And, by the way, I did not see any "errors" on the screen, unless they scrolled up to fast for me to notice.

I am assuming that since the unRaid loaded to a point of the login screen that the drive itself is functional. Am I mistaken in that?

The drive seems to be functional or you would not have seen the linux kernel come up and there would not be a login: prompt.

The question is.. Does it have the UNRAID label on it and was it mounted by the system startup.

 

I am assuming that since the unRaid loaded to a point of the login screen that the drive itself is functional. Am I mistaken in that?

The drive seems to be functional or you would not have seen the linux kernel come up and there would not be a login: prompt.

The question is.. Does it have the UNRAID label on it and was it mounted by the system startup.

 

 

The volume label is correct - UNRAID

 

...was it mounted by the system startup. - again, please forgive my novice ways, but how would I know this step? I am not trying to be ignorant, just inexperienced...

I am assuming that since the unRaid loaded to a point of the login screen that the drive itself is functional. Am I mistaken in that?

The drive seems to be functional or you would not have seen the linux kernel come up and there would not be a login: prompt.

The question is.. Does it have the UNRAID label on it and was it mounted by the system startup.

 

 

The volume label is correct - UNRAID

 

...was it mounted by the system startup. - again, please forgive my novice ways, but how would I know this step? I am not trying to be ignorant, just inexperienced...

If it was mounted, it would have been listed when you typed "mount"

If it was mounted, you would have seen the files on it when you typed "ls -l /boot"

 

Joe L.

Joe,

 

Got it.

This is really strange. All I did was reset my BIOS to the original settings and then back to custom and use a second USB drive, 4GB Gizmo. The system now seems to work. I tried back the original Cruzer USB drive and still no go. By the way, when I try to record master boot record (c:\syslinux.exe -ma s:) I get an error message:

 

Accessing physical drive: Access is denied.

Did not successfully update the MBR. continuing...

 

That happened to both drives. However, the Gizmo is working OK for now. I am starting the array even as I type... I am not sure as to why the other drive would not work now, even though it has been working flawlessly up to this, and what resetting the BIOS had to do. I am pretty comfortable with BIOS and know my way around it to know what I did...

 

Thanks for the help.

 

Lev

 

This is really strange. All I did was reset my BIOS to the original settings and then back to custom and use a second USB drive, 4GB Gizmo. The system now seems to work. I tried back the original Cruzer USB drive and still no go. By the way, when I try to record master boot record (c:\syslinux.exe -ma s:) I get an error message:

 

Accessing physical drive: Access is denied.

Did not successfully update the MBR. continuing...

 

That happened to both drives. However, the Gizmo is working OK for now. I am starting the array even as I type... I am not sure as to why the other drive would not work now, even though it has been working flawlessly up to this, and what resetting the BIOS had to do. I am pretty comfortable with BIOS and know my way around it to know what I did...

 

Thanks for the help.

 

Lev

 

Does your USB drive show up as drive "s" on your PC?  That might be the whole issue.  Usually, it will be drive "d" or "e" or something like that.  It sounds like you never made the original flash drives bootable because you did not give the correct drive letter corresponding to the USB flash drive.

 

Joe L.

This is really strange. All I did was reset my BIOS to the original settings and then back to custom and use a second USB drive, 4GB Gizmo. The system now seems to work. I tried back the original Cruzer USB drive and still no go. By the way, when I try to record master boot record (c:\syslinux.exe -ma s:) I get an error message:

 

Accessing physical drive: Access is denied.

Did not successfully update the MBR. continuing...

 

That happened to both drives. However, the Gizmo is working OK for now. I am starting the array even as I type... I am not sure as to why the other drive would not work now, even though it has been working flawlessly up to this, and what resetting the BIOS had to do. I am pretty comfortable with BIOS and know my way around it to know what I did...

 

Thanks for the help.

 

Lev

 

Does your USB drive show up as drive "s" on your PC?  That might be the whole issue.  Usually, it will be drive "d" or "e" or something like that.  It sounds like you never made the original flash drives bootable because you did not give the correct drive letter corresponding to the USB flash drive.

 

Joe L.

 

The PC that I used for the formatting of the USB drives is my current media server and hence has many drives as well as networked drives in other PCs using up the drive letters. Therefore, when I plugged in the flash drive to be formatted it got assigned a letter, in this case S as the others were already taken.

The PC that I used for the formatting of the USB drives is my current media server and hence has many drives as well as networked drives in other PCs using up the drive letters. Therefore, when I plugged in the flash drive to be formatted it got assigned a letter, in this case S as the others were already taken.

Ok, you are on the ball as far as getting the right drive letter... glad you are up and running.

 

Joe L.

This is really strange. All I did was reset my BIOS to the original settings and then back to custom and use a second USB drive, 4GB Gizmo. The system now seems to work. I tried back the original Cruzer USB drive and still no go. By the way, when I try to record master boot record (c:\syslinux.exe -ma s:) I get an error message:

 

Accessing physical drive: Access is denied.

Did not successfully update the MBR. continuing...

 

That happened to both drives. However, the Gizmo is working OK for now. I am starting the array even as I type... I am not sure as to why the other drive would not work now, even though it has been working flawlessly up to this, and what resetting the BIOS had to do. I am pretty comfortable with BIOS and know my way around it to know what I did...

 

Thanks for the help.

 

Lev

 

 

For future reference, that error message sounds very familiar to what you would encounter if you run syslinux.exe from a default Vista installation or while running under a restricted user.  If you right-click the "Command Prompt" icon from your "Accessories" folder then left click "Run as administrator" then insert the syslinux command most likely it will complete successfully (barring no interference from peculiar group policies, registry settings, or permissions beyond the normal OS install).

This is really strange. All I did was reset my BIOS to the original settings and then back to custom and use a second USB drive, 4GB Gizmo. The system now seems to work. I tried back the original Cruzer USB drive and still no go. By the way, when I try to record master boot record (c:\syslinux.exe -ma s:) I get an error message:

 

Accessing physical drive: Access is denied.

Did not successfully update the MBR. continuing...

 

That happened to both drives. However, the Gizmo is working OK for now. I am starting the array even as I type... I am not sure as to why the other drive would not work now, even though it has been working flawlessly up to this, and what resetting the BIOS had to do. I am pretty comfortable with BIOS and know my way around it to know what I did...

 

Thanks for the help.

 

Lev

 

 

For future reference, that error message sounds very familiar to what you would encounter if you run syslinux.exe from a default Vista installation or while running under a restricted user.  If you right-click the "Command Prompt" icon from your "Accessories" folder then left click "Run as administrator" then insert the syslinux command most likely it will complete successfully (barring no interference from peculiar group policies, registry settings, or permissions beyond the normal OS install).

 

Very interesting... I will try this later on today. I did not think of running command prompt as an Admin. Vista strikes again... I'll try this with another USB key and report later... Thanks!