Raid automounted in XBMCBuntu, not XBMC
#1
Hi there,

I have an Intel fakeraid 5 array with 4x 2tb drives that only seems accessible
when I login to the XBMCBuntu session. If i logout and enter XBMC its still
accessible until I reboot. Aftercthat, only my ssd boot drive is available. i am
hoping to use the array for media only.

Do I just need to add it to etc/fstab? I have tried mapping /dev/mapper/longarrayname
to /media/raid in fstab but get a message when booting saying its not available, continue
or wait.

When booting directly into the XBMCBuntu session, even without the /etc/fstab mapping
entry, the array is there..

Any ideas guys?
Reply
#2
SMB or NFS?

I use unraid over SMB and have no problems. With SMB you don´t have to setup your fstab.
Reply
#3
how do I tell? i think i used a gnome disk utility to format it as an Ext4 partition..
Reply
#4
try adding in fstab
Reply
#5
Thanks for the suggestion, I have tried adding the following;

/dev/mapper/isw_cbcdgehihd_Storage2 /home/xbmc/media default 0 0

and

/dev/mapper/isw_cbcdgehihd_Storage2 /media/storage default 0 0
(after creating /media/storage/ using mkdir)

but it keeps coming up with an error message at boot time. I have also tried
using ext4 as a file system type but no luck.

Interestingly if I boot directly into XBMCBuntu its there under 6TB Storage in
the file manager.

Also, if I manually mount it using sudo mount /dev/mapper/isw_cbcdgehihd_Storage2 /home/xbmc/media
it mounts successfully. I do this via Putty remotely once the XBMC session is running.

Sorry guys, obviously Im a Linux newb and have no idea what Im doing so any help
appreciated..

I would ideally like the array to be automounted but would be quite happy autobooting into the XBMCBuntu
session and automatically starting XBMC under that if its the only way around it.

Please any help hugely appreciated!!!!! =)
Reply
#6
(2013-05-20, 11:23)mkleynhans Wrote: Thanks for the suggestion, I have tried adding the following;

/dev/mapper/isw_cbcdgehihd_Storage2 /home/xbmc/media default 0 0

and

/dev/mapper/isw_cbcdgehihd_Storage2 /media/storage default 0 0
(after creating /media/storage/ using mkdir)

but it keeps coming up with an error message at boot time. I have also tried
using ext4 as a file system type but no luck.

Interestingly if I boot directly into XBMCBuntu its there under 6TB Storage in
the file manager.

Also, if I manually mount it using sudo mount /dev/mapper/isw_cbcdgehihd_Storage2 /home/xbmc/media
it mounts successfully. I do this via Putty remotely once the XBMC session is running.

Sorry guys, obviously Im a Linux newb and have no idea what Im doing so any help
appreciated..

I would ideally like the array to be automounted but would be quite happy autobooting into the XBMCBuntu
session and automatically starting XBMC under that if its the only way around it.

Please any help hugely appreciated!!!!! =)

The fstab option is defaults, try that.
HTPC RPI3 Kodi 17 (Krypton) v8.0.1 MR
Storage BPI 1x 500GB SSD UPnP server
Display Sony Bravia 32"
Reply
#7
Sorry that was a typo it is defaults in fstab.

Unfortunately, it doesn't work.

If I allow the XBMC session to autologin and then access the box remotely via Putty and run

sudo mount /dev/mapper/isw_cbcdgehigd_Storage2 /home/xbmc/media, it mounts ok but if
its in the fstab as;
isw_cbcdgehihd_Storage2 /home/xbmc/media auto defaults 0 0

it comes up with an error message on the XBMC boot screen saying
'An error occurred while mounting /home/xbmc/media Press S to Skip of M to fix Manually..

It almost seems like when the etc/fstab is running, the raid array isn't ready yet...
Reply
#8
RIght, still the problem is fstab (I think) the format needs to be this:

<device> <mount-point> <fstype> <options> <dump> <pass>

With multiple arguments being comma separated.

Code:
/dev/mapper/isw_cbcdgehigd_Storage2 /home/xbmc/media ext4 defaults 0 0

I think auto is a default.

If that still doesn't work, please paste fstab here.
HTPC RPI3 Kodi 17 (Krypton) v8.0.1 MR
Storage BPI 1x 500GB SSD UPnP server
Display Sony Bravia 32"
Reply
#9
Another test to know if fstab is right, from a terminal type:

Code:
mount /home/xbmc/media

That'll read fstab for the details.
HTPC RPI3 Kodi 17 (Krypton) v8.0.1 MR
Storage BPI 1x 500GB SSD UPnP server
Display Sony Bravia 32"
Reply
#10
Hi again and thanks for your help on this.. Please see my /etc/fstab below...
Unfortunately the code below doesn't work but mounting manually works fine....

Code:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=f2a23721-0b54-4af3-b091-54028af1517a /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=4e439677-f932-4cb5-9656-994e2fb857ee none            swap    sw                0       0
isw_cbcdgehihd_Storage2 /home/xbmc/media ext4 defaults 0 0
Reply
#11
Thanks, still fstab Wink

Your device needs to use an absolute path, so change the last line to this:

Code:
/dev/mapper/isw_cbcdgehigd_Storage2 /home/xbmc/media ext4 defaults 0 0

Mounting manually will work because your specifying the full device path and mount point, as you demonstrated above:

Code:
sudo mount /dev/mapper/isw_cbcdgehihd_Storage2 /home/xbmc/media

But, if that is your fstab I bet sudo mount /home/xbmc/media does not.
HTPC RPI3 Kodi 17 (Krypton) v8.0.1 MR
Storage BPI 1x 500GB SSD UPnP server
Display Sony Bravia 32"
Reply
#12
undefined
Reply
#13
(2013-05-20, 13:30)mkleynhans Wrote: undefined

Pardon? Smile
HTPC RPI3 Kodi 17 (Krypton) v8.0.1 MR
Storage BPI 1x 500GB SSD UPnP server
Display Sony Bravia 32"
Reply
#14
Lol sorry about that , i have no idea wht happened there. Thanks for all the help, i got it working by using the UUID entry in fstab and it rebooted without any errors. Happy days : )
Reply

Logout Mark Read Team Forum Stats Members Help
Raid automounted in XBMCBuntu, not XBMC0