[Durham] fstab and mounting drives at boot
andrewglass3 at gmail.com
Tue Aug 5 08:52:17 UTC 2014
Yes they are wonderful little boxes, mine is simply running as a samba server and VPN gateway box - it's brilliant.
I tried downloading the firmware upgrade as my warranty is brand new but when I ran the software to build the boot pen on my windows 8.1 box it had terrible trouble and never competed fully so I'm currently on a bios from 10/1/13 :(
Any ideas to solve this?
Sent from my iPhone
> On 5 Aug 2014, at 09:35, Richard Mortimer <richm at oldelvet.org.uk> wrote:
>> On 05/08/2014 08:02, Andrew Glass wrote:
>> Thanks for your help guys. I found out why the microserver does this,
> > it's due to the spare sata port and esata port being on a different
> > controller on the motherboard. There is a hacked bios that allows
> > the 5th sata port to be used at full speed and grouped together with
> > the other satas however I've just popped drives into the correct places
> > for now. May look at the hack in a few days when I'm off work.
> Unless I'm missing something you shoudn't need to use any hacked firmware. The UUID= fstab method is pretty much the norm these days (at least I think/thought it is). It works for the boot partition too so I don't think you need to worry about hacked firmware apart from speed issues.
>> Great little servers are these hp n54l microservers. Do any of you use them?
> Yes. Had one for a few years. Wonderful thing! A bit sluggish on the CPU front but it works fine with plenty of storage.
> P.S. Do be aware that HP changed their firmware patching policy about a year ago. You can now only download the firmware whilst you have a valid support contract or whilst the machine is under manufacturers warranty. Make sure you get any that you might need sooner rather than later.
>> Sent from my iPhone
>>>> On 4 Aug 2014, at 22:39, Dougie Nisbet <dougie at highmoor.co.uk> wrote:
>>>> On 04/08/14 22:23, Richard Mortimer wrote:
>>>> There are various techniques to work out what UUID is on each partition but assuming that you have the filesystems already mounted by /dev/xxx then look at what the /dev/disk/by-uuid link points to
>>> I think 'blkid' might help too. I've only recently started using this as it's particular useful when dealing with USB drives.
>>> Durham mailing list - Durham at mailman.lug.org.uk
>> Durham mailing list - Durham at mailman.lug.org.uk
> Durham mailing list - Durham at mailman.lug.org.uk
More information about the Durham