[opensuse] Order of drives changed in 11.2?
Hello SuSE people, Downloaded the 11.2 build and was going to upgrade my 11.0 test bed. I have three drives with several versions on them. sda with windows and a bunch of storage. sdb with 11.0 sdc1 with 10.2 and sdc8 with 10.3 When I went to upgrade 11.0 TO 11.2 the installer listed the drives this way: sda1 as 10.2 and sda8 as 10,3 No mention of sdb sdc as 11.0 I was afraid to continue for fear of overwriting something else. Anybody else seeing this? Is it a change again? Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, May 19, 2009 at 4:52 PM, Bob S <911@sanctum.com> wrote:
Hello SuSE people,
Downloaded the 11.2 build and was going to upgrade my 11.0 test bed.
I have three drives with several versions on them. sda with windows and a bunch of storage. sdb with 11.0 sdc1 with 10.2 and sdc8 with 10.3
When I went to upgrade 11.0 TO 11.2 the installer listed the drives this way:
sda1 as 10.2 and sda8 as 10,3 No mention of sdb sdc as 11.0
I was afraid to continue for fear of overwriting something else. Anybody else seeing this? Is it a change again?
Bob S
Bob, The old /dev/hda scheme was tied to the physical structure of the machine, so it could be trusted to be constant. The new /dev/sda scheme has the names assignedthe order of the drivers loaded. Consistency is not even a goal of the new design. So you have to switch to using one of the /dev/disk/by-* designations for your disk. Yes, I too find it very frustrating, especially since opensuse does not even include a real tool for converting the various references. Please go vote for the fate entry about this. https://features.opensuse.org/306321 You need to update /etc/fstab (can be done via the yast2-partitioner) /boot/grub/device.map, and /boot/grub/menu.lst (I don't know of anything but an editor to handle those.) The fate entry does not discuss these last 2, but it should. Feel free to add that if you go look at it. I already have 2 comments, so it would be nice is new name were adding comments. It will make it look of more general interest. Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 19 May 2009 04:57:35 pm Greg Freemyer wrote: .<old message snipped>.........
Bob,
The old /dev/hda scheme was tied to the physical structure of the machine, so it could be trusted to be constant.
Yeah, I remember. Had an hda, an hdb, and an sda at one of the iterations, I think at the install of 10.2. Then I think they all became sdx at the install of 10.3
The new /dev/sda scheme has the names assignedthe order of the drivers loaded. Consistency is not even a goal of the new design.
So you have to switch to using one of the /dev/disk/by-* designations for your disk.
I do use disk/bylabel but that doesn't change the drive designation or help you identify a drive during the installation phase.
Yes, I too find it very frustrating, especially since opensuse does not even include a real tool for converting the various references. Please go vote for the fate entry about this. https://features.opensuse.org/306321
You need to update /etc/fstab (can be done via the yast2-partitioner)
?? That statement confuses me. You mean on all of my existing installs? and after the new upgrade?
/boot/grub/device.map, and /boot/grub/menu.lst (I don't know of anything but an editor to handle those.)
Same as above? The editing doesn't bother me, assuming I can get to them.
The fate entry does not discuss these last 2, but it should. Feel free to add that if you go look at it. I already have 2 comments, so it would be nice is new name were adding comments. It will make it look of more general interest.
I will take a look and definitely add my comments. This is really getting to be a PITA. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 19 May 2009 04:57:35 pm Greg Freemyer wrote: .....< snip a lot>.......
Yes, I too find it very frustrating, especially since opensuse does not even include a real tool for converting the various references. Please go vote for the fate entry about this. https://features.opensuse.org/306321
You need to update /etc/fstab (can be done via the yast2-partitioner)
/boot/grub/device.map, and /boot/grub/menu.lst (I don't know of anything but an editor to handle those.)
The fate entry does not discuss these last 2, but it should. Feel free to add that if you go look at it. I already have 2 comments, so it would be nice is new name were adding comments. It will make it look of more general interest.
Greg I added my comment but did not mention device map or menu.lst because I haven't worked up the nerve to do the upgrade yet and don't know what will happen. Bob S. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, May 19, 2009 at 11:34 PM, Bob S <911@sanctum.com> wrote:
On Tuesday 19 May 2009 04:57:35 pm Greg Freemyer wrote:
.....< snip a lot>.......
Yes, I too find it very frustrating, especially since opensuse does not even include a real tool for converting the various references. Please go vote for the fate entry about this. https://features.opensuse.org/306321
You need to update /etc/fstab (can be done via the yast2-partitioner)
/boot/grub/device.map, and /boot/grub/menu.lst (I don't know of anything but an editor to handle those.)
The fate entry does not discuss these last 2, but it should. Feel free to add that if you go look at it. I already have 2 comments, so it would be nice is new name were adding comments. It will make it look of more general interest.
Greg
I added my comment but did not mention device map or menu.lst because I haven't worked up the nerve to do the upgrade yet and don't know what will happen.
Bob S.
Don't forget to vote for it too. I find the whole process horribly painful. On a new install it all happens, but on an upgrade from configs with /dev/hda style references, I think the whole thing is a bit daunting. In fact a machine I upgraded 2 months ago just needed rebooting today, and I had the /boot/grub/* stuff wrong, so it would not boot. Took me an hour or so to straighten it out. Unacceptable. Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday May 19 2009, Bob S wrote:
Hello SuSE people,
Downloaded the 11.2 build and was going to upgrade my 11.0 test bed.
I have three drives with several versions on them. sda with windows and a bunch of storage. sdb with 11.0 sdc1 with 10.2 and sdc8 with 10.3
When I went to upgrade 11.0 TO 11.2 the installer listed the drives this way:
sda1 as 10.2 and sda8 as 10,3 No mention of sdb sdc as 11.0
I was afraid to continue for fear of overwriting something else. Anybody else seeing this? Is it a change again?
The assignment of the drive letter portion of a disk device's minor number is not stable or predictable and should never be counted on. Use either a volume label (where available) or a drive or partition unique ID. Boot your 11.0 system and list all the entries in /dev/disk/by-id. There you'll find a symlink for every drive and every partition to a /dev/sdD or /dev/sdDP entry (D: drive; P: partition). That will let you know unambiguously where your existing partitions are in terms that are stable across releases. Then when you're in the partitioner module of the installer you can tell it to display these unique IDs and correlate them with what you know a given drive or partition holds. Personally, I label all my partitions (including swap partitions) and use by-label mounting. This is indicated by fstab entries that use LABEL=driveOrPartitionLabel in the first column..
Bob S
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 19 May 2009 04:58:52 pm Randall R Schulz wrote: .<original message snipped>.......
The assignment of the drive letter portion of a disk device's minor number is not stable or predictable and should never be counted on. Use either a volume label (where available) or a drive or partition unique ID.
Boot your 11.0 system and list all the entries in /dev/disk/by-id. There you'll find a symlink for every drive and every partition to a /dev/sdD or /dev/sdDP entry (D: drive; P: partition). That will let you know unambiguously where your existing partitions are in terms that are stable across releases. Then when you're in the partitioner module of the installer you can tell it to display these unique IDs and correlate them with what you know a given drive or partition holds.
Hello Randall, OK I know where everything is presentlybut if you are doing an upgrade you never get to see the partioner. It just supplies you with this incorrect information.
Personally, I label all my partitions (including swap partitions) and use by-label mounting. This is indicated by fstab entries that use LABEL=driveOrPartitionLabel in the first column..
I also use /disk/by-label but as I explained to Greg that doesn't help when you are upgrading blindly. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday May 19 2009, Bob S wrote:
On Tuesday 19 May 2009 04:58:52 pm Randall R Schulz wrote: .<original message snipped>.......
The assignment of the drive letter portion of a disk device's minor number is not stable or predictable and should never be counted on. Use either a volume label (where available) or a drive or partition unique ID.
Boot your 11.0 system and list all the entries in /dev/disk/by-id. There you'll find a symlink for every drive and every partition to a /dev/sdD or /dev/sdDP entry (D: drive; P: partition). That will let you know unambiguously where your existing partitions are in terms that are stable across releases. Then when you're in the partitioner module of the installer you can tell it to display these unique IDs and correlate them with what you know a given drive or partition holds.
Hello Randall,
OK I know where everything is presentlybut if you are doing an upgrade you never get to see the partioner. It just supplies you with this incorrect information.
That is not true. Use the fancy / full-feature partitioner, not the "we know what's best for you" mode.
Personally, I label all my partitions (including swap partitions) and use by-label mounting. This is indicated by fstab entries that use LABEL=driveOrPartitionLabel in the first column..
I also use /disk/by-label but as I explained to Greg that doesn't help when you are upgrading blindly.
I only know the expert partitioner, but it shows everything that it can detect / determine about existing partitions, and that includes their labels.
Bob S
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 19 May 2009 06:42:53 pm Randall R Schulz wrote:
Hello Randall,
OK I know where everything is presentlybut if you are doing an upgrade you never get to see the partioner. It just supplies you with this incorrect information.
That is not true. Use the fancy / full-feature partitioner, not the "we know what's best for you" mode.
Hello again Randall, I'm sorry, but it is true, There is no way to access the expert partitioner when you try to do an upgrade. (11.0 to 11.2) You can see all of the partitions but not their labels which are all marked Linux unknown except for the boot partitions which have the bogey (new3ly revised ??) disk letters. I've used the expert partitioner many times doing installs and reinstalls to devise special partitioning schemes and do all of the labeling. You just cannot get to it in this upgrade mode.
Personally, I label all my partitions (including swap partitions) and use by-label mounting. This is indicated by fstab entries that use LABEL=driveOrPartitionLabel in the first column..
I also use /disk/by-label but as I explained to Greg that doesn't help when you are upgrading blindly.
I only know the expert partitioner, but it shows everything that it can detect / determine about existing partitions, and that includes their labels.
Bob S
Randall Schulz
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 19 May 2009, Bob S wrote:-
On Tuesday 19 May 2009 06:42:53 pm Randall R Schulz wrote:
Hello Randall,
OK I know where everything is presentlybut if you are doing an upgrade you never get to see the partioner. It just supplies you with this incorrect information.
That is not true. Use the fancy / full-feature partitioner, not the "we know what's best for you" mode.
Hello again Randall,
I'm sorry, but it is true, There is no way to access the expert partitioner when you try to do an upgrade. (11.0 to 11.2) You can see all of the partitions but not their labels which are all marked Linux unknown except for the boot partitions which have the bogey (new3ly revised ??) disk letters.
When upgrading, you shouldn't actually _need_ to access the partitioner. What should happen, and at least did with my last 10.3 to 11.1 upgrade[0], is that the installer looks to see what installations are available that can be upgraded and it asks which one to upgrade. The fstab is for that installation then read and the various file systems are used. [0] on a PPC, and not actually successful, just in case you're curious. To get it to work I ended up having to do a full install. Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s openSUSE 10.3 32b | openSUSE 11.0 32b | | openSUSE 10.3 64b | openSUSE 11.0 64b | openSUSE 11.1 64b | RISC OS 3.6 | RISC OS 3.11 | openSUSE 11.1 PPC | TOS 4.02 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob, In addition to my earlier comments: When you say 11.2, I assume your talking about the first milestone release? If so, and it is a change in functionality compared to 11.1 you should report that on the factory list. And if you're using the milestone release, you really should be on that list anyway. It is the only form of support you have as I understand it. Greg On Tue, May 19, 2009 at 11:03 PM, Bob S <911@sanctum.com> wrote:
On Tuesday 19 May 2009 06:42:53 pm Randall R Schulz wrote:
Hello Randall,
OK I know where everything is presentlybut if you are doing an upgrade you never get to see the partioner. It just supplies you with this incorrect information.
That is not true. Use the fancy / full-feature partitioner, not the "we know what's best for you" mode.
Hello again Randall,
I'm sorry, but it is true, There is no way to access the expert partitioner when you try to do an upgrade. (11.0 to 11.2) You can see all of the partitions but not their labels which are all marked Linux unknown except for the boot partitions which have the bogey (new3ly revised ??) disk letters.
I've used the expert partitioner many times doing installs and reinstalls to devise special partitioning schemes and do all of the labeling. You just cannot get to it in this upgrade mode.
Personally, I label all my partitions (including swap partitions) and use by-label mounting. This is indicated by fstab entries that use LABEL=driveOrPartitionLabel in the first column..
I also use /disk/by-label but as I explained to Greg that doesn't help when you are upgrading blindly.
I only know the expert partitioner, but it shows everything that it can detect / determine about existing partitions, and that includes their labels.
Bob S
Randall Schulz
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-05-19 at 15:42 -0700, Randall R Schulz wrote:
OK I know where everything is presentlybut if you are doing an upgrade you never get to see the partioner. It just supplies you with this incorrect information.
That is not true. Use the fancy / full-feature partitioner, not the "we know what's best for you" mode.
No, Bob is correct: when upgrading (not fresh install) the partitioner can not be activated; YaST simply installs to the root filesystem it finds and which you select. The only leeway is that you can go to a terminal and mount/umount extra partitions, and perhaps use fdisk/mkfs on the console (I've never tried that). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoVTxAACgkQtTMYHG2NR9XMaACggnzahZbVidCLPjcsCrLoOY42 kQAAoJKpazLz3eK6HNpgjTaV93K8d0Jf =OhMb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday May 21 2009, Carlos E. R. wrote:
On Tuesday, 2009-05-19 at 15:42 -0700, Randall R Schulz wrote:
OK I know where everything is presentlybut if you are doing an upgrade you never get to see the partioner. It just supplies you with this incorrect information.
That is not true. Use the fancy / full-feature partitioner, not the "we know what's best for you" mode.
No, Bob is correct: when upgrading (not fresh install) the partitioner can not be activated; YaST simply installs to the root filesystem it finds and which you select. The only leeway is that you can go to a terminal and mount/umount extra partitions, and perhaps use fdisk/mkfs on the console (I've never tried that).
Too bad. Out of probably a dozen installs, I've only ever done one upgrade. I guess this just adds to the conventional wisdom that plain installs are preferable to upgrades.
-- Cheers, Carlos E. R.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-05-21 at 06:01 -0700, Randall R Schulz wrote:
No, Bob is correct: when upgrading (not fresh install) the partitioner can not be activated; YaST simply installs to the root filesystem it finds and which you select. The only leeway is that you can go to a terminal and mount/umount extra partitions, and perhaps use fdisk/mkfs on the console (I've never tried that).
Too bad. Out of probably a dozen installs, I've only ever done one upgrade. I guess this just adds to the conventional wisdom that plain installs are preferable to upgrades.
You do not need to create/modify partitions when you do an upgrade: the system is already installed, the partitions are the same you have already. In fact, you do not change (almost) anything of the configuration. In the case you do need to change the partitioning, you can do them on the previous version of the system, using the tools you have. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoVVlUACgkQtTMYHG2NR9VKywCfajaVXTxvLX9V04yDLdt4BUdM Rw4AnjsR4y21Rc6jZi+k5CBNVYIRcI24 =9vX7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-05-19 at 18:26 -0400, Bob S wrote:
or /dev/sdDP entry (D: drive; P: partition). That will let you know unambiguously where your existing partitions are in terms that are stable across releases. Then when you're in the partitioner module of the installer you can tell it to display these unique IDs and correlate them with what you know a given drive or partition holds.
Hello Randall,
OK I know where everything is presentlybut if you are doing an upgrade you never get to see the partioner. It just supplies you with this incorrect information.
As this is for 11.2, you should report this in the factory list, where some devs are around and can comment. This way you can influence them and correct the behaviour for when the "real" 11.2 comes out. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoUYkQACgkQtTMYHG2NR9U6NQCgkdqoM8RNEPi9fykXikYMUoRF GFQAniZaaSKj/U6hsPzw4C9EQ7F4WxK0 =VGxK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Bob S -
Carlos E. R. -
David Bolt -
Greg Freemyer -
Randall R Schulz