My goal was to totally backup my laptop image to a usb drive.
I used UNetbootin to create a bootable USB drive with the clonezilla ISO.
I’m not sure if doing this was baaad… or not.
So, I rebooted my laptop and selected the USB drive, and clonezilla popped up. Good start, I went with all the defaults to backup the image on my laptop to the USB drive.
I ran into a problem where it said that I was out of space, so no quite understanding, I backed out of it totally and rebooted my laptop.
When the laptop came up, I had a keyboard failure. I rebooted it again and it went away, but it took forever to boot.
Now when I boot, it takes forever. Forever meaning minutes instead of seconds.
I’m positive I hosed something up. How do I find out what I screwed up, and how then do I fix it?
Was the USB entered into th fstab? If so it may be looking for it.
How do I check for that?
It’s pretty odd. It takes 3 - 4 minutes to boot, and my keyboard is dead the entire time (can’t enter network password).
cat /etc/fstab
At what point is it slow?
Have you pressed esc after the bootup start to see if some process is slow?
Here is the output of cat etc/fstab:
linux-dbrq:/home/yehudah # cat /etc/fstab
/dev/disk/by-id/ata-WDC_WD3200BEVT-75ZCT2_WD-WXE908LNA035-part1 swap swap defaults 0 0
/dev/disk/by-id/ata-WDC_WD3200BEVT-75ZCT2_WD-WXE908LNA035-part2 / ext4 acl,user_xattr 1 1
/dev/disk/by-id/ata-WDC_WD3200BEVT-75ZCT2_WD-WXE908LNA035-part3 /home ext4 acl,user_xattr 1 2
/dev/disk/by-id/ata-Wintec_SSD_48GB_WT1027C4D048000339-part1 /windows/C ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
I have a 320GB drive in the laptop, looks like it has a swap and two partitions (not sure why - I used default settings to set it up originally)
I also have an SSD 48GB card installed.
It doesn’t show anything else, that’s a good thing I think.
I’ll look at the boot sequence and post the results a little later.