Re: [Dorset] How do I find out the file system type?

2015-03-11 Thread Tim

On 10/03/15 13:37, Ralph Corderoy wrote:

Hi Tim,

Andrew wrote:

Tim wrote:

Number  Start  End Size  Type File system  Flags
   1 32.3kB  1021MB  1021MB  primary boot

You can avoid those awkward units, by getting it in bytes, with

 sudo parted /dev/sdd unit B print

That then gives you a precise position and size should you need it.


If I plug it into my Debian box, it does not mount

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.


'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.

Also, look at its bytes, e.g. the first 16KiB with

 sudo hexdump -Cn $((1024 * 16)) /dev/sdd1 | less

You might find it's a compressed file, inflated into the terminal's RAM
on boot, where it's only then a filesystem image.

Cheers, Ralph.

--
Next meeting:  Bournemouth, Tuesday, 2015-04-07 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
New thread:  mailto:dorset@mailman.lug.org.uk / Check if you're replying
Reporting bugs well:  http://goo.gl/4Xue / to the list or the author


Thanks for the help Ralph

I think you suggestion it could be a compressed archived might be right 
there something in the depth of my mind that telling me I read something 
about booting from a compressed file.


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, so that 
on my I need to look at that later list.


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, there was 
some readable stuff at the end but this was related to missing file 
systems, (type of stuff that appears on screen when there is an error 
booting).


It was around this time I had a eureka moment, I remember I had buried 
on my desk some where a thinclient converter USB stick (plug it into an 
old PC and boot from it and it converts the PC to a thin client), a 
little investigation showed that there was an iso image on the usb stick 
which after a bit more investigation allowed me to to see the program 
that makes up the install. The only program that stood out was *os.rrdp 
(the format was os.sane, os.scim). Unfortunately I have not been able to 
find out much more an a quick google does not throw up any info.


*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.


Time to call an end of proceeding for tonight, will start again another 
night.


Tim

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


Re: [Dorset] How do I find out the file system type?

2015-03-11 Thread John Carlyle-Clarke
I find newer Windows systems will only work with xfreerdp instead of the
rdesktop ( http://www.rdesktop.org/ ) program I've always used, unless you
specifically modify their security settings.

On 11 March 2015 at 15:13, Andrew zil...@ziltro.com wrote:

 On 10/03/2015 22:29, Tim wrote:

 *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.


 In case it is relevant, I have been using Remmina for RDP for quite a
 while now. At some point, something changed and now I find I have to set
 Security to RDP, rather than Negotiate in order for it to work.

 --

 Andrew.




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

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


Re: [Dorset] How do I find out the file system type?

2015-03-11 Thread Ralph Corderoy
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:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING
Reporting bugs well:  http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR