You’re welcome. Should I start a new topic re system preliminaries required prior to swapping out SSD? I DD’d my 16GB SSD to a 16GB USB formatted ext4 and DD’d it back to the 64GB SSD using my OS6 boot stick. Well, of course, that didn’t work as the new SSD was not recognised by boot process. So I ended up using Boot-repair to install a 1GB boot partition. Now I can boot from the 64GB SSD but it is messy as I have two partitions 1GB and 63GB. Clearly I didn’t do enough homework in preparation!
Sounds like you just need to reinstall grub.
Do you know how to do this ? … or would you like assistance ?
What’s the output from:
sudo fdisk -l
As you can see I made a right mess of this!
"Disk /dev/sda: 63.4 GB, 63350767616 bytes
255 heads, 63 sectors/track, 7701 cylinders, total 123731968 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
Disk identifier: 0x0005219f
Device Boot Start End Blocks Id System
/dev/sda1 * 2050048 123731967 60840960 83 Linux
/dev/sda2 2048 2050047 1024000 83 Linux
Partition table entries are not in disk order"
My starting point was an ext4 16GB USB DD image of the original SSD which I then DD’d to the Super Talent 64GB SSD - which incidentally is measurably faster. If I should have used grub instead of Gparted and Boot Repair then a few steps would be very useful. I should be able to research the detail.
We could reinstall GRUB, but we’d also need to create a swap partition as there isn’t one at the moment … I take it /dev/sda2 is the boot partition you created, or was that meant to be swap ?
Can you post the output from:
mount
and
free -m
Yes, it was the partition I created and looking at my other POS6 ZG5 /dev/sda1 is Boot - Linux, /dev/sda2 is Extended and /dev/sda5 is Linux Swap Solaris which I how I would have installed POS6. I’m assuming then I will need a swap partition. Both machines have RAM upgrades to 1.5Gb if that has any bearing.
$ mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=guest)
$ free -m
total used free shared buffers cached
Mem: 1499 812 687 73 39 371
-/+ buffers/cache: 401 1098
Swap: 0 0 0
Yeah You should really have a swap partition otherwise the system will crash when you run out of memory … and you’ll not be able to use hibernation.
How large is the /boot partition ?
What’s the output from:
df -h
Here’s what I reckon should be the plan of action
a) boot to the LiveUSB and reinstall GRUB to properly point to the /dev/sda1 partition without the need for a separate /boot partition
b) boot to the LiveUSB and delete the /boot partition (/dev/sda2) … though I’d like to know
c) resize /dev/sda1 to leave 2GB unpartitioned free space behind it
d) create a swap 1.5GB partition in that 2GB free space, leaving 500MB unpartitioned for overprovisioning.
(overprovisioning is empty space at the end of the SDD that can be used for failing block remapping)
e) set “swapon” to activate the swap partition.
f) set swappiness to something like 10
I know 2GB is a lot to loose of a 64GB SSD, but really you should be setting aside around 7% (4.5G) of the drive for overprovisioning, and as a general rule of thumb around twice your RAM for swap (3GB).
Sound about right to you ?
I created a partition of 1Gb as per whatever guidance I found at the time. When I checked later only about 60Mb or so had been used. Anyway this is the output from df -h
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 57G 7.4G 47G 14% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 741M 8.0K 741M 1% /dev
tmpfs 150M 1.1M 149M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 750M 400K 750M 1% /run/shm
none 100M 8.0K 100M 1% /run/user
I’m going to work through the steps at some point over the next three days and report back to share.
Tried re-installing Grub from OS memory stick using install-grub to my SSD but got /boot not found. I pressed on with Gparted and have moved the main partition to start at 2048. The remaining 2GB has been partitioned into a 1.5GB swap and unallocated 512Mb as suggested. I just need to set swappiness to 10.
The only problem I have now is that when I boot from my 64Gb SSD I get the GNU GRUB v2.02 menu which is a little disconcerting. Is this related to the problem I encountered with install-grub?
No it’s because you installed GRUB to the master boot record … I thought that was what you wanted ?
When I used Boot Repair to get the ZG5 to boot from the new SSD I unwittingly installed Grub. Should I have used install-mbr instead in this case? Now that the SSD is correctly partitioned all I want to do is lose GNU GRUB menu on boot.
Is there 2 OS’s on the SSD or not ?
you could try this
Open a terminal and run:
sudo gedit /etc/default/grub
and change:-
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
to:-
GRUB_HIDDEN_TIMEOUT=2
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=0
SAVE the file and exit gedit.
Back in the terminal run
sudo gedit /etc/grub.d/30_os-prober
and change (approx line 23):-
quick_boot="1"
to
quick_boot="0"
SAVE the file and exit gedit.
Back in the terminal run:
sudo update-grub
and reboot to test.
I only have Peppermint six OS on the SSD. Do I need Grub then or would a MBR suffice?
Having made the changes the GNU GRUB V2.02 menu no longer appears on boot up - thanks! However as before there is a 17 second delay between the Acer F2 F12 screen and Peppermint start up screen. When this screen appears there’s a message along the top which reads “Keys: Continue to wait, press S for skip mounting or M for Manual recovery” or words to that effect. Is this Grub related as well?
My Peppermint OS now takes three seconds to shutdown which is a big improvement over the original 16Gb SSD!
No you need to have GRUB (or some other bootloader) but if you only have a single OS, GRUB normally hides its menu … I guess that got messed up somewhere along the line.
Following the instructions in my last posting should hide the GRUB menu again.
I’m getting the impression that the hardware just isn’t physically capable of using a bluetooth/wireless combo card.
If people are having to go to these lengths to add bluetooth internally:
and
http://joeharper.net/2008/10/02/43/
you can pretty much guarantee it’s not going to be as easy as just swapping out the card 
As an update - Acer Aspire One (ZG5) compatible Super Talent SSD’s all formats now available again with 10% off coupon.
No connection etc.
As I await the delivery of my second 64GB Super Talent SSD I’d really appreciate some advice on how to migrate Peppermint OS6 and customisations from my other ZG5 SSD to the the 64GB. I boot from POS6 only i.e. not dual booting required. I’m comfortable with swapping the SSD’s but want to avoid a complete OS re-install if that is possible. I started off on the wrong foot last time using DD. Any thoughts?
Have you got an external HDD you can use to write an image to ?
Alas, I don’t have an HDD. All I have is a 2GB boot memory stick (USB) with POS6 installed and then a 16GB and 32GB memory stick (USB). I’m looking to migrate from the ZG5 original 16GB SSD to the Super Talent 64GB SSD.
Well as you have a USB stick larger than the SSD, here’s what I’d do
a) Download the latest Redo Backup & Restore ISO image from here:
and place it on your desktop
b) Install syslinux:
sudo apt-get install syslinux
c) Make the ISO image an isohybrid image:
isohybrid ~/redobackup-livecd-1.0.4.iso
d) Burn the ISO image to the 16GB USB stick, by (In Peppermint 6) right-clicking the redobackup-livecd-1.0.4.iso file and selecting “Make bootable USB stick” … then pointing it at the 16GB stick.
e) boot to the 16GB stick … once booted, also inert the 32GB stick and use Redo to create a full disk image of the SSD saved onto the 32GB stick.
f) swap out the SSD
g) boot back to the 16GB stick and use Redo to restore the backup you wrote to the 32GB stick to the new SSD
h) If necessary (though IIRC you can tell redo to do this on the fly) … boot to the Peppermint 6 LiveUSB and use GPArted to resize the partitions on the 64GB SSD
did that make sense ?
Thanks Mark, I’ll give it a crack and report back. When I insert the 64GB SSD at f) do I need to refomat it to ext4? No need for reply if reformat not needed.