Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Flash not recognized

Featured Replies

I am having a problem very similar to this with 4.2.1.

 

I have had a working system for over a year and all of a sudden my tower will not connect to my network. I restarted the machine just for the heck of it because it had been running for a few months. When I turned it back on, it started up just fine but it will not connect to my DHCP network.

 

I've verified my network.cfg and it is set to use DHCP and I have verified the netmask and gateway. My results from "ifconfig eth0" look very similar to the first post with the missing IP address.

 

I also tried to do the following command cp  /var/log/syslog  /boot/config/syslog.txt but it returns cp: cannot create regular file '/boot/config//syslog.txt' : No such file or directory

 

The last 2 lines before I get to the Tower login are

 

/ect/rc.d/rc/inet1.conf: line 19 /boot/config/network.cfg: No such file or directory

/ect/rc.d/rc/inet1.conf: line 19 /var/tmp/network.cfg: No such file or directory

 

Anyone have any ideas? Ive been at this all day, upgraded my motherboard's (asus p5pe-vm) bios also!

 

  • Author

I have bought the Netgear GA311 thinking that my onboard LAN was dead. This card, which is supposed to work with Unraid, is still rendering me the same problems as described above.

 

At this point I am very worried that I might lose my family photos and everything else I have cataloged on the server. Help please!?

It sounds as if your flash drive is not being mounted at /boot.

 

Type

ls -l /boot

 

It should have the contents of the flash drive.  If not, then that is why your network is not accessible.  It can get to the config files it needs on the flash drive.

 

Many times, this is the result of not having se the volume label on the flash drive to "UNRIAD"  Could you have recently changed something on the flash drive?  Plug it into a windows box and look at its "properties"  Make sure the label says UNRAID

 

To view the syslog, you can type

more /var/log/syslog

 

each time you press the space bar you will see the next page.  Look for error messages and share what you are unsure of here.

 

Your pictures and data on the unRaid server are probably just fine...

 

Type

mount

 

To see if the disks were mounted on the mount points...

 

and type

smbstatus

 

To see your shared drives if it got that far.  All will be clues as to what is happening.

 

 

If the network driver was loaded, you can see it if you type:

lsmod

 

 

Joe L.

  • Author

Thank you for the reply Joe.

 

I tried ls -l /boot and got total 0 back.

 

Even after verifying that my flash drive is still set as "UNRAID" I see:

mount: special device /dev/disk/by-label/UNRAID does not exist

 

Here are the lines that caught my attention:

Cannot enable port 1. Maybe the USB cable is bad?

hub_port_status failed error -32

ehci_hcd 0000:00:1d.7: port 1 reset error -110

device not accepting address 107, error -71

 

mount followed by smbstatus gave me the following:

sessionid.tdb not initialised

/var/cache/sambe/connection.tdb not initialized

This is normal if an SMB client has never connected to your server.

Failed to open byte range locking database /car/cache/samba/brlock.tdb

ERROR: Failed to initialise locking database

Can't initialise locking module - exiting

 

lsmod gave me the following:

module                size        used by

ide_disk              13184    0

ata_piix              11140    0

libata                  98252    1 ata_piix

skge                  33172    0

pdc202xx_new  6272      0 [permanent]

r8169                22808    0

piix                    7940      0 [permanent]

ide_core            95748    3 ide_disk,pdc202xx_new,piix

 

The last time I had that problem was because I hadn't correctly set the name of the flash drive to UNRAID, but if you had been working for a while that probably isnt it...

 

  • Author

I just triple checked that it was set to UNRAID on my windows machine and it was set correctly. I did not unplug this when I restarted my machine so it should be the same install as when it was running smoothly!

OK... from the errors you posted it appears as if your motherboard is having a difficult time finding the device on the USB hub the flash drive is plugged into.

 

Now, obviously, it must be reading some of the flash drive, otherwise it would not be booting at all.    The main issue is that unRaid is unable to locate the drive with the UNRAID label to mount it at /boot. 

 

Perhaps Tom at lime-technology will have an idea or two...

 

Did you make any (hardware) changes since you last booted?  Changed any bios options?  Do you have any other USB devices plugged in that might be getting it confused?  Did you upgrade to a new version of unRaid?  (just trying to jog your memory... ;D)

 

Joe L.

  • Author

I have made no hardware changes besides adding the Netgear GA311, but I have also tried multiple times without it. No other USB devices are connected.

 

The bios changes I have made are small, just turned off the onboard nic.

 

I plugged in another USB hub to the onboard motherboard USB connections and still could not get anywhere.

Trying to see if the flash drive is being detected at all...

 

try the following three commands... 

ls -l /dev/disk/by-label

ls -l /dev/disk/by-path

ls -l /dev/disk/by-id

 

On my array, the ls -l /dev/disk/by-label returns this:

root@Tower:~# ls -l /dev/disk/by-label

total 0

lrwxrwxrwx 1 root root 10 Feb  5 02:40 UNRAID -> ../../sda1

  • Author

Here are the responses I received:

 

ls -l /dev/disk/by-label

no such file or directory

 

ls -l /dev/disk/by-path

da1

lrwxrwxrwx  root root  9 Feb 12 11:34 pci-0000:00:1f.1-ide-o:1 -> ../../hdb

lrwxrwxrwx  root root  10 Feb 12 11:34 pci-0000:00:1f.1-ide-o:1-part1  -> ../../hdb

 

db1

lrwxrwxrwx  root root  9 Feb 12 11:34 pci-0000:00:1f.1-ide-o:1 -> ../../hdb

lrwxrwxrwx  root root  10 Feb 12 11:34 pci-0000:00:1f.1-ide-o:1-part  -> ../../hdb

 

dc1

lrwxrwxrwx  root root  9 Feb 12 11:34 pci-0000:00:1f.1-ide-o:1 -> ../../hdb

lrwxrwxrwx  root root  10 Feb 12 11:34 pci-0000:00:1f.1-ide-o:1-part  -> ../../hdb

 

dd1

lrwxrwxrwx  root root  9 Feb 12 11:34 pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../sd

 

a

lrwxrwxrwx  root root  10 Feb 12 11:34 pci-0000:00:1f.2-scsi-0:0:0:0- part1  -> ../../sd

(followed be more of this b, de1...)

 

ls -l /dev/disk/by-id

../../hde1

lrwxrwxrwx 1 root root  9 feb 12 11:34 ata-Maxtor_6Y160p0_Y43XTA9E > ../../hdd

lrwxrwxrwx 1 root root 10 feb 12 11:34 ata-Maxtor_6Y160p0_Y43XTA9E-part1  > ../../hdd

./hdd1

lrwxrwxrwx 1 root root  9 feb 12 11:34 ata-Maxtor_6Y200p0_Y61YZZ6E > ../../hda

lrwxrwxrwx 1 root root 10 feb 12 11:34 ata-Maxtor_6Y200p0_Y61YZZ6E-part1 -> ../.

./hda1

lrwxrwxrwx 1 root root  9 feb 12 11:34 ata-Maxtor_6Y250P0_Y64TC8YE > ../../hdb

lrwxrwxrwx 1 root root 10 feb 12 11:34 ata-Maxtor_6Y250P0_Y64TC8YE-part1  > ../../hdb1

 

lrwxrwxrwx 1 root root  9 Feb 12 11:34 ata-ST3320620A_5QF1PGJH -> ../../hdb

lrwxrwxrwx 1 root root 10 Feb 12 11:34 ata-ST3320620A_5QF1PGJH-part1 -> ../../hdb1

lrwxrwxrwx 1 root root  9 Feb 12 11:34 ata-ST3500630A_9QG021Z0 -> ../../hdf

lrwxrwxrwx 1 root root 10 Feb 12 11:34 ata-ST3500630A_9QG021Z0-part1 -> ../../hdf1

lrwxrwxrwx 1 root root  9 Feb 12 11:34 scsi-SATA_Maxtor_7L300S0_L60LPVG -> ../../sdb

lrwxrwxrwx 1 root root 10 Feb 12 11:34 scsi-SATA_Maxtor_7L300S0_L60LPVG-part1 -> ../../sdb1

lrwxrwxrwx 1 root root  9 Feb 12 11:34 scsi-SATA_WDC_WD5000KS-00_WD-WMANU1102909 -> ../../sda

lrwxrwxrwx 1 root root  10 Feb 12 11:34 scsi-SATA_WDC_WD5000KS-00_WD-WMANU1102909-part1 -> ../../sda1

I was hoping the by-label entry was there... clearly, it is not.

 

So... now we know why unRaid can't find the entry with an UNRAID label, it was not created.  In fact, I don't see any evidence of any entries except those of your hard disks in the by-path or by-id listings.

 

Perhaps Tom will get an idea or two when he reads this...  We can search in google to see if it gives any advice if the entries are not created for the USB flash drive...

 

Joe L.

  • Author

I did a search on our forum and came up with this: http://lime-technology.com/forum/index.php?topic=1231.0

 

This was never a U3 USB drive and has always worked in the past but I'll be sure to give this a try when I get home.

  • Author

I tried the HP Flash Formatter and reran syslinux on the drive, downloaded a fresh copy of unRaid and put it on the drive.

 

I then put my disk.cfg and pro.key in the config folder.

 

I am still getting the 2 lines before Tower login:

 

/ect/rc.d/rc/inet1.conf: line 18 /boot/config/network.cfg: No such file or directory

/ect/rc.d/rc/inet1.conf: line 19 /var/tmp/network.cfg: No such file or directory

You did remember to set the label again to UNRAID as it would have been erased when you re-formatted and re-loaded everything.

 

The two messages are an indication that the flash drive did not get mounted at /boot.  Therefore, the files it was looking for were not there.  Assuming the label is set, we are still trying to figure out what is going on.

 

Joe L.

  • Author

I did made sure to set it to UNRAID. Just for grins I formatted another USB drive I had lying around and put a fresh copy of unraid on it without my key and custom disk.cfg. Unraid did boot up fine.

 

At this point I have to think that my USB connections and onboard NIC are fine because thats what I justed used to connect to http://tower using the 2nd USB drive.

 

I'm not quite understanding that because unraid starts just fine with my production USB drive, it just doesn't get mounted as /boot as you pointed out. Do I need to use a new USB drive?

interesting...

 

I suppose it could be something as simple as your original USB flash drive acting weird on you.

 

 

  • Author

Do you know if there is any sort of program to check the USB drive?

<Note: I split this conversation off to a new topic>

 

Looks like your Flash died somehow.  You can try to manually mount it like this:

 

From the console, type this:

 

cat /proc/partitions

 

In this output will be listed all your storage devices.  You want to look down the #blocks column to find one about the size of your Flash (note that the numbers there are in 1K units).  Usually easy to find because it will be much smaller than all the others.  Now look which name has been assigned (typically 'sda' and 'sda1', but could be different).

 

Let's assume it's 'sda' and 'sda1'.

 

You can manually mount the flash like this:

 

mount /dev/sda1 /boot

  Use the version of 'name' found above with the '1' in it.

 

If this does not produce any errors, then you should be able to copy the system log to the Flash:

 

cp /var/log/syslog /boot/syslog.txt

 

Now un-mount the Flash:

 

umount /boot 

  [note command name is 'umount', not 'unmount'  <-- original programmer being thrifty with letters :) ]

 

Now plug flash into your PC and post the system log.

  • Author

Thank you for the reply.

 

After typing in mount /dev/sdc1/boot I get the error: cant find dev/sda1/boot in /etc/fstab or /etc/mtab

 

Thank you for the reply.

 

After typing in mount /dev/sdc1/boot I get the error: cant find dev/sda1/boot in /etc/fstab or /etc/mtab

 

You missed a space in what you should be typing.

mount  /dev/sdc1  /boot

  • Author

Thank you for noticing that Joe. Turns out though, I had my wife doing this from home, she put in my newer flash drive.

 

I am home now and I put in the correct flash drive. After typing cat /proc/partitions I only see my hard drives, not the flash drive.

Well it looks like your Flash died.

 

If you have another Flash that seems to be recognized, then, after the system boots with ONLY your suspect Flash installed, then hot-plug your second flash.  Again type the 'cat /proc/partitions' command, this time it should recognize the Flash you just plugged in.  Proceed as indicated above to copy the syslog to the Flash you just plugged in.  What I want to see is the USB subsystem startup - it might be outputting error messages which would give a clue why your original Flash is no longer recognized.

Hi,

I had the same problem with a usb key and i changed the usb from v2 to v1 in the bios and it was much happier.

Cheers Dave

  • Author

Wow! Thank you, that did the trick!

 

I now have a smaller problem. When I started the server this time, the array did not start like it normally does.

 

It does see all my disks and they appear to be in the correct order. Do I want to start or restore?

 

Ive also attached the syslog!

These messages in your syslog seem to indicate the flash drive might still be giving you an issue or two.

 

You can try starting your array... if it lets you.  If not, a "restore" will do it.    It will probably do a full parity calculation.

 

Feb 13 18:24:09 Tower kernel: [  131.944660] read_file: error 2 opening /boot/config/super.dat

Feb 13 18:24:09 Tower kernel: [  131.944665] md: could not read superblock from /boot/config/super.dat

Feb 13 18:24:09 Tower kernel: [  131.944667] md: warning! initializing superblock

Feb 13 18:24:09 Tower kernel: [  131.945163] md0: new disk

Feb 13 18:24:09 Tower kernel: [  131.945313] md1: new disk

Feb 13 18:24:09 Tower kernel: [  131.945411] md2: new disk

Feb 13 18:24:09 Tower kernel: [  131.946398] md3: new disk

Feb 13 18:24:09 Tower kernel: [  131.946554] md4: new disk

Feb 13 18:24:09 Tower kernel: [  131.946689] md5: new disk

Feb 13 18:24:09 Tower kernel: [  131.946838] md6: new disk

Feb 13 18:24:09 Tower kernel: [  131.946971] md7: new disk

 

 

Archived

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.