Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.


Messages - Rich J

Pages: [1] 2 3 ... 26
1
General Help & Advice / Re: Speed up Boot
« on: November 16, 2017, 01:37:15 pm »
You're probably now using grub from the M17 drive .. in other words, the first boot device has changed in the BIOS.

Yes, you're correct!  I checked in the BIOS and indeed, M17 on sda is now 1st drive listed but how it did so is still a mystery as it wouldn't boot into anything beyond the options screen until I re-connected all the bits.............  Computers, eh?   ;D

Not to worry, all ok for the moment!!

Rich

2
General Discussion / Re: Email Clients are they free
« on: November 14, 2017, 03:07:04 pm »
If you don't mind Google then Gmail is very good.  Free, with very good spam filters and works fine with Thunderbird.  Also can be used across several platforms - smartphones etc.  Set up a Google account then simply email everyone in your address book (that you wish to know the new address) and you're up and running.  You can take it wherever you want as you're not tied to a particular provider, as is the case with your friend.  By the way, AOL is the service provider that 'owns' the email address - Thunderbird is the open-source (Mozilla) client that allows you to read and write and send/receive the mails.

I've used Gmail for years without any issues.  ;)

Hope this helps
Rich

 

3
General Help & Advice / Re: Speed up Boot
« on: November 14, 2017, 11:39:15 am »
Hi Mark and thanks for the explanation - very clear.

Things are now getting a bit weird..........

To test sdb boot speed I did this -

Disconnected all cables
Changed sdb jumper from 'slave' to 'master'
Reconnected cables to sdb
Restarted and system hung at the options screen - press Del, Esc, Tab etc.  Pressing any key did nothing.
Swapped connectors on data ribbon (tried both centre and end).  No different, same as above.
Connected cables to DVD and got a little further.  Past the options screen but now hanging on 'no device found'
Changed sdb jumper back to 'slave'
Reconnected sda cables and booted.
Back to Grub screen listing both distro's as before (and they both boot successfully) but, and this is the weird bit, the Grub list has now reversed it's order........ ???

After I'd originally got M18 on to sdb, I wasn't sure which distro was the right one to use to update Grub, so I used M18 (as the last one installed) and everything went ok.  Grub listed M18 first, then M17 - which is what I'd expected.  Now, after trying out the above, M17 is listed first, then M18 but at no time have I updated Grub! Very odd!

I wonder if the problem with running sdb independently of sda may be due to the way I set things up and I possibly missed a step?  Basically, I just popped the drive in, set the jumper and cables and the used GParted to partition the drive before installing M18.  Or perhaps is just a peculiarity of this motherboard?

Anyway, nothing lost - both distro's boot ok (he says, fingers crossed!) but M18 is still a bit on the slow side in firing up.  Once up though, it runs fine.  The reason for all this rigmarole is I wanted to fully test M18 64bit independently of M17 without the danger of screwing up.  It seems fine so far so I'll do a clean install of M18 on the larger Hdd and use the smaller one for data storage - but that's for another time!

Thanks again for your help.

Rich



4
General Help & Advice / Re: Speed up Boot
« on: November 11, 2017, 05:21:00 pm »
I don't know if it'll help, but I guess it can't hurt to try.

As you installed Mint 18 whilst it was the only drive in the PC it should have it's own GRUB stage 1 in its master boot record .. how quickly does the PC boot if you disconnect the Mint 17 drive and the DVD and set the jumper on the Mint18 drive to master.
(so it's the only drive attached)

Is it still slow ?

Ok, I'll give that a try but it might be a day or 3 before I get back to you. 

Regarding the set-up as per the fdisk -l data  -

Before installation of M18,  I set up sdb partitions exactly the same as sda was with M17, following your instructions. (I'd had issues with the boot files not being found - possibly due to the motherboard specs or file sizes?)  Anyway, I let the installer do its job and all seemed to go exactly the same as with M17.  But - the boot files are in a different place in M18?  sdb5 in M18 yet sda1 in M17............  Could that be a factor?  And does it matter?  I would expect the installer to put the boot files on the 1st partition also.


5
General Help & Advice / Re: Speed up Boot
« on: November 11, 2017, 02:42:35 pm »
SCSI Disks - both ATA  -  same ribbon  -  sda on end connector  -  sdb on centre connector  -  DVD ATAPI on separate (SATA?) cable via adaptor

From memory, I ended up with this config as there were problems with the disks being 'seen' when connected differently (master/slave etc).  I needed an adaptor for the DVD as there is only 1 IDE connector on this motherboard.  All 3 devices are IDE connected. 

I could try changing the connections around if you think this would help?

'EH' - error handler, possibly?

Hope this helps

Rich






6
General Help & Advice / Re: Speed up Boot
« on: November 11, 2017, 08:32:24 am »
In Mint 18 can you run:
Code: [Select]
dmesg > ~/Desktop/dmesg.txt
you'll then find a file on your desktop called "dmesg.txt" .. can you host that file online somewhere and provide a link to it.

[EDIT]

Here's a free file hosting service
http://www.tinyupload.com/


As requested -

http://s000.tinyupload.com/?file_id=94794851481583555645

7
General Help & Advice / Re: Speed up Boot
« on: November 10, 2017, 02:39:15 pm »
Can you post the output from:
Code: [Select]
sudo fdisk -l

Hi Mark - as requested

~ $ sudo fdisk -l
[sudo] password for richard:
Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0001ba51

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048    980991    978944   478M 83 Linux
/dev/sda2          983038 312580095 311597058 148.6G  5 Extended
/dev/sda5          983040 152638097 151655058  72.3G 83 Linux
/dev/sda6       304693248 312580095   7886848   3.8G 82 Linux swap / Solaris


Disk /dev/sdb: 37.3 GiB, 40020664320 bytes, 78165360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7ad54111

Device     Boot    Start      End  Sectors  Size Id Type
/dev/sdb1           2048   976895   974848  476M 83 Linux
/dev/sdb2         978942 78163967 77185026 36.8G  5 Extended
/dev/sdb5  *      978944 70352895 69373952 33.1G 83 Linux
/dev/sdb6       70354944 78163967  7809024  3.7G 82 Linux swap / Solaris


8
General Help & Advice / Re: Speed up Boot
« on: November 10, 2017, 11:15:00 am »
Hi SeZo - thanks for the reply.

sudo e2fsck -C0 -p -f -v /dev/sdb5  returns -

461757 inodes used (21.27%, out of 2170880)
         594 non-contiguous files (0.1%)
         435 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 404389/83
     3344862 blocks used (38.57%, out of 8671744)
           0 bad blocks
           1 large file

      342488 regular files
       59172 directories
          56 character device files
          25 block device files
           0 fifos
          29 links
       60006 symbolic links (57195 fast symbolic links)
           1 socket
------------
      461777 files

sudo hdparm -tT /dev/sdb  returns -

/dev/sdb:
 Timing cached reads:   1704 MB in  2.00 seconds = 851.98 MB/sec
 Timing buffered disk reads: 110 MB in  3.00 seconds =  36.64 MB/sec

sudo hdparm -tT /dev/sda  returns -

/dev/sda:
 Timing cached reads:   1628 MB in  2.00 seconds = 813.43 MB/sec
 Timing buffered disk reads: 184 MB in  3.02 seconds =  60.83 MB/sec

I can't see any particular issues there but I'm not experienced in analysing this kind of data!  Any ideas your end?



9
General Help & Advice / Re: Speed up Boot
« on: November 10, 2017, 10:00:13 am »
Hi - I'm still struggling with improving the boot times of Mint 18.2.  Blame gives this (just the main culprits)

22.102s dev-sdb5.device
         19.344s ufw.service
         18.402s systemd-tmpfiles-setup-dev.service
         16.550s systemd-sysctl.service
         12.252s apt-daily-upgrade.service
          6.818s udisks2.service
          6.645s preload.service
          4.235s NetworkManager.service
          2.862s iio-sensor-proxy.service
          2.752s keyboard-setup.service
          2.453s systemd-modules-load.service
          2.318s thermald.service
          2.154s upower.service
          2.012s grub-common.service
          1.788s loadcpufreq.service
          1.760s systemd-journald.service
          1.668s colord.service
          1.484s systemd-fsck@dev-disk-by\x2duuid-e5fdbb08\x2d9250\x2d489a\x2d9e9a\x2dd83de51b2f45.service
          1.466s networking.service
          1.241s irqbalance.service
          1.187s sys-kernel-debug.mount
          1.185s dev-mqueue.mount
          1.070s binfmt-support.service
          1.070s dev-hugepages.mount
          1.063s console-setup.service
          1.019s polkitd.service


Further investigations have indicated possible errors in fstab and I wonder if these can be corrected?

# /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/sda5 during installation
UUID=b5f3259f-385a-4768-b6de-a27a60a03468 /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda1 during installation
#UUID=e5fdbb08-9250-489a-9e9a-d83de51b2f45 /boot           ext4    defaults        0       2
# swap was on /dev/sda6 during installation
UUID=7878d4b2-294f-4d21-974c-7929419f617a none            swap    sw              0       0
# Move /tmp to RAM
tmpfs /tmp tmpfs defaults,noexec,nosuid 0 0
UUID=e5fdbb08-9250-489a-9e9a-d83de51b2f45   /boot   ext4   defaults   0   2

Whereas lsblk -f shows -

NAME   FSTYPE LABEL UUID                                 MOUNTPOINT
sdb                                                     
??sdb5 ext4         b5f3259f-385a-4768-b6de-a27a60a03468 /
??sdb1 ext4         e5fdbb08-9250-489a-9e9a-d83de51b2f45 /boot
??sdb6 swap         7878d4b2-294f-4d21-974c-7929419f617a [SWAP]
sr0                                                     
sda                                                     
??sda2                                                   
??sda5 ext4         fd7a3f3e-5d95-48cb-ab1b-0a7415cfd185
??sda1 ext4         bd41cb59-1633-4957-8b92-e85530ad0662
??sda6 swap         eed0839a-eded-443d-91b6-f1c239008fe0

And blkid shows -

/dev/sda1: UUID="bd41cb59-1633-4957-8b92-e85530ad0662" TYPE="ext4" PARTUUID="0001ba51-01"
/dev/sda5: UUID="fd7a3f3e-5d95-48cb-ab1b-0a7415cfd185" TYPE="ext4" PARTUUID="0001ba51-05"
/dev/sda6: UUID="eed0839a-eded-443d-91b6-f1c239008fe0" TYPE="swap" PARTUUID="0001ba51-06"
/dev/sdb1: UUID="e5fdbb08-9250-489a-9e9a-d83de51b2f45" TYPE="ext4" PARTUUID="7ad54111-01"
/dev/sdb5: UUID="b5f3259f-385a-4768-b6de-a27a60a03468" TYPE="ext4" PTTYPE="dos" PARTUUID="7ad54111-05"
/dev/sdb6: UUID="7878d4b2-294f-4d21-974c-7929419f617a" TYPE="swap" PARTUUID="7ad54111-06"

The UUID's shown in fstab are listed on the wrong drive as M18 is installed on sdb, not sda. 

I reckon this has happened due to the way I installed M18.  Because of previous Grub issues with installing distro's on separate HDD's, on Mark's advice, I disconnected sda (M17) before installing M18 on sdb.  I now realise that, as the only HDD 'seen' by the system, this drive now automatically becomes 'sda' and the fstab file would be generated to reflect that.

On booting to M18, the system must first be looking for the boot files for M18 on sda and they aren't there - hence the long delay.  Is there a way to re-generate the fstab file to show the correct locations, now  that both HDD's are connected?  Btw, both distro's run fine, it's just that M18 takes an age to boot - more than twice as long as M17.

Thanks for your time.

Rich





10
General Help & Advice / Re: Mdm and Lightdm
« on: October 31, 2017, 01:39:07 pm »
Code: [Select]
sudo apt-get remove --purge slick-greeter lightdm lightdm-settings apparmor

Lovely - all done and dusted!

and NO, don't mess with the boot files ;)

Understood!   ;) 

11
General Help & Advice / Re: Mdm and Lightdm
« on: October 31, 2017, 01:22:31 pm »
Mark that's brilliant!  All up and running  ;)  Thanks very much - I'll set this as solved shortly.

Just a couple of points. 

The installer also listed lightdm as available.  Given that there is a possibility for future conflict, I'd rather remove it altogether.  What's the best way? 

And, looking at the output from fdisk -l, the boot files in M18 are in a different location to those in M17, yet  I deliberately set things up on sdb in exactly the same way as I'd done on sda due to previous issues with Grub finding the files.  Does this matter?  And would it cause further issues if they were moved from sdb5 to sdb1?

Thanks again 

Rich



12
General Help & Advice / Re: Mdm and Lightdm
« on: October 31, 2017, 12:27:25 pm »
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0001ba51

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048    980991    978944   478M 83 Linux
/dev/sda2          983038 312580095 311597058 148.6G  5 Extended
/dev/sda5          983040 152638097 151655058  72.3G 83 Linux
/dev/sda6       304693248 312580095   7886848   3.8G 82 Linux swap / Solaris


Disk /dev/sdb: 37.3 GiB, 40020664320 bytes, 78165360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7ad54111

Device     Boot    Start      End  Sectors  Size Id Type
/dev/sdb1           2048   976895   974848  476M 83 Linux
/dev/sdb2         978942 78163967 77185026 36.8G  5 Extended
/dev/sdb5  *      978944 70352895 69373952 33.1G 83 Linux
/dev/sdb6       70354944 78163967  7809024  3.7G 82 Linux swap / Solaris
mint@mint ~ $

sda is Mint 17.3 Qiana - sdb is Mint 18.2 Sonya.  It's 18 that won't boot.

13
General Help & Advice / Re: Mdm and Lightdm
« on: October 31, 2017, 12:05:13 pm »
Have you got a Mint 18 Live USB ?

If so, can you boot to it and post the output from:
Code: [Select]
sudo fdisk -l
so we can figure out which is your Mint partition.

Then we can mount that partition, chroot into it, and reinstall mdm.

My box won't boot from a usb but I have the M18 disk - will that work?

14
General Help & Advice / Re: Mdm and Lightdm
« on: October 31, 2017, 11:25:01 am »
can you link to the instructions you followed ?

https://blog.linuxmint.com/?p=3306

[EDIT]

And if you hit Ctrl+Alt+F3 (to drop to a text console), log on, then run:
Code: [Select]
sudo service lightdm restart
does it give any clues why lightdm doesn't start ?

Hi Mark - I can only get to a console via 'Advanced Options'.( Hitting Ctrl+Alt+F3 in Mint 18.2 drops me to a grub screen where 'sudo service lightdm restart' isn't recognised).  In 'advanced ...' I can get to a console and log in as root then run the command and get errors '...failure to start light display manager...'.  I think that lightdm didn't install properly (if at all) and removing mdm has left me with no display manager at all.

Trying to boot M18 and hitting Esc brings up a screenfull of messages - at the end it states 'Failed to start Light Display Manager'  - See systemctl status lightdm.service for details, but I don't know how to get to this, then last line is 'A start job is running for Hold unt...finishes up (timer running/no limit)



15
General Help & Advice / Mdm and Lightdm (SOLVED)
« on: October 31, 2017, 10:04:44 am »
Hi All
In my efforts to configure Mint 18.2 I've managed to break my display manager........... :-[

I changed from mdm to lightdm using a 'how to' from the official Mint site and all seemed to go well until it came to reboot.  The boot now just hangs at the splash screen.  I can see a screen full of output (by hitting 'enter') and that reports an error 'failure to start light display manager'.  It then runs on for a few more lines then halts, waiting for 'another process'.  Unfortunately, the 'how to' said to remove mdm as part of the changeover so there's no way to switch back to it.

 I have the Mint 18.1 install disk (original install was 18.1 - upgraded to 18.2 via Update Manager) and also Mint 17.3 installed on a separate Hdd (sda) - M18 is on Hdd sdb.

Is it possible to re-install mdm on to M18 from either of these mediums?  I could just reinstall M18 afresh but have made a lot of changes that I would prefer to keep if possible.

Thanks in advance

Rich


Pages: [1] 2 3 ... 26

SimplePortal 2.3.3 © 2008-2010, SimplePortal