Ubuntu
partman-basicfilesystems package

Bug #106209
Comment #27

Comment 27 for bug 106209

Revision history for this message

Craig A. Eddy (tyche-deactivatedaccount) wrote on 2007-11-13:

#27

I am an inexperienced user. Yes, you can call me a n00bie, the label doesn't bother me. What does bother me is that this bug goes back to APRIL of 2007 without a resolution. To a programmer or developer who has experience with dealing with all sorts of strange bugs, this isn't a problem. Just hit <CTL>D and continue on. No sweat. Then bring up 2 terminals. In one, enter blkid. In the other, enter sudo gedit /etc/fstab and compare the UUID's in each, and revise as necessary. See? Problem solved.

Except that an inexperienced user wouldn't know that it's that simple to do. Nor would they feel comfortable with going in and manually editing a system file like that. Especially if the user is fresh out of that "other OS" that has taught him/her so well NOT to touch system files. To an inexperienced user, this is a SERIOUS bug.

I run a dual boot system. That gives me a valid partition for serious work, and a second partition to use as a playground. When a playground partition proves itself to be stable, and set up the way I want, then the purposing of the two partitions switches. I currently have 4 partitions: swap (of course), /home (ok, so I finally got smart), and 2 installation partitions. I am running Ubuntu 7.10 Final (Gutsy Gibbon) on both installation partitions. I recently had a problem with one partition, and did a clean install. The new installation came up with no problem. When I went back to the old partition, I encountered the, "fsck Unable to resulve UUID=. . ." problem. I then spent the better part of a day searching through the Ubuntu Community Forum for a solution. That, and asking some of the wizz-kids that frequent #ubuntu-arizona on irc.freenode.net. After finally gathering up the courage to change the /etc/fstab file (using the procedure in paragraph 1), and with fear and trembling, I rebooted into the old partition. I was relieved to see that the problem had gone away. I'd actually done something right.

Two days ago, I came across another problem that decided me it was time to reinstall on the "playground" partition (I'm hard on playgrounds). Yesterday, I booted back into the old partition (my stable source) and encountered the same problem of "fsck Unable to resolve UUID=. . .". So, today, I went looking for a bug report on the problem, and discovered the above long list of bugs, comments, and possible solutions. I respectfully request that this situation be addressed and corrected. It's gone on way too long.

Thank you,
Craig A. Eddy (tyche)
Member, Ubuntu-Arizona LoCo Team
Member, Ubuntu Marketing Team
https://launchpad.net/~tyche

I am an inexperienced user.  Yes, you can call me a n00bie, the label doesn't bother me.  What does bother me is that this bug goes back to APRIL of 2007 without a resolution.  To a programmer or developer who has experience with dealing with all sorts of strange bugs, this isn't a problem.  Just hit <CTL>D and continue on.  No sweat.  Then bring up 2 terminals.  In one, enter blkid.  In the other, enter sudo gedit /etc/fstab and compare the UUID's in each, and revise as necessary.  See?  Problem solved.

Except that an inexperienced user wouldn't know that it's that simple to do.  Nor would they feel comfortable with going in and manually editing a system file like that.  Especially if the user is fresh out of that "other OS" that has taught him/her so well NOT to touch system files.  To an inexperienced user, this is a SERIOUS bug.

I run a dual boot system.  That gives me a valid partition for serious work, and a second partition to use as a playground.  When a playground partition proves itself to be stable, and set up the way I want, then the purposing of the two partitions switches.  I currently have 4 partitions:  swap (of course), /home (ok, so I finally got smart), and 2 installation partitions.  I am running Ubuntu 7.10 Final (Gutsy Gibbon) on both installation partitions.  I recently had a problem with one partition, and did a clean install.  The new installation came up with no problem.  When I went back to the old partition, I encountered the, "fsck Unable to resulve UUID=. . ." problem.  I then spent the better part of a day searching through the Ubuntu Community Forum for a solution.  That, and asking some of the wizz-kids that frequent #ubuntu-arizona on irc.freenode.net.  After finally gathering up the courage to change the /etc/fstab file (using the procedure in paragraph 1), and with fear and trembling, I rebooted into the old partition.  I was relieved to see that the problem had gone away.  I'd actually done something right.

Two days ago, I came across another problem that decided me it was time to reinstall on the "playground" partition (I'm hard on playgrounds).  Yesterday, I booted back into the old partition (my stable source) and encountered the same problem of "fsck Unable to resolve UUID=. . .".  So, today, I went looking for a bug report on the problem, and discovered the above long list of bugs, comments, and possible solutions.  I respectfully request that this situation be addressed and corrected.  It's gone on way too long.

Thank you, 
Craig A. Eddy (tyche)
Member, Ubuntu-Arizona LoCo Team
Member, Ubuntu Marketing Team
https://launchpad.net/~tyche

Ubuntupartman-basicfilesystems package

Comment 27 for bug 106209

Ubuntu
partman-basicfilesystems package