Categories
Tech

Avoid “S to Skip” Message Ubuntu

After following the steps in my XBMC Live Drives Mounted as Odd IDs article, wherein the user modifies the label of the drive and sets it to be recognized as part of the fstab process, I found myself occasionally seeing the message that indicates that Ubuntu can’t find the drive. I found it frustrating that I would occasionally reboot my XBMC setup and the Seagate USB harddrives would have issues until I power cycled them.

With a bit of quick research, I found that there is an option as part of the fstab setup called nobootwait which lets the operating system continue to boot up even if the drive isn’t present. In order to add this option, take the following steps.

Open the fstab file in your favorite editor:

sudo nano /etc/fstab

Modify the line for your hard drive to add the nobootwait parameter:

UUID=1234-5678           /media/SeagateHDD              ntfs-3g defaults,umask=002,gid=users,nobootwait               0 0

That’s all it should take. Next time you reboot, the system should skip past the waiting screen (“S to Skip”).

Categories
Tech

Set XBMC to Automount Drives

Whenever I install XBMC, one of the first settings I change is I enable auto mounting of drives. It’s a relatively simple change, but requires you modify a file on the filesystem.

For Ubuntu Lucid 10.04:

I’ve noticed that it’s not necessary to manually remove the nodiskmount option on 10.04 (grub2). The modifications that I used to make in /boot/grub/menu.lst on Ubuntu Karmic, I now have to make in /etc/default/grub on Ubuntu Lucid.. When I removed the nodiskmount on Ubuntu Lucid I started having some issues with the disks being mounted in odd ways (eg. my NTFS drive being mounted directly to /media). What I found is that instead of removing nodiskmount, if I just properly labeled my partitions, they would automatically show up properly — you can label your partitions using the e2label command.

As I noted in the comments below, you may still need to remove nodiskmount in Ubuntu Lucid to get your eSATA drive to mount (especially true for people who followed my Revo 1600 guide). What I found is that because the internal drive on the Revo 1600 is NTFS, it will cause the weird issues I mentioned above. If you happen to fall into this case, I would highly recommend you check out my article on Drives Being Mounted with Odd IDs. The article explains how to find the unique identifier (UUID) for your drive and manually create an FSTAB entry to mount your drive with your specifications each time the system loads. Now that I’ve wrapped my head around how FSTAB works, I prefer to use this method as it lets me set my own unique name, path, and other settings for how the drive is mounted.

However, if you’d still like to modify the grub parameters for other reasons, I’ve included the details below…

Open the file /etc/default/grub:

sudo nano /etc/default/grub

Find the line for loading your system (usually starts with GRUB_CMDLINE_LINUXDEFAULT) and make sure it’s not the commented out line that often comes default at the top of the file. Modify this line so it no longer has the nodiskmount option in it.

Save the file and close it. Ctrl+O, Enter, Ctrl+X.

Run the following line to update grub and then reboot:

sudo update-grub sudo reboot

For Ubuntu Karmic:

If you are still booting from the XBMC-Live 9.11 Camelot USB stick directly, this will be in the syslinux.cfg file. If you have installed XBMC to disk, this is in the /boot/grub/menu.lst file. 

To remove this flag from the menu.lst file, telnet into the XBMC machine (use the instructions from the sabnzbd install post if you don’t know how), then open up the file with your favorite editor:

sudo nano /boot/grub/menu.lst (you may have to enter your root username and password — typically xbmc / xbmc)

Arrow down to the first line under “## ## End Default Options ##” near the bottom of the file and on the “kernel” line arrow to the right until you see the “nodiskmount” text. Delete this text then press Ctrl+O [enter] to save the file then Ctrl+X to exit. Reboot your box and you should now see some new items in your file manager usually named something like sdb1 or sda1.

Categories
Tech

Setup Samba/Windows Shares on XBMC Live

It’s relatively easy to setup samba shares on XBMC Live, but it does require bashing out some commands on the shell. First, you’ll need to install samba using apt-get:

sudo apt-get update sudo apt-get install samba

Then, you’ll want to configure your shares by editing the the file named smb.conf, placed in the /etc/samba/ directory. For example, I added the user folder and media folders to be available shares by running the following command:

sudo nano /etc/samba/smb.conf

Scroll down all the way to the bottom of the file, then paste in the following (use right click in Putty to paste something from your clipboard):

[xbmc]  path = /home/xbmc  public = yes  guest only = yes  writable = yes  browseable = yes  force user = xbmc  inherit permissions = yes  [media]  path = /media  public = yes  guest only = yes  writable = yes  browseable = yes  force user = xbmc  inherit permissions = yes

After that, restart the samba server using:

sudo /etc/init.d/samba restart

Update: It looks like this has changed in the more recent versions of Ubuntu that the XBMC Live distribution is packaged with (10.04). You can restart the samba service using the old method:

sudo service smbd restart sudo service nmbd restart

Note: I updated the samba configuration above to include the ‘force user’ and ‘inherit permissions’ features as I was having trouble with newly created files not getting the right permissions and logging into samba.

Also, when accessing the shares from Windows, if you left the default security options you can use the account ‘guest’ with no password to access the shares. Otherwise, you can play with the settings to force a local linux account to be used in order to access the shares.