Hi Tim,

> > After attempting to mount it, have a look at the end of dmesg(1)'s
> > output for any information from the kernel filesystem modules about
> > what they did or didn't like.
>
> Strangely my system does not have a dmesg log file, I had a good
> search (looked in the normal /var/log/ ) but there no log to be found

The `(1)' after `dmesg' means its man page is found in section 1 of the
manual.  It's a command, not a log file, though some distros may choose
to copy its output to a log file now and again.  Just run `dmesg'.

> > > 'sudo file -s /dev/sdd*' works here to tell me that I have an x86
> > > boot sector on /dev/sdd and an ext4 filesystem on /dev/sdd1.
> > > Adding '-k' shows more information.
...
> I moved onto the sudo hexdump, this dumped a load of gibberish where
> 95% of the readable text in the right hand column was just random,

If it really was random then that suggests compression.  Did you try the
file(1) command Andrew suggested?  Do you recognise the boot loader when
it's booting?
https://en.wikipedia.org/wiki/Master_boot_record#Sector_layout describes
how the machine code is located within the first sector of the disk, and
probably later stages before the start of that partition.

> *The reason I am doing this is that these terminal are Linux based and
> they have a built in RDP client, I am having issue with running RDP on
> my PC so I was hoping to glean some info from one of these terminals.

Seems a long shot.  :-)  Doesn't mean it's not an interesting way to
fill your time though.  Perhaps working out what goes wrong in the
network protocol, e.g. Wireshark, between your failing Linux RDP client
and the server would get closer to a solution;  you can look at a thin
terminal's traffic to see if you can spot the traffic for a similar
activity.

Cheers, Ralph.

--
Next meeting:  Bournemouth, Tuesday, 2015-04-07 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
New thread:  mailto:[email protected] / CHECK IF YOU'RE REPLYING
Reporting bugs well:  http://goo.gl/4Xue     / TO THE LIST OR THE AUTHOR

Reply via email to