I am running Debian Wheezy, and needed to clone a running installation to a smaller SSD drive, so that the SSD can be used in another laptop. My current Harddisk is 500 GB, the SSD is 128GB. As you may be aware, most disk cloning softwares, including my favourite Clonezilla, are set up to go to a same or larger disk; not smaller.
So this is how I accomplished the task:
on the running system attach the SSD drive ( my system has a nice fast eSata ), and run gparted to format and partition the drive. Set it up as MBR partition, MSDOS type, with a similar layout to what you had. HOWEVER, I added a separate /var partition, because a SSD has a relatively high failure rate with many read/writes on a particular memory cell, and /var is where much of that happens. So when it comes down to it, the system could fail, and it would be easy to recover.
Then I made a bash script to do some work for me:
# /dev/sdb below is MY SSD drive, change it for yours
mount /dev/sdb1 /mnt/new/boot
mount /dev/sdb3 /mnt/new
rsync -auv \
rsync -auv /var/ /mnt/new/var
rsync -auv /boot/ /mnt/new/boot
grub-install --recheck --root-directory=/mnt/new /dev/sdb
Save it as ~/clone.sh
then chmod +x clone.sh to make it executable
then su to switch to root user
then ./clone.sh to run the script.
Open another terminal as ROOT.
blkid will print out the UUID for each partition in the system. You want to note the ones for your SSD.
back to the first terminal window;
grub-install --boot-directory=/mnt/new/boot /dev/sdb
Edit /mnt/new/etc/fstab & /mnt/new/boot/grub/grub.cfg to taste with new UUIDs for the SSD...be careful!!
mount --bind /dev/ /mnt/new/dev mount --bind /sys/ /mnt/new/sys chroot /mnt/new update-grub After that, the GRUB command should have completed happily, in which case your system is ready to rock and roll on the SSD. Remember that if you have different users then you need to handle the addition of those at ROOT level first.
mount --bind /dev/ /mnt/new/dev
mount --bind /sys/ /mnt/new/sys
After that, the GRUB command should have completed happily, in which case your system is ready to rock and roll on the SSD. Remember that if you have different users then you need to handle the addition of those at ROOT level first.
Wow, looooong time no post, eh?
I am here to tell you that I am on Debian Wheezy, running on a Dell Inspiron 17R (n7110) laptop. I use XFCE 4.8 for my DE.
Thunar is the default file manager in XFCE, and is fast and easy... but doesn't natively handle OBEX FTP that is what bluetooth needs, s o we need to use FUSE as an intermediate layer.
Here is how to get Bluetooth to work happily in such an environment:
Open the terminal, then:
<enter root password>
apt-get install fuse fuse-utils blueman
Now, using your favoured text editor, create a file at your home directory called 'bluetooth-thunar.sh', with this inside it:
#!/bin/bash fusermount -u ~/bluetooth obexfs -b $1 ~/bluetooth thunar ~/bluetooth
Save and close. Open the terminal again, do:
chmod +x ~/bluetooth-thunar.sh
adduser <yourusername> fuse
Now, right-click the Bluetooth icon in the system tray, and choose
Local Services > Transfer > Advanced
Set how you want the file sharing to be handled in the checkboxes, and in Advanced, put:
sh /home/yourusername/bluetooth-thunar.sh %d
Now set up the bluetooth phone in the BlueMan Manager. Test the Browse files on device. You may have to log out to make it function.
What you should have is a Thunar File Manager window pop open to your newly created bluetooth directory, so you can drag and drop files both ways.
Yes, yes, I know... it would be great to have this all pre-done so it is automagical. But where is the fun in using Debian in that case? It's fast and raw because all of that is not assumed about you.
Hmmm, I'm not spending much time here lately...too many other projects on the boil...but checked out the statistics for the past month, and all of a sudden they have shot through the roof. Yet most of my content is old (well, to me anyhow).
So tell me, dear readers what it is that you come here for?
Do you want to see this blog continue?