Kelley's questions

I created a zpool, called zstorage, on two mirrored drives, on Ubuntu 18.04. The OS is installed on an SSD, with the /home directory on its own partition on that same SSD. I want to migrate /home to the ZFS pool. As you can see, the pool has been set up and ready - as far as I know. Where do I go from here?

Ordinarily, when moving /home to another drive, one can edit fstab, but ZFS doesn't use fstab. I'm rather stuck at knowing how to move my existing /home to /zstorage/home and how to mount /zstorage/home. The command

sudo zfs set mountpoint=/home zstorage/home

gives me the error

cannot mount '/home': directory is not empty property may be set but unable to remount filesystem.

I have Ubuntu 12.04 and Windows7 installed onto a machine so that I could boot into either one. I wanted to keep using the Windows bootloader (actually EasyBCD), so I made sure that I didn't install Grub into the MBR, and all was well.

However, a week or two ago, just doing a routine update with Update Manager, it updated Grub but put it into the MBR (without telling me and without asking my permission), disabling the Windows bootloader, so now the machine boots into Grub instead. I'd like to get it back to booting into the Windows bootloader.

I've read it is easy to fix this, but I don't know how. Any help?

Okay, so I did something stupid. I was trying to clean up my Grub entries, and accidentally removed all of my Linux kernels from Grub (they're still on the hard drive). So now, obviously, Grub doesn't give me any way to boot into Ubuntu; I can boot into Windows just fine, but Ubuntu isn't even listed.

So I just want to run "sudo upgrade-grub" somehow to restore Ubuntu to the list. I can boot from a LiveCD, but once there how do I run that command? (My Ubuntu installation is on sda5, by the way.)

I saw on a couple sites that there were instructions for installing Google Earth 6.2, so I did it. The results were not good. Now, every place I view is broken into rectangles of somewhat different colors, making it very difficult to use.

It does this whether I zoom in or out, and no matter where on the planet I look.

If I could completely remove Google Earth and reinstall it, I could give it another try, but I don't know how to get it completely off my system. I even went into my home directory and found the .googleearth folder and deleted it and then tried reinstalling, but it's always the same story.

Has anyone seen something like this before, and/or have a way to fix it? Thanks!

UPDATE

I tried the instructions on WebUpd8, which basicaly were just that there was an update. I downloaded the 64-bit deb from the Google Earth site, and double-clicked it. It opened the Software Center and said it would conflict, so I figured I should uninstall the previous version. When I then tried to install the new version, it seemed to go well, until I opened it and saw how it looked. So I thought perhaps I had not completely removed the prior version.

I tried running sudo apt-get purge google-earth* googleearth* and then removing everything from /opt/google/earth/free, hoping to clear out any remnants that could interfere with a fresh install, but those haven't worked.

I then followed some older instructions from WebUpd8 for installing Google Earth 6.1 by building a an installable deb with Google-Earth-Package. I now have that older Google Earth working, but 6.2 is still on the computer, too, and is still looking really bad.

UPDATE 2

Output from recommended commands:

    ~$ sudo dpkg --list | grep earth
[sudo] password for mdk: 
ii  google-earth-stable                    6.2.0.5905-r0                           Explore, search and discover the planet
ii  googleearth                            6.0.3.2197+0.6.0-1                      Google Earth, a 3D map/planet viewer
ii  googleearth-package                    0.6.1                                   utility to automatically build a Debian package of Google Earth

Of course, that's after trying to get things working by reinstalling 6.0.3. It shows they're both still there.

~$ sudo apt-get install --reinstall google-earth
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package google-earth

Recently I started having a problem when checking for updates: the process stalled for several minutes while connecting to the medibuntu site. This happened every time. (Mysteriously, this only happened on one of my two computers.) Getting tired of this, I unchecked Medibuntu in my software sources, and everything speeded up again.

Is this something I will regret? I have some things installed from Medibuntu, but once installed do I get anything by getting updates from Medibuntu? Or are things now provided elsewhere - like in Multiverse - sufficiently now so that I no longer need Medibuntu?

I used to listen to a radio station (KNRS) online that uses iHeartRadio (www.iheartradio.com) for online radio. After upgrading to 11.10, it no longer works. In fact, I have to "force quit" to get out of it. I can't check what format the service uses, as it freezes before I can do anything on the site. However, it does work with Chromium.

I can listen to other stations that use different services (such as WLS-AM). Flash, Banshee, VLC, etc., all work just fine, as far as I can tell.

This is the same on two computers: my desktop, and my laptop. Has anyone else experienced this? Any ideas or suggestions?

I upgraded 11.04 to 11.10 using the online upgrade, and all went well except for Banshee. It shows under the sounds icon in the panel, and the icon for the program shows in Applications in the Dash, but clicking on either one does nothing (as does trying to run it from the terminal). There are no error messages or other indications that anything is wrong.

I tried uninstalling it and then reinstalling, but I receive the message "Package dependencies cannot be resolved". Hmmm ... how would I fix that?

UPDATE:

mdk@savina:~$ sudo apt-get update && sudo apt-get upgrade
[sudo] password for mdk: 
Ign http://extras.ubuntu.com oneiric InRelease
Ign http://archive.canonical.com oneiric InRelease                             
Ign http://security.ubuntu.com oneiric-security InRelease                      
Hit http://extras.ubuntu.com oneiric Release.gpg                               
Hit http://archive.canonical.com oneiric Release.gpg                           
Hit http://security.ubuntu.com oneiric-security Release.gpg          
Hit http://extras.ubuntu.com oneiric Release                         
Ign http://us.archive.ubuntu.com oneiric InRelease                             
Ign http://us.archive.ubuntu.com oneiric-updates InRelease                     
Hit http://archive.canonical.com oneiric Release                               
Hit http://security.ubuntu.com oneiric-security Release              
Hit http://extras.ubuntu.com oneiric/main Sources                              
Hit http://archive.canonical.com oneiric/partner Sources             
Hit http://security.ubuntu.com oneiric-security/main Sources         
Hit http://extras.ubuntu.com oneiric/main amd64 Packages             
Hit http://extras.ubuntu.com oneiric/main i386 Packages                        
Hit http://us.archive.ubuntu.com oneiric Release.gpg                           
Hit http://security.ubuntu.com oneiric-security/restricted Sources             
Hit http://security.ubuntu.com oneiric-security/universe Sources     
Hit http://archive.canonical.com oneiric/partner amd64 Packages      
Hit http://archive.canonical.com oneiric/partner i386 Packages       
Ign http://archive.canonical.com oneiric/partner TranslationIndex    
Ign http://extras.ubuntu.com oneiric/main TranslationIndex           
Hit http://security.ubuntu.com oneiric-security/multiverse Sources   
Hit http://security.ubuntu.com oneiric-security/main amd64 Packages            
Hit http://security.ubuntu.com oneiric-security/restricted amd64 Packages      
Hit http://security.ubuntu.com oneiric-security/universe amd64 Packages        
Hit http://security.ubuntu.com oneiric-security/multiverse amd64 Packages      
Hit http://security.ubuntu.com oneiric-security/main i386 Packages             
Hit http://security.ubuntu.com oneiric-security/restricted i386 Packages       
Hit http://security.ubuntu.com oneiric-security/universe i386 Packages         
Hit http://security.ubuntu.com oneiric-security/multiverse i386 Packages       
Ign http://security.ubuntu.com oneiric-security/main TranslationIndex          
Ign http://security.ubuntu.com oneiric-security/multiverse TranslationIndex    
Ign http://security.ubuntu.com oneiric-security/restricted TranslationIndex    
Ign http://security.ubuntu.com oneiric-security/universe TranslationIndex
Hit http://us.archive.ubuntu.com oneiric-updates Release.gpg         
Hit http://us.archive.ubuntu.com oneiric Release                     
Hit http://us.archive.ubuntu.com oneiric-updates Release                       
Ign http://extras.ubuntu.com oneiric/main Translation-en_US                    
Ign http://extras.ubuntu.com oneiric/main Translation-en                       
Ign http://archive.canonical.com oneiric/partner Translation-en_US   
Hit http://us.archive.ubuntu.com oneiric/main Sources                
Hit http://us.archive.ubuntu.com oneiric/restricted Sources          
Hit http://us.archive.ubuntu.com oneiric/universe Sources            
Hit http://us.archive.ubuntu.com oneiric/multiverse Sources          
Hit http://us.archive.ubuntu.com oneiric/main amd64 Packages         
Ign http://archive.canonical.com oneiric/partner Translation-en      
Ign http://security.ubuntu.com oneiric-security/main Translation-en_US
Ign http://security.ubuntu.com oneiric-security/main Translation-en
Hit http://us.archive.ubuntu.com oneiric/restricted amd64 Packages
Hit http://us.archive.ubuntu.com oneiric/universe amd64 Packages
Hit http://us.archive.ubuntu.com oneiric/multiverse amd64 Packages
Hit http://us.archive.ubuntu.com oneiric/main i386 Packages
Hit http://us.archive.ubuntu.com oneiric/restricted i386 Packages
Hit http://us.archive.ubuntu.com oneiric/universe i386 Packages
Ign http://security.ubuntu.com oneiric-security/multiverse Translation-en_US
Ign http://security.ubuntu.com oneiric-security/multiverse Translation-en
Ign http://security.ubuntu.com oneiric-security/restricted Translation-en_US
Ign http://security.ubuntu.com oneiric-security/restricted Translation-en
Ign http://security.ubuntu.com oneiric-security/universe Translation-en_US
Ign http://security.ubuntu.com oneiric-security/universe Translation-en
Hit http://us.archive.ubuntu.com oneiric/multiverse i386 Packages
Hit http://us.archive.ubuntu.com oneiric/main TranslationIndex
Hit http://us.archive.ubuntu.com oneiric/multiverse TranslationIndex
Hit http://us.archive.ubuntu.com oneiric/restricted TranslationIndex
Hit http://us.archive.ubuntu.com oneiric/universe TranslationIndex
Hit http://us.archive.ubuntu.com oneiric-updates/main Sources
Hit http://us.archive.ubuntu.com oneiric-updates/restricted Sources
Hit http://us.archive.ubuntu.com oneiric-updates/universe Sources
Hit http://us.archive.ubuntu.com oneiric-updates/multiverse Sources
Hit http://us.archive.ubuntu.com oneiric-updates/main amd64 Packages
Hit http://us.archive.ubuntu.com oneiric-updates/restricted amd64 Packages
Hit http://us.archive.ubuntu.com oneiric-updates/universe amd64 Packages
Hit http://us.archive.ubuntu.com oneiric-updates/multiverse amd64 Packages
Hit http://us.archive.ubuntu.com oneiric-updates/main i386 Packages
Hit http://us.archive.ubuntu.com oneiric-updates/restricted i386 Packages
Hit http://us.archive.ubuntu.com oneiric-updates/universe i386 Packages
Hit http://us.archive.ubuntu.com oneiric-updates/multiverse i386 Packages
Hit http://us.archive.ubuntu.com oneiric-updates/main TranslationIndex
Hit http://us.archive.ubuntu.com oneiric-updates/multiverse TranslationIndex
Hit http://us.archive.ubuntu.com oneiric-updates/restricted TranslationIndex
Hit http://us.archive.ubuntu.com oneiric-updates/universe TranslationIndex
Hit http://us.archive.ubuntu.com oneiric/main Translation-en
Hit http://us.archive.ubuntu.com oneiric/multiverse Translation-en
Hit http://us.archive.ubuntu.com oneiric/restricted Translation-en
Hit http://us.archive.ubuntu.com oneiric/universe Translation-en
Hit http://us.archive.ubuntu.com oneiric-updates/main Translation-en
Hit http://us.archive.ubuntu.com oneiric-updates/multiverse Translation-en
Hit http://us.archive.ubuntu.com oneiric-updates/restricted Translation-en
Hit http://us.archive.ubuntu.com oneiric-updates/universe Translation-en
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
mdk@savina:~$ 

This morning on my laptop I ran Update Manager (I'm running 11.04) and I received a message that I could only run a partial update. Being fairly new to Ubuntu, I wasn't sure what I should do, but it appeared to want to do some updates but not all, and even remove some things. It gave several possible reasons for this, one of them being that this might occur with a "pre-release version." Since 11.10 is coming out next week, I figured that might be the cause, so I had it go ahead.

A few hours later, I ran Update Manager on my desktop computer, and was presented with the same choice. Since it appeared to have worked on my desktop, I chose to let it apply the "partial update", too.

Since then, on both computers, I've noticed a few little bugs. Nothing big, but nothing I had been previously experiencing. And in the history folder of the Software Center, no updates are listed as having been applied today.

So my question is, what does it mean when Update Manager wants to run a partial update? Is it better not to accept it (and thus not do any updates)?

On my Ubuntu 11.04 64-bit system, this morning the Update Manager wanted to install the 2.6.38-10-generic kernel, so I let it. I haven't noticed any difference except that memory no longer seems to leak. Usually, after awhile the memory usage increases gradually and doesn't drop much, even when I close programs, but since installing the new kernel it seems to return to "normal" (about where it was after reboot) when I close programs. Of course, I don't really know if this is due to the kernel or to something else. Does someone out there know if this was a fix in the kernel?

I'm glad for the improvement, but don't really know what brought it about.

Earlier today my Unity desktop disappeared: I got a black screen with white text, but it disappeared too quickly for me to read. When the desktop reappeared, it was the Ubuntu Classic desktop. I used $ unity --reset but that did not do anything. I tried rebooting so I could choose unity from the list when I logged in, but although there was Ubuntu choice, there was no unity listed (but classic was listed). I was able to install Unity 2D and am using that, but really want to get 3D back.

I had been using Ubuntu without problems for several weeks when this happened. My graphics card is onboard a Dell Latitude desktop - a couple years old - and is reported as an Intel G33/G31.

I've looked at other requests for help here, and tried suggestions when they seemed to relate to similar problems, but nothing seems to work so far.

Any ideas? Thanks!

This is part of the output of my latest attempt to run unity --reset

Window manager warning: 0x3e01c35 () appears to be one of the offending windows with a timestamp of 1309472834.  Working around...
Window manager warning: last_user_time (1309473695) is greater than comparison timestamp (1126160).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Window manager warning: 0x4c0046c (mdk@Habane) appears to be one of the offending windows with a timestamp of 1309473695.  Working around...
Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4c0046c (mdk@Habane)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.

I've been running a couple Screenlets for awhile and like them. I'm only running two, although there are quite a few more in Screenlets. However, today I found that icons for all of them, whether or not I'm using them, have appeared in Installed Programs. Curiously, they do not have identifying text under them, as do all other programs there. How do I get rid of them?

Last week I installed Miredo and configured my system to handle IPv6 through 6to4 tunneling. It was easy and it worked well.

So I decided I'd give Hurricane Electric's IPv6 connection a try. I've had a lot to learn, and I thought I had it all running (with a great deal of help from a very patient person at Hurricane: my LinkSys E3200 didn't like IPv6).

But now, when all should be good, after I uninstalled Miredo and Teredo and whatever else, I find that there is "6to4 tunneling - another automatic tunneling," which I need to remove from my box. But I have no idea where or what it might be.

Connected to my computer are a couple printers, an external hard drive, and a router (which has no settings for IPv6). All of these are, I think, innocent in this matter.

$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:21:9b:1c:26:bb  
          inet addr:192.168.1.104  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: 2002:42db:c22c:0:221:9bff:fe1c:26bb/64 Scope:Global
          inet6 addr: fe80::221:9bff:fe1c:26bb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1427 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1342 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1152240 (1.1 MB)  TX bytes:177497 (177.4 KB)
          Interrupt:20 Memory:fdfc0000-fdfe0000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:720 (720.0 B)  TX bytes:720 (720.0 B)

$ ip -6 route show
2002:42db:c22c::/64 dev eth0  proto kernel  metric 256  expires 24sec
fe80::/64 dev eth0  proto kernel  metric 256 
default via fe80::c2c1:c0ff:fec6:3308 dev eth0  proto kernel  metric 1024  
expires   1794sec hoplimit 64

So, how can I get rid of 6to4 tunneling, when I don't even know where it is? Is there someplace to look and find out what's going on? I'm pretty new to Linux and Ubuntu.

So it looks like Miredo isn't running, yet I'm getting IPv6 addresses in eth0. It was that, I think, that a guy at Hurricane Electric was seeing and that caused him to see "6to4 tunneling - another automatic tunneling." Is that just a feature of Ubuntu?

He told me this:

"Look for a machine that has 6to4 tunneling configured and announcing 6to4 prefix to your linux box.

Here's the clue: According to your IPv6 route table, fe80::XXXX:XXXX:XXXX:XXXX is a link local address for your default gateway. Can you check and see which device has a MAC address of XX-XX-XX-XX-XX?"

It turns out that the device with that MAC address is my LinkSys router! (Which has NO IPv6 support!) I don't understand that.

I'm pretty new to Ubuntu, and installed Natty (32-bit, because it was recommended) soon after it came out. The installation process chose to put Natty onto an external USB hard drive, a 500 MB WD Passport, which I liked (it wouldn't interfere with my Windows partition that way). However, at boot, the computer boots directly into Windows unless I press F12 (on my Dell) to choose boot options, and then select to boot into the Passport. Then I get grub and select to boot into Ubuntu. I don't really mind this; it seems obvious that grub was installed onto the Passport. No big deal.

But I just recently installed 64-bit Natty onto the Passport, choosing the option to "upgrade Ubuntu 11.04 to Ubuntu 11.04." It went well, most of my settings were saved (and all of my data), but it seems to have installed another instance of grub. Now, when I boot the computer, I have to press F12 to select the Passport (as I did before), then select "earlier versions of Ubuntu" in grub, at which time another grub screen comes up which allows me to choose the right OS (the 64-bit version).

I don't mind selecting the Passport, but after that I'd rather have one grub screen, not two in a row. How do I do this?

mdk@Tabasco:~$ sudo fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe49667b6

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1           5       40131   de  Dell Utility
/dev/sda2               6        1918    15358976    7  HPFS/NTFS
/dev/sda3   *        1918       35363   268649893+   7  HPFS/NTFS
/dev/sda4           35363       60802   204334080    f  W95 Ext'd (LBA)
/dev/sda5           35363       60802   204333056    7  HPFS/NTFS

Disk /dev/sdb: 500.1 GB, 500074283008 bytes
201 heads, 9 sectors/track, 539915 cylinders
Units = cylinders of 1809 * 512 = 926208 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00038a56

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           2      269958   244175360    7  HPFS/NTFS
/dev/sdb2          269958      539915   244175873    5  Extended
/dev/sdb5          269958      535292   239993856   83  Linux
/dev/sdb6          535293      539915     4180992   82  Linux swap / Solaris

Disk /dev/sdc: 1299 MB, 1299594240 bytes
40 heads, 62 sectors/track, 1023 cylinders
Units = cylinders of 2480 * 512 = 1269760 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System