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.

Newbie with prebuilt needs help - new system not working

Featured Replies

Hi everyone,

 

Not sure where this post belongs, so I'm trying it here.

 

This morning I picked up my prebuilt MD1500-LL.  I followed the instructions - loaded the drives, powered up and that was as far as I got.  The \\tower never showed up in my network places so I'm trying to figure out what's going on.  The tower reports that "mount: special device /dev/disk/by-label/UNRAID does not exist".  I wondered if there was something wrong with the USB so I opened up the case, switched it with the spare and restarted the tower.  This time I watched the bootup - there was a lot of messages that I don't understand and kind of went too fast to read but the end result was the same.  So I've switched the USB and am ready to start again.

 

I would really appreciate it if someone could guide me through this process.  I know nothing about linux but am happy to follow instructions and report back.

 

Any assistance would be greatly appreciated.

 

Thanks,

 

Mark

  • Author

Hello,

 

Here is some more data of what I see when I restart the machine

 

- seems to find the 5 drives

- scans for devices

- messages that BIOS disabled and then that BIOS not installed

- next a screen comes up which has Unraid OS highlighted and a bunch of stuff happens (looks like it's "installing" unraid?)

 

For several cycles I get messages about Sata13 link slow to respond with the following associated messages

- SRST failed (errno=16)

- link online but misclassified

-sata13.DO failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask = 0x80)

 

Next, a bunch of messages then these error messages

 

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

- chmod: dev/console: no such file or directory

 

Finally get to a prompt

 

- Welcome to Linux 2.6.27.7-unRAID (tty1)

 

Would certainly welcome any suggestions on what to do next.  I'm not a technophobe and can certainly run some diagnostic commands to try to figure out what's going on where - just need a little direction..

 

I assumed that everything would be configured right out of the box as it's a pre-built machine direct from Tom.

 

TIA

  • Author

I tried to follow some advice from another thread and ran the following commands:

 

"ls -l /dev/disk/by-label"

1 root root UNRAID

 

"ls -l /dev/disk/by-id"

4 of my 5 drives are listed twice each (once ata once scsi) - not sure what happened to the 5th drive

usb is listed twice as sda and sda1

 

"mount"

 

fusect1 on /sys/fs/fuse/connections type fusect1 (rw)

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

 

"ls /boot"

no response

 

Thanks for any help or direction...

I tried to follow some advice from another thread and ran the following commands:

 

"ls -l /dev/disk/by-label"

1 root root UNRAID

 

"ls -l /dev/disk/by-id"

4 of my 5 drives are listed twice each (once ata once scsi) - not sure what happened to the 5th drive

usb is listed twice as sda and sda1

 

"mount"

 

fusect1 on /sys/fs/fuse/connections type fusect1 (rw)

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

 

"ls /boot"

no response

 

Thanks for any help or direction...

Did you load the USB drive? Or was it supplied by Tom at Lime-Technology?

 

The usual cause of this is a missing volume label of "UNRAID" (exactly six capital letters) on the flash drive. 

It has happened where some flash drives are not recognized by the software in time to view their label.  Some never show their label, even when visible under windows.

 

Assuming that sda is your flash drive, what do you get by typing

vol_id /dev/sda1

(note... that is sda1 ... with a "1" at the end, signifying the first partition on the drive)

 

You should see the "UNRAID" label.

 

If you do see the correct volume label, You can try typing

/sbin/udevtrigger

and see if the entry for it is created  in the /dev/disk/by-label directory.

 

If they are, perhaps adding that command to the top of the "config/go" script might work for you.

 

As an alternative, you could add a line like this to make the expected entry, but I've never tried this to see if if would get removed by the "udev" processing when it next runs.

ln -s /dev/sda1 /dev/disk/by-label/UNRAID

 

Joe L.

  • Author

Thanks for the reply Joe!

 

The USB was loaded by Tom at Lime-Technology

 

I tried the vol_id /dev/sda1 and I do see the UNRAID label

 

I typed /sbin/udevtrigger and got the following message: "-bash: /sbin/udevtrigger: no such file or Directory"

 

I don't really know how to add anything to the config/go statement

 

edit: When I tried this ln -s /dev/sda1 /dev/disk/by-label/UNRAID I got the message

"ln: creating symbolic link '/dev/disk/by-label/UNRAID': file exists

 

Any further insight and advice is greatly appreciated.

 

edited to remove my unreasonable comments

 

Hopefully we can get this figured out - thanks for your help.

Thanks for the reply Joe!

 

The USB was loaded by Tom at Lime-Technology

 

I tried the vol_id /dev/sda1 and I do see the UNRAID label

 

I typed /sbin/udevtrigger and got the following message: "-bash: /sbin/udevtrigger: no such file or Directory"

 

I don't really know how to add anything to the config/go statement

 

edit: When I tried this ln -s /dev/sda1 /dev/disk/by-label/UNRAID I got the message

"ln: creating symbolic link '/dev/disk/by-label/UNRAID': file exists

 

Any further insight and advice is greatly appreciated.

 

I really thought that when buying a pre-built server that it would have been fully tested to ensure that everything was working properly.  Hopefully we can get this figured out - thanks for your help.

I apologize, I did not read your prior response correctly.  I now see where you said you did see the UNRAID volume label.  I was misled when you described the error:

"mount: special device dev/disk/by-label/UNRAID does not exist.  Apparently, at the time it was looked for, it did not exist. (and it does now, as you were told it already exists when you attempted to create it)

 

Based on the fact that Tom supplied the complete pre-built system, the most likely is that something is not plugged in firmly or got dis-lodged in shipping.

Power down,  Un-plug from the AC wall outlet, then try re-seating the interface boards and SATA connectors.  The SATA connectors are easy to come loose, as many do not have a locking mechanism. 

 

Other than that...  An e-mail to Tom @ lime-tech pointing to this thread might help.  Apparently the UNRAID label was not present when it was looked for earlier (and the cause of your initial error message) and if it cannot be located, then the flash drive is not mounted, and unRAID software on it not run, and you are where you are now...  If it is present now (and apparently it is), you might be booting faster than expected (or more likely, slower, based on the SATA time-outs you described) 

 

Did Tom supply the disk drives?  Or did you install them?  (Are they Seagate 1.5TB drives? They have timeout issues of their own corrected by a firmware update)

 

We would be able to learn more of we could see a copy of the system log....  It is difficult though, as you have no easy way to get us a copy when the system not properly mounting the flash drive.

You could try:

mount -t vfat -w /dev/sda1 /boot

followed by

/etc/rc.d/rc.local

(to start unRAID manually now that the /boot/config hierarchy exists)

 

Then see if you have connectivity...

ls -l /boot will show files if it does.

Then

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

will make a copy on the flash drive you can subsequently upload for analysis as described here in the wiki: http://lime-technology.com/wiki/index.php?title=Troubleshooting

 

Joe L.

  • Author

Thanks Joe

 

I opened it up and checked all the connections and everything seemed fine - tried rebooting and had the same issue.

 

This got me thinking - same issue at the same point with ata13 so I wondered if there was a problem with the drive.  Shut it down and removed the drive (brand new WD 1TB) and rebooted - this time it's up and running.  Not sure now if it's the drive or the connector, but can figure that out later.

 

My issue now is that I don't see tower showing up in my network places.  It shows up in my browser when I enter http:\\tower or also via the ip address.  Any suggestions as to how to get it showing up in my network places?

 

Thanks again!!

My issue now is that I don't see tower showing up in my network places.  It shows up in my browser when I enter http:\\tower or also via the ip address.  Any suggestions as to how to get it showing up in my network places?

Do you have the "workgroup" set to the same one as your PC?  If not, that is where I would start.

 

Joe L.

  • Author

Thanks Joe - I did start there...

 

...and finished there!!  Problem solved.  Thanks for all your help - really appreciate it.

 

I've been lurking here for several months and knew this was a community I could count on for help.

 

 

- Welcome to Linux 2.6.27.7-unRAID (tty1)

 

I was intrigued by this line!  Would you mind posting a copy of your syslog?  See the Troubleshooting link in my sig for instructions.  Glad you are up and running.

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.