well, I did a upgrade from 6.06 to 8.04 yesterday and my fstab was not
updated with the new sh* or uuid locations of my drives. and since one
of those drives was my home directory took quite a while to unravel what
the problem was as i only had command line. Find it a bit strange that
this does not
El mié, 03-10-2007 a las 14:36 +, Scott James Remnant escribió:
> We handled the transition during an earlier upgrade cycle, and have
> always written UUID= form since then. If you don't have UUIDs in your
> fstab, it's likely that you removed them yourself. We preserve this for
> you, since
We handled the transition during an earlier upgrade cycle, and have
always written UUID= form since then. If you don't have UUIDs in your
fstab, it's likely that you removed them yourself. We preserve this for
you, since it's your choice.
Gutsy's volumeid (113-0ubuntu15) package contains the mig
Just in case this might help:
[EMAIL PROTECTED]:/home/hjmf# for id in 6 7 8 9; do /sbin/vol_id -u
/dev/sda${id}; echo $?; done
4
4
4
4
[EMAIL PROTECTED]:/home/hjmf# for id in 6 7 8 9; do echo -n "sda${id}: ";
udevinfo --name=sda${id} --query=symlink; done
sda6: disk/by-id/scsi-1ATA_WDC_WD2500JB-
Hello, and thanks to you for following this issue; sadly, I have to say
that this behavior is still present.
As far as from today in the last kernel update (linux-image-2.6.20-16-generic)
I had, when re-boot hanged, to manually change fstab as:
/dev/hda6 /home2 reiserfs defaults 0 2 -> /dev/sda6
Isn't this bug report similar to
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/8497 ?
--
hda -> sda transition not handled during upgrade
https://bugs.launchpad.net/bugs/93655
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I can confirm this. I upgraded yesterday and now I have troubles because
fstab has still the "hdc1, hdc2" etc disks. No transition has been made.
My fstab after the upgrade:
proc/proc procdefaults0 0
/dev/hdc2 / ext3defaults,errors=re
Unduplicated, from #79327, this bug is only about cdrom entries in the
sources.list.
** This bug is no longer a duplicate of bug 79327
fstab entries for CD-ROM drivers not migrated from hdX to sdX
--
hda -> sda transition not handled during upgrade
https://bugs.launchpad.net/bugs/93655
You re
*** This bug is a duplicate of bug 79327 ***
https://bugs.launchpad.net/bugs/79327
I had a similar problem, my swap partition wouldn't mount, resulting in an
barely usable system. I had to manually edit fstab, and now my swap partiton is
used twice:
[EMAIL PROTECTED]:~$ swapon -s
Filename
*** This bug is a duplicate of bug 79327 ***
** This bug has been marked a duplicate of bug 79327
fstab entries for CD-ROM drivers not migrated from hdX to sdX
--
hda -> sda transition not handled during upgrade
https://launchpad.net/bugs/93655
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
forgot to notice that i upgraded from 2.6.20-11-generic to
2.6.20-12-generic, too.
--
hda -> sda transition not handled during upgrade
https://launchpad.net/bugs/93655
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Time for a friendly "me too". Just tried to access a NTFS-Partition
(yeah, well...erm, it's useful :D) just to notice it's "gone" (yeah, i
fixed the fstab entry manually and, whoops, there it was), so no big
problem, still the update-process should just handle this somehow.
fstab:
# /etc/fstab:
12 matches
Mail list logo
