[opensuse] complex confusing partition problem
Hello SuSE users, Going to need a guru for this one. Actually it is not a partition problem but one of having two instances of 10.2 installed -unintentionally. One instance is complete and working. The other is incomplete and missing apps, The only way to demonstrate this is through the partitioning scheme. First you need the background. Sorry, but it is the only way to understand. I originally had two ide hard drives, hda of 80GB and hdb of 30GB. I put a 5GB partition for Windows on hda. The rest of the drive is ext3 which is used for datastorage, storage, backup and workspace. hdb (30GB) was used strictly for 10.2 and utilized LVM partitioning, That drive previously had 9.3 and 10.0 on it. New installs each time. Worked fine - no problems whatsoever as did 10.2. I then bought a 250 GB sata drive to install 10.3 on as I wanted to keep 10.2 on hdb and all of the storage on the hda drive. 10.3 installed flawlessly on the saata drive. However after booting 10.3 a couple of times I decided to copy over some of my stuff from the 10.2 install. To my amazement, when I clicked on 10.2 in the grub menu, it brought up another grub menu with two instances of 10.2. Each of them booted and opened up. One instance was complete and performed perfectly the other opened and looked fine. Same desktop schemes etc. as the good one. But none of my /home info was there and It would not open any of the apps I had installed, would not print, etc. etc. Now, when I installed 10.3 the libata thing came into play. It made the new sata disk sda. then it took the ide disks and renamed hda to sdb and the hdb disk and renamed it sdc. (I complained bitterly to the list but it made no difference) So now I look at the grub menu.lst for both instances of 10.2 and they are exactly the same. NOTE: I renamed the good 10.2 to plain "SUSE" for clarity and so I could choose the proper instance from the second grub menu. Following is the grub menu: -------------------------------- # Modified by YaST2. Last modification on Tue Sep 18 19:13:07 EDT 2007 default 0 timeout 8 gfxmenu (hd1,0)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd title SUSE root (hd2,0) kernel /boot/vmlinuz root=/dev/sda1 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.2 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd title Windows rootnoverify (hd0,0) chainloader (hd0,0)+1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,0) chainloader (fd0)+1 ----------------------------------------------- Note that root is different between SUSE and SUSE 10.2. Also, /dev/sda1 should actually be 10.3 ( I think) So now I look at the fstab for both. They are quite different. Following is for the good instance designated SUSE ----------------------------------------------- /dev/sda1 / ext3 acl,user_xattr 1 1 /dev/sda7 /fat vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/sda2 /home ext3 acl,user_xattr 1 2 /dev/sda6 /tmp ext3 acl,user_xattr 1 2 /dev/sda5 /var ext3 acl,user_xattr 1 2 /dev/sda3 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/hda2 /workspace ext3 user,acl 1 2 /dev/hda3 /datastorage ext3 defaults 1 2 /dev/hda1 /windows vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/hda5 /backup ext3 acl,user_xattr 1 2 /dev/hda6 /storage ext3 acl,user_xattr 1 2 /dev/hda7 /mediadata ext3 noauto,acl,user_xattr 1 2 /dev/hdb1 /boot ext3 acl,user_xattr 1 0 /dev/hdc /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/hdd /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 ----------------------------------------------------------------------------------------- BUT....Look at the first 5 lines. They say /dev/sda*. That can't be, /dev/sda is SUSE 10.3. So now I look at the fstab for 10.3 and I get this unintelligible mess: --------------------------------------------------------------- /dev/sda8 / ext3 acl,user_xattr 1 1 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part5 /backup ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part3 /datastorage ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part9 /home ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part7 /mediadata ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part6 /storage ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part10 /tmp ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part12 /usr ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part11 /var ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part2 /workspace ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part3 swap swap defaults 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 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part1 /windows vfat users,gid=users,umask=0002,utf8=true 0 0 ----------------------------------------------------------------------------------- So continuing on: The following is for the bogus SUSE 10.2 But it looks like it should except that the LVM's don't show. There is however a ~fstab which does show the LVM's. ----------------------------------------------------------------------------------------- /dev/hdb1 / ext3 acl,user_xattr 1 1 /dev/hdb2 /home ext3 acl,user_xattr 1 2 /dev/hdb7 /opt ext3 acl,user_xattr 1 2 /dev/hdb8 /tmp ext3 acl,user_xattr 1 2 /dev/hdb5 /usr ext3 acl,user_xattr 1 2 /dev/hdb6 /var ext3 acl,user_xattr 1 2 /dev/hda1 /windows/C vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/sda7 /windows/D vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/sda3 swap swap defaults 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 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 --------------------------------------------------------------------------------------------- So now I look at my partitioner and of course there is no hda or hdb but it does seem to reflect the partitioning accurately. But no LVM and no explanation for the dual appearances of 10.2. I have attached the screen shot of the partitioner. Hopefully it will survive the censors. If not I can put it up on the web for viewing if anyone wants to see it. I want to keep my SUSE (10.2) and get rid of the bogus SUSE 10.2 because it is solid and complete. Better yet it would be great to get everything in one single grub menu before I install 11.0. I have no idea on how to proceed,or to delete what partitions because libata changed all of the names. The partitioner will show the setup clearly. Hopefully the guru's out there can analyze this and come up with a solution
Bob S a écrit :
Hello SuSE users,
Going to need a guru for this one.
I think I was for the old naming sheme, not so for the new :-(. But what I don't see in your mail is the booting sequence... you can boot of many ways, in Linux. most of the time, when using YaST defaults, grub is written in the MBR (master of the first disk) and so the last openSUSE install rules all the booting system. If this is the case, the other grubs menus are never used and so not relevant. The other case is when one istalls grub on the root partition and then the mbr menu only send the pointer to each partition grub (at this moment you have two cascading grub menus) Actually it is not a partition problem but
one of having two instances of 10.2 installed -unintentionally.
/dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part5 /backup ext3 defaults 1 2
As you can see the new way of naming disks in fstab is just done for such situation. It makes it easy to see what disk is involved. It's pretty difficult to make this by hand, but yast do it for you.So you better stay with the 10.3 grub menu and yast partitionner.
I want to keep my SUSE (10.2)
do you need only 10.2, 10.3 and windows? if the 3 boot correctly, keep using 10.3 grub and comment out the unused grub entries.
The partitioner will show the setup clearly.
why would you install the 11 if your computer behave well with the previous ones? anyway if the partitionner behave clearly, go on. do not remove anything in the partition before being really sure you don't have the same data mounted twice :-) jdd (and remember new sata driver can only cope with 16 partitions) -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2008/04/03 09:32 (GMT+0200) jdd sur free apparently typed:
(and remember new sata driver can only cope with 16 partitions)
14 actually if the relevant number is places that provide homes for filesystems. Count is from 0-15, of which one of 1-4 is the extended, which can not contain a filesystem, and 0 is the whole physical device. -- "Either the constitution controls the judges, or the judges rewrite the constitution." Judge Robert Bork Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-04-03 at 07:09 -0400, Felix Miata wrote:
On 2008/04/03 09:32 (GMT+0200) jdd sur free apparently typed:
(and remember new sata driver can only cope with 16 partitions)
14 actually if the relevant number is places that provide homes for filesystems. Count is from 0-15, of which one of 1-4 is the extended, which can not contain a filesystem, and 0 is the whole physical device.
Exactly. Number 0 represents the whole disk. One is lost to the extend container partition (sda4 in Bob's case), so the maximun is 14 usable partitions, and all primaries have to be used (contrary to the typical usage of using 1 primary, 1 extended, the rest logical). (Mmmm... I need more coffee, I said the same thing in other words... never mind) He has a lot of free space and only three partitions available more to make. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH9MhutTMYHG2NR9URAtzeAJ9INHsKKMBoMxDkhUTh7j+N2+F7dgCdG5fU N/srfvKa+dHVUMRSCcwEeEc= =ENJK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 03 April 2008 03:32:08 am jdd sur free wrote:
Bob S a écrit :
Hello SuSE users,
Going to need a guru for this one.
I think I was for the old naming sheme, not so for the new :-(.
But what I don't see in your mail is the booting sequence...
you can boot of many ways, in Linux. most of the time, when using YaST defaults, grub is written in the MBR (master of the first disk) and so the last openSUSE install rules all the booting system.
Yes. I have always used the Yast defaults.
If this is the case, the other grubs menus are never used and so not relevant.
Well yes, I hear what you are saying but I do have the cascading menu. I will attach the 10.3 grub menu when I reply to Carlos's lengthy analysis.
The other case is when one istalls grub on the root partition and then the mbr menu only send the pointer to each partition grub (at this moment you have two cascading grub menus)
Actually it is not a partition problem but
one of having two instances of 10.2 installed -unintentionally.
/dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part5 /backup ext3 defaults 1 2
As you can see the new way of naming disks in fstab is just done for such situation. It makes it easy to see what disk is involved. It's pretty difficult to make this by hand, but yast do it for you.So you better stay with the 10.3 grub menu and yast partitionner.
I want to keep my SUSE (10.2)
do you need only 10.2, 10.3 and windows? if the 3 boot correctly, keep using 10.3 grub and comment out the unused grub entries.
No, as above clicking on 10.2 in the 10.3 grub menu opens the second menu where I can choose between the two 10.2 versions
The partitioner will show the setup clearly.
why would you install the 11 if your computer behave well with the previous ones?
I just like to try out the new releases after they are somewhat stable.
anyway if the partitionner behave clearly, go on. do not remove anything in the partition before being really sure you don't have the same data mounted twice :-)
jdd (and remember new sata driver can only cope with 16 partitions)
Yeah, I know, 14 actually. That is why I, Carlos and others complained so bitterly when they did that. Supposed to be a work around but hasn't happened yet. Take a look at my reply to Carlos. Bob S. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S a écrit :
No, as above clicking on 10.2 in the 10.3 grub menu opens the second menu where I can choose between the two 10.2 versions
you ca still use 10.3 yast to have direct loading of the other distros. what you can make is to write some text on the root of *any partition* with the expected content of this partition (for example: "Root 10.3* *home 10.2 a", it's enough to create (as root) an empty text file with the relevant name. so, whatever the system name the partition you know what *you* want it to be jdd -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-04-02 at 21:58 -0400, Bob S wrote: ...
I then bought a 250 GB sata drive to install 10.3 on as I wanted to keep 10.2 on hdb and all of the storage on the hda drive. 10.3 installed flawlessly on the saata drive. However after booting 10.3 a couple of times I decided to copy over some of my stuff from the 10.2 install. To my amazement, when I clicked on 10.2 in the grub menu, it brought up another grub menu with two instances of 10.2. Each of them booted and opened up. One instance was complete and performed perfectly the other opened and looked fine. Same desktop schemes etc. as the good one. But none of my /home info was there and It would not open any of the apps I had installed, would not print, etc. etc.
Another install you forgot about, probably.
Now, when I installed 10.3 the libata thing came into play. It made the new sata disk sda. then it took the ide disks and renamed hda to sdb and the hdb disk and renamed it sdc. (I complained bitterly to the list but it made no difference)
No... One thing that helps is to have all partitions "labeled". Some of your old partitions have labels, but not the new ones in the new disk.
So now I look at the grub menu.lst for both instances of 10.2 and they are exactly the same. NOTE: I renamed the good 10.2 to plain "SUSE" for clarity and so I could choose the proper instance from the second grub menu. Following is the grub menu:
We'd need to look at the big disk grub, too (the 10.3 system). Boot your 10.3, and copy-paste the /boot/grub/menu.lst file and the /boot/grub/device.map file. Then boot each 10.2 and do the same.
-------------------------------- # Modified by YaST2. Last modification on Tue Sep 18 19:13:07 EDT 2007 default 0 timeout 8 gfxmenu (hd1,0)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd
title SUSE root (hd2,0) kernel /boot/vmlinuz root=/dev/sda1 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd
I think you have 10.3 in sda8, and a 10.2 in sda1 (big disk).
----------------------------------------------- Note that root is different between SUSE and SUSE 10.2. Also, /dev/sda1 should actually be 10.3 ( I think) So now I look at the fstab for both. They are quite different. Following is for the good instance designated SUSE ----------------------------------------------- /dev/sda1 / ext3 acl,user_xattr 1 1 /dev/sda7 /fat vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/sda2 /home ext3 acl,user_xattr 1 2 /dev/sda6 /tmp ext3 acl,user_xattr 1 2 /dev/sda5 /var ext3 acl,user_xattr 1 2 /dev/sda3 swap swap defaults 0 0
This is 10.2 in /dev/sda1, I think.
/dev/hda2 /workspace ext3 user,acl 1 2 /dev/hda3 /datastorage ext3 defaults 1 2
That's /dev/sdb in the photo.
/dev/hda1 /windows vfat
/dev/hdb1 /boot ext3 acl,user_xattr 1 0
This could be... ugh! ... could be /dev/sdc1 in the photo. That's a 10 GB partition dedicated to /boot of your 10.2 system in /dev/sda1 !
----------------------------------------------------------------------------------------- BUT....Look at the first 5 lines. They say /dev/sda*. That can't be, /dev/sda is SUSE 10.3. So now I look at the fstab for 10.3 and I get this unintelligible mess: ---------------------------------------------------------------
Yes, sda1 is 10.2, and sda8 is 10.3. Not what you expected. Somehow you have a 10.2 (and a 10.3) in your new disk, and another 10.2 in your old disk.
/dev/sda8 / ext3 acl,user_xattr 1 1 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part5 /backup ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part3 /datastorage ext3
----------------------------------------------------------------------------------- So continuing on: The following is for the bogus SUSE 10.2 But it looks like it should except that the LVM's don't show. There is however a ~fstab which does show the LVM's. -----------------------------------------------------------------------------------------
I know nothing about LVM, sorry.
/dev/hdb1 / ext3 acl,user_xattr 1 1
This is sdc in the photo.
/dev/hdb2 /home ext3 acl,user_xattr 1 2 /dev/hdb7 /opt ext3 acl,user_xattr 1 2 /dev/hdb8 /tmp ext3 acl,user_xattr 1 2 /dev/hdb5 /usr ext3 acl,user_xattr 1 2 /dev/hdb6 /var ext3 acl,user_xattr 1 2 /dev/hda1 /windows/C vfat
because the fat partition is in sdb. So, the "bogus" 10.2 is really your old 10.2, broken because the LVM is not active, probably.
users,gid=users,umask=0002,utf8=true 0 0 /dev/sda7 /windows/D vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/sda3 swap swap defaults 0 0
So, sda here is also sda in the photo.
So now I look at my partitioner and of course there is no hda or hdb but it does seem to reflect the partitioning accurately. But no LVM and no explanation for the dual appearances of 10.2. I have attached the screen shot of the partitioner. Hopefully it will survive the censors. If not I can put it up on the web for viewing if anyone wants to see it.
Got ok. I think some "ghost fairy" cloned your lvm 10.2 into your new SATA drive, disabled the lvm, reconstructed the fstab the "bogus" 10.2 (thus the references to sda there), and installed 10.3 in the SATA (big disk).
I want to keep my SUSE (10.2) and get rid of the bogus SUSE 10.2 because it is solid and complete. Better yet it would be great to get everything in one single grub menu before I install 11.0. I have no idea on how to proceed,or to delete what partitions because libata changed all of the names. The partitioner will show the setup clearly.
Hopefully the guru's out there can analyze this and come up with a solution
You need a good one! You have over 100 GB not partitioned in your big disk, you can use that to move over things and repartition your old disks fresh. A proposal about what you can actually do... dunno, not yet. Let's wait for more comments. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH9NmntTMYHG2NR9URAr+KAJ98PEbh6gzLn3UCHEXuMidmDniuigCfTcCl z/TThOoSn8otoXv4wxbhH+0= =U3bL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. a écrit :
Another install you forgot about, probably.
good idea. YaST may have found an old install forgotten... may be done long time ago jdd -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 03 April 2008 09:20:32 am Carlos E. R. wrote:
The Wednesday 2008-04-02 at 21:58 -0400, Bob S wrote:
...
I then bought a 250 GB sata drive to install 10.3 on as I wanted to keep 10.2 on hdb and all of the storage on the hda drive. 10.3 installed flawlessly on the saata drive. However after booting 10.3 a couple of times I decided to copy over some of my stuff from the 10.2 install. To my amazement, when I clicked on 10.2 in the grub menu, it brought up another grub menu with two instances of 10.2. Each of them booted and opened up. One instance was complete and performed perfectly the other opened and looked fine. Same desktop schemes etc. as the good one. But none of my /home info was there and It would not open any of the apps I had installed, would not print, etc. etc.
Another install you forgot about, probably.
No, only one 10.2 was installed on hdb. And that waas done long before I bought the sata drive to install 10.3 on
Now, when I installed 10.3 the libata thing came into play. It made the new sata disk sda. then it took the ide disks and renamed hda to sdb and the hdb disk and renamed it sdc. (I complained bitterly to the list but it made no difference)
No...
One thing that helps is to have all partitions "labeled". Some of your old partitions have labels, but not the new ones in the new disk.
Yes, that is so true, What is it they say? "spilt milk" , "water over the dam" ?
So now I look at the grub menu.lst for both instances of 10.2 and they are exactly the same. NOTE: I renamed the good 10.2 to plain "SUSE" for clarity and so I could choose the proper instance from the second grub menu. Following is the grub menu:
We'd need to look at the big disk grub, too (the 10.3 system).
Boot your 10.3, and copy-paste the /boot/grub/menu.lst file and the /boot/grub/device.map file. Then boot each 10.2 and do the same.
OK, here is the 10.3 grub menu and the device map file: ---------------------------------------------------------------------------- # Modified by YaST2. Last modification on Wed Feb 13 00:32:30 EST 2008 default 0 timeout 8 gfxmenu (hd2,7)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.3 - 2.6.22.17-0.1 root (hd2,7) kernel /boot/vmlinuz-2.6.22.17-0.1-default root=/dev/sda8 vga=0x31a resume=/dev/sda3 splash=silent showopts initrd /boot/initrd-2.6.22.17-0.1-default ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.3 - 2.6.22.17-0.1 root (hd2,7) kernel /boot/vmlinuz-2.6.22.17-0.1-default root=/dev/sda8 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd-2.6.22.17-0.1-default ###Don't change this comment - YaST2 identifier: Original name: openSUSE 10.2 (/dev/sdc1)### title openSUSE 10.2 (/dev/sdc1) root (hd1,0) configfile /boot/grub/menu.lst ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd2,7) chainloader (hd0,0)+1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd2,7) chainloader (fd0)+1 ----------------------------------------------- (fd0) /dev/fd0 (hd2) /dev/sda (hd1) /dev/sdc (hd0) /dev/sdb ----------------------------------------------------- OK, here is the menu.lst for both of the 10.2's The good working one and the "bogus" not working one. They are the same. -------------------------------------------------------------------------- # Modified by YaST2. Last modification on Tue Sep 18 19:13:07 EDT 2007 default 0 timeout 8 gfxmenu (hd1,0)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd title SUSE root (hd2,0) kernel /boot/vmlinuz root=/dev/sda1 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.2 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd title Windows rootnoverify (hd0,0) chainloader (hd0,0)+1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,0) chainloader (fd0)+1 -------------------------------------------------------------------------- That certainly does look like there are two copies. (hd1.0 & hd2.0) OK ,again, both of them are exactly the same. -------------------------------------------------------- (hd1) /dev/hdb (fd0) /dev/fd0 (hd2) /dev/sda (hd0) /dev/hda ---------------------------------------------------------- OK....Where were we? So confusing. Continuing on. Would love to trim some of this stuff but I don't know what.
-------------------------------- # Modified by YaST2. Last modification on Tue Sep 18 19:13:07 EDT 2007 default 0 timeout 8 gfxmenu (hd1,0)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd
title SUSE root (hd2,0) kernel /boot/vmlinuz root=/dev/sda1 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd
I think you have 10.3 in sda8, and a 10.2 in sda1 (big disk).
Ohhhh Carlos. you may be right, but how can that be ??? The partitioning looks right and if Yast did that wouldn't there be a lot of used disk space?
----------------------------------------------- Note that root is different between SUSE and SUSE 10.2. Also, /dev/sda1 should actually be 10.3 ( I think) So now I look at the fstab for both. They are quite different. Following is for the good instance designated SUSE ----------------------------------------------- /dev/sda1 / ext3 acl,user_xattr 1 1 /dev/sda7 /fat vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/sda2 /home ext3 acl,user_xattr 1 2 /dev/sda6 /tmp ext3 acl,user_xattr 1 2 /dev/sda5 /var ext3 acl,user_xattr 1 2 /dev/sda3 swap swap defaults 0 0
This is 10.2 in /dev/sda1, I think.
Oh I hope not. Thaat would be a real mess
/dev/hda2 /workspace ext3 user,acl 1 2 /dev/hda3 /datastorage ext3 defaults 1 2
That's /dev/sdb in the photo.
Yes, because libata changed hda to sdb
/dev/hda1 /windows vfat
/dev/hdb1 /boot ext3 acl,user_xattr 1 0
This could be... ugh! ... could be /dev/sdc1 in the photo. That's a 10 GB partition dedicated to /boot of your 10.2 system in /dev/sda1 !
Yes, because hdb1 was the original / (boot) for 10.2. libata changed it. FYI I never make a /boot partition but I do make a large / primary partition for growth and new things.
------------------------------------------------------------------------- ---------------- BUT....Look at the first 5 lines. They say /dev/sda*. That can't be, /dev/sda is SUSE 10.3. So now I look at the fstab for 10.3 and I get this unintelligible mess: ---------------------------------------------------------------
Yes, sda1 is 10.2, and sda8 is 10.3. Not what you expected.
Certainly not
Somehow you have a 10.2 (and a 10.3) in your new disk, and another 10.2 in your old disk.
Ohhh Carlos, I wish you to be wrong. How can that happen? Wouldn't the partitions be filled up with all of the 10.2 stuff?
/dev/sda8 / ext3 acl,user_xattr 1 1 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part5 /backup ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part3 /datastorage ext3
------------------------------------------------------------------------- ---------- So continuing on: The following is for the bogus SUSE 10.2 But it looks like it should except that the LVM's don't show. There is however a ~fstab which does show the LVM's. -------------------------------------------------------------------------
I know nothing about LVM, sorry.
No problem. Evidently neither do I.
/dev/hdb1 / ext3 acl,user_xattr 1 1
This is sdc in the photo.
Yes, because again, libata changed hdb to sdc.
/dev/hdb2 /home ext3 acl,user_xattr 1 2 /dev/hdb7 /opt ext3 acl,user_xattr 1 2 /dev/hdb8 /tmp ext3 acl,user_xattr 1 2 /dev/hdb5 /usr ext3 acl,user_xattr 1 2 /dev/hdb6 /var ext3 acl,user_xattr 1 2 /dev/hda1 /windows/C vfat
The /home, /opt, /tmp, /usr, and /var, were the original LVM partitions on 10.2 in the original hdb
because the fat partition is in sdb.
The original fat partition was on hdb ?. A common fat file to save stuff to from both os's. ( I think) But it wasn't an LVM. Just a part of /
So, the "bogus" 10.2 is really your old 10.2, broken because the LVM is not active, probably.
I hope not but I am beginning to think you are right. How am I ever going to fix that? Suppose I could fix my original hdb (now sdc) and restore the LVM's somehow? What would I do then with the now new "bogus" 10.2 on sda?
users,gid=users,umask=0002,utf8=true 0 0 /dev/sda7 /windows/D vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/sda3 swap swap defaults 0 0
So, sda here is also sda in the photo
I guess. So confused now I don't know what to think.
So now I look at my partitioner and of course there is no hda or hdb but it does seem to reflect the partitioning accurately. But no LVM and no explanation for the dual appearances of 10.2. I have attached the screen shot of the partitioner. Hopefully it will survive the censors. If not I can put it up on the web for viewing if anyone wants to see it.
Got ok.
Good, one less small problem.
I think some "ghost fairy" cloned your lvm 10.2 into your new SATA drive, disabled the lvm, reconstructed the fstab the "bogus" 10.2 (thus the references to sda there), and installed 10.3 in the SATA (big disk).
Oh Carlos, you may be right. That means everything is screwed up. Both 10.2 and 10.3. Start all over again? Why?? Because some hair-brained idea that this would be a good thing to do? Without any thought of the consequences? No doubt in my mind that the change to libata caused this mess. The dev's just foisted this upon us without any thought or consideration of the consequences it may cause. Tough cookies guys. Live with it. I sincerely hope that it did not cause you the problems it has me. I know that you run several different releases concurrently. Maybe your saving grace was that you don't use LVM's.
I want to keep my SUSE (10.2) and get rid of the bogus SUSE 10.2 because it is solid and complete. Better yet it would be great to get everything in one single grub menu before I install 11.0. I have no idea on how to proceed,or to delete what partitions because libata changed all of the names. The partitioner will show the setup clearly.
Hopefully the guru's out there can analyze this and come up with a solution
You need a good one!
So far you are the best. I wish that the others would take the time and energy to right a wrong and speak out about it.
You have over 100 GB not partitioned in your big disk, you can use that to move over things and repartition your old disks fresh.
I'm sure you know what that entails. Hours and hours of uneccesary work just to get back to where you were originally. Why? For some stupid decision that is ambiguous at best.
A proposal about what you can actually do... dunno, not yet. Let's wait for more comments.
I certainly hope they are forthcoming.
Cheers, Carlos E. R.
Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
Hello SuSE users,
Going to need a guru for this one. Actually it is not a partition problem but one of having two instances of 10.2 installed -unintentionally. One instance is complete and working. The other is incomplete and missing apps, The only way to demonstrate this is through the partitioning scheme.
First you need the background. Sorry, but it is the only way to understand. I originally had two ide hard drives, hda of 80GB and hdb of 30GB. I put a 5GB partition for Windows on hda. The rest of the drive is ext3 which is used for datastorage, storage, backup and workspace.
hdb (30GB) was used strictly for 10.2 and utilized LVM partitioning, That drive previously had 9.3 and 10.0 on it. New installs each time. Worked fine - no problems whatsoever as did 10.2.
I then bought a 250 GB sata drive to install 10.3 on as I wanted to keep 10.2 on hdb and all of the storage on the hda drive. 10.3 installed flawlessly on the saata drive. However after booting 10.3 a couple of times I decided to copy over some of my stuff from the 10.2 install. To my amazement, when I clicked on 10.2 in the grub menu, it brought up another grub menu with two instances of 10.2. Each of them booted and opened up. One instance was complete and performed perfectly the other opened and looked fine. Same desktop schemes etc. as the good one. But none of my /home info was there and It would not open any of the apps I had installed, would not print, etc. etc.
Now, when I installed 10.3 the libata thing came into play. It made the new sata disk sda. then it took the ide disks and renamed hda to sdb and the hdb disk and renamed it sdc. (I complained bitterly to the list but it made no difference)
So now I look at the grub menu.lst for both instances of 10.2 and they are exactly the same. NOTE: I renamed the good 10.2 to plain "SUSE" for clarity and so I could choose the proper instance from the second grub menu. Following is the grub menu: -------------------------------- # Modified by YaST2. Last modification on Tue Sep 18 19:13:07 EDT 2007 default 0 timeout 8 gfxmenu (hd1,0)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd
title SUSE root (hd2,0) kernel /boot/vmlinuz root=/dev/sda1 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd
###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.2 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd
title Windows rootnoverify (hd0,0) chainloader (hd0,0)+1
###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,0) chainloader (fd0)+1 ----------------------------------------------- Note that root is different between SUSE and SUSE 10.2. Also, /dev/sda1 should actually be 10.3 ( I think) So now I look at the fstab for both. They are quite different. Following is for the good instance designated SUSE ----------------------------------------------- /dev/sda1 / ext3 acl,user_xattr 1 1 /dev/sda7 /fat vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/sda2 /home ext3 acl,user_xattr 1 2 /dev/sda6 /tmp ext3 acl,user_xattr 1 2 /dev/sda5 /var ext3 acl,user_xattr 1 2 /dev/sda3 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/hda2 /workspace ext3 user,acl 1 2 /dev/hda3 /datastorage ext3 defaults 1 2 /dev/hda1 /windows vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/hda5 /backup ext3 acl,user_xattr 1 2 /dev/hda6 /storage ext3 acl,user_xattr 1 2 /dev/hda7 /mediadata ext3 noauto,acl,user_xattr 1 2 /dev/hdb1 /boot ext3 acl,user_xattr 1 0 /dev/hdc /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/hdd /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 ----------------------------------------------------------------------------------------- BUT....Look at the first 5 lines. They say /dev/sda*. That can't be, /dev/sda is SUSE 10.3. So now I look at the fstab for 10.3 and I get this unintelligible mess:
--------------------------------------------------------------- /dev/sda8 / ext3 acl,user_xattr 1 1 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part5 /backup ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part3 /datastorage ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part9 /home ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part7 /mediadata ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part6 /storage ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part10 /tmp ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part12 /usr ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part11 /var ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part2 /workspace ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part3 swap swap defaults 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 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part1 /windows vfat users,gid=users,umask=0002,utf8=true 0 0 -----------------------------------------------------------------------------------
Why did you choose "mount by DISK-ID" for the non-removable disks, instead of something that is readable, such as "mount by LABEL"??? C'mon, Bob... I know you're smart enough to make the logical choice. "Mount by DISK-ID can good for removable media, but just makes a mess of things for disks which don't go anywhere.
So continuing on: The following is for the bogus SUSE 10.2 But it looks like it should except that the LVM's don't show. There is however a ~fstab which does show the LVM's. ----------------------------------------------------------------------------------------- /dev/hdb1 / ext3 acl,user_xattr 1 1 /dev/hdb2 /home ext3 acl,user_xattr 1 2 /dev/hdb7 /opt ext3 acl,user_xattr 1 2 /dev/hdb8 /tmp ext3 acl,user_xattr 1 2 /dev/hdb5 /usr ext3 acl,user_xattr 1 2 /dev/hdb6 /var ext3 acl,user_xattr 1 2 /dev/hda1 /windows/C vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/sda7 /windows/D vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/sda3 swap swap defaults 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 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 --------------------------------------------------------------------------------------------- So now I look at my partitioner and of course there is no hda or hdb but it does seem to reflect the partitioning accurately. But no LVM and no explanation for the dual appearances of 10.2. I have attached the screen shot of the partitioner. Hopefully it will survive the censors. If not I can put it up on the web for viewing if anyone wants to see it.
I want to keep my SUSE (10.2) and get rid of the bogus SUSE 10.2 because it is solid and complete. Better yet it would be great to get everything in one single grub menu before I install 11.0. I have no idea on how to proceed,or to delete what partitions because libata changed all of the names. The partitioner will show the setup clearly.
Hopefully the guru's out there can analyze this and come up with a solution
------------------------------------------------------------------------
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-04-04 at 20:22 -0400, Sam Clemens wrote: ...
Why did you choose "mount by DISK-ID" for the non-removable disks, instead of something that is readable, such as "mount by LABEL"???
Because it is the default, for good reasons. I prefer labels, but that needs a decision on the user part. Actually, the disk id contains the disk model name, and partition number, so they are easy to identify uniquely. It's the best thing when device names can not be used anymore that can be used automatically. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH9tQvtTMYHG2NR9URAiioAJ9h30zbvQq5Zku3ioQyN1JefY64TQCfZgcr 0ybtzw78B4IELPH/mu8U/fE= =iqe7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 04 April 2008 08:22:50 pm Sam Clemens wrote:
Bob S wrote:
Hello SuSE users,
Going to need a guru for this one. Actually it is not a partition problem but one of having two instances of 10.2 installed -unintentionally. One instance is complete and working. The other is incomplete and missing apps, The only way to demonstrate this is through the partitioning scheme.
First you need the background. Sorry, but it is the only way to understand. I originally had two ide hard drives, hda of 80GB and hdb of 30GB. I put a 5GB partition for Windows on hda. The rest of the drive is ext3 which is used for datastorage, storage, backup and workspace.
hdb (30GB) was used strictly for 10.2 and utilized LVM partitioning, That drive previously had 9.3 and 10.0 on it. New installs each time. Worked fine - no problems whatsoever as did 10.2.
I then bought a 250 GB sata drive to install 10.3 on as I wanted to keep 10.2 on hdb and all of the storage on the hda drive. 10.3 installed flawlessly on the saata drive. However after booting 10.3 a couple of times I decided to copy over some of my stuff from the 10.2 install. To my amazement, when I clicked on 10.2 in the grub menu, it brought up another grub menu with two instances of 10.2. Each of them booted and opened up. One instance was complete and performed perfectly the other opened and looked fine. Same desktop schemes etc. as the good one. But none of my /home info was there and It would not open any of the apps I had installed, would not print, etc. etc.
Now, when I installed 10.3 the libata thing came into play. It made the new sata disk sda. then it took the ide disks and renamed hda to sdb and the hdb disk and renamed it sdc. (I complained bitterly to the list but it made no difference)
So now I look at the grub menu.lst for both instances of 10.2 and they are exactly the same. NOTE: I renamed the good 10.2 to plain "SUSE" for clarity and so I could choose the proper instance from the second grub menu. Following is the grub menu: -------------------------------- # Modified by YaST2. Last modification on Tue Sep 18 19:13:07 EDT 2007 default 0 timeout 8 gfxmenu (hd1,0)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd
title SUSE root (hd2,0) kernel /boot/vmlinuz root=/dev/sda1 resume=/dev/sda3 splash=silent showopts initrd /boot/initrd
###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.2 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd
title Windows rootnoverify (hd0,0) chainloader (hd0,0)+1
###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,0) chainloader (fd0)+1 ----------------------------------------------- Note that root is different between SUSE and SUSE 10.2. Also, /dev/sda1 should actually be 10.3 ( I think) So now I look at the fstab for both. They are quite different. Following is for the good instance designated SUSE ----------------------------------------------- /dev/sda1 / ext3 acl,user_xattr 1 1 /dev/sda7 /fat vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/sda2 /home ext3 acl,user_xattr 1 2 /dev/sda6 /tmp ext3 acl,user_xattr 1 2 /dev/sda5 /var ext3 acl,user_xattr 1 2 /dev/sda3 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/hda2 /workspace ext3 user,acl 1 2 /dev/hda3 /datastorage ext3 defaults 1 2 /dev/hda1 /windows vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/hda5 /backup ext3 acl,user_xattr 1 2 /dev/hda6 /storage ext3 acl,user_xattr 1 2 /dev/hda7 /mediadata ext3 noauto,acl,user_xattr 1 2 /dev/hdb1 /boot ext3 acl,user_xattr 1 0 /dev/hdc /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/hdd /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 ------------------------------------------------------------------------- ---------------- BUT....Look at the first 5 lines. They say /dev/sda*. That can't be, /dev/sda is SUSE 10.3. So now I look at the fstab for 10.3 and I get this unintelligible mess:
--------------------------------------------------------------- /dev/sda8 / ext3 acl,user_xattr 1 1 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part5 /backup ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part3 /datastorage ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part9 /home ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part7 /mediadata ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part6 /storage ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part10 /tmp ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part12 /usr ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part11 /var ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part2 /workspace ext3 defaults 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part3 swap swap defaults 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 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/disk/by-id/scsi-SATA_ST380011A_5JVQS2KB-part1 /windows vfat users,gid=users,umask=0002,utf8=true 0 0 ------------------------------------------------------------------------- ----------
Why did you choose "mount by DISK-ID" for the non-removable disks, instead of something that is readable, such as "mount by LABEL"???
C'mon, Bob... I know you're smart enough to make the logical choice.
Well, that's just it. I didn't. Yast did it. Just like it blew away the LVM's on the old install on the older disk. That wasn't in there when I clicked the "accept" button on the partitioner And I DO check that very carefully before I do that. It still showed the hda and the hdb drives and there was no dialogue about those changes. Wish I had another setup so I could reproduce this.
"Mount by DISK-ID can good for removable media, but just makes a mess of things for disks which don't go anywhere.
..............< snip all of the rest>................ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Bob S -
Carlos E. R. -
Felix Miata -
jdd sur free -
Sam Clemens