Re: [DNG] ascii 2.0 installation confused by mount points
On Mon, Jun 11, 2018 at 07:16:52AM +0200, Didier Kryn wrote: > > If you want to share a partition (say home) between different OSes, > then, of course you have to mention it, but it's not recommendable because > config files of several applications are not backward compatible between > versions. Also private applications using dynamically linked libraries might > not find the proper version of the libraries. But of course, it is > convenient to mount the old home from another disk to copy it to the new one > to start from. I usually share /var/mail between releases. It seems to be compatible between releases (at least it has been for more than a decade), and this keeps mail from getting lost by arriving when the wrong release is in use. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
Le 10/06/2018 à 14:55, Haines Brown a écrit : On Sun, Jun 10, 2018 at 10:05:48AM +0200, Didier Kryn wrote: Le 10/06/2018 à 04:01, Haines Brown a écrit : On Sat, Jun 09, 2018 at 10:36:46PM +0100, Simon Hobson wrote: Haines Brown wrote: In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a primary partition that is bootable and the mount point /. You probably want to set this partition to unused (or whatever it's called, it's a looong time since I last did this) so that it doesn't appear in the mount point table (eventually in fstab of the new install). I think what you are telling it is that you want sda1 to mounted as / IN THIS INSTALLATION and that then clashes with your new / (on sdc) that you're trying to install to. In the partitionner (which is not only a partitionner, but generates the fstab and the filesystems), you should select "dont use the partition"on every partition which is not in sdc. Click on "use partition as" and select "dont use the partition". Didier, that seems to have done the trick. I apologize for having been too hasty. Where the partitioner asks what to use a partition as, because the top options were simply file systems, I interpreted it to be merely for selecting file system and did not notice the "don't use" option at the bottom. When I marked sda partitions not to be used, I was able to save the sdc partition table and proceed with the installation. Now that installation of ascii 2.0 on sdc is underway and before going further I must figure out how to recover a use of partitions on sda. I assume that were I to use the menu to revert to partitioning and restore usage of sda partitions I'll just end up with the same problem of a competition of sda and sdc for use of /. When I execute a shell toward the end of installation, can I use it to run the command "parted /dev/sda set 1 boot on" both to enable sda1 and to make it bootable at the same time? Would the command "parted /dev/sda set 2 on" simply re-enable the second partition? I found the parted manual unclear on this point. I guess you don't want to use sda from your sdc OS. Therefore don't do anything more. When you boot the OS on sda, then, this one won't use sdc. And vice-versa. Isn't this what you want? Or do you haved changed the partition table on sda, or erased some partitions there which you want to recover? This can be difficult. If you want to share a partition (say home) between different OSes, then, of course you have to mention it, but it's not recommendable because config files of several applications are not backward compatible between versions. Also private applications using dynamically linked libraries might not find the proper version of the libraries. But of course, it is convenient to mount the old home from another disk to copy it to the new one to start from. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
Le 10/06/2018 à 16:08, Rowland Penny a écrit : On Sun, 10 Jun 2018 08:55:55 -0400 Haines Brown wrote: When I execute a shell toward the end of installation, can I use it to run the command "parted /dev/sda set 1 boot on" both to enable sda1 and to make it bootable at the same time? Would the command "parted /dev/sda set 2 on" simply re-enable the second partition? I found the parted manual unclear on this point. I am fairly sure you will need to set up grub2 to do this, try reading this: https://unix.stackexchange.com/questions/252936/grub2-boot-to-a-second-another-hard-disk Or failing that, google for the answer ;-) When your installation is almost finished, one of thevery last steps is installing the Grub bootloader. Just do it: it will automatically detect all OSes on all disks (which don't need to be mounted in any way), and generate a boot list which enables all them. You will have the currently installed OS on top of the list, then a rescue mode for this OS, then all the other detected OSes. You decide on which disk you want to install the Grub bootloader. I suggest you install it on all disks as explained below. You can install the Grub bootloader on other disks as well, either by re-running the bootloader installation step (I didn't check but I don't see why it would fail), or by invoking install-grub from the command-line (install-grub /dev/sda; install-grub /dev/sdb; etc..). Grub does not use internally the device names sda2, sdb1 sdc5, etc... but the UUIDs of the partitions to boot from, therefore you can permute your disks as you like if you have installed the bootloader on all of them. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On 2018-06-10 17:31, Renaud (Ron) OLGIATI wrote: On Sun, 10 Jun 2018 12:45:36 -0500 goli...@dyne.org wrote: > Just have to keep a post-it on the monitor, to remind you which HD has > what ;-3) I actually keep a small sticky label on the drive itself. ;) Might not be very useful at boot time ;-3) Cheers, Ron. It does if you take a drive out for some reason or move drives around. ;) My gigabyte boards allow me to choose which drive I want to boot from a list that pops up with F12. golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, 10 Jun 2018 12:45:36 -0500 goli...@dyne.org wrote: > > Just have to keep a post-it on the monitor, to remind you which HD has > > what ;-3) > I actually keep a small sticky label on the drive itself. ;) Might not be very useful at boot time ;-3) Cheers, Ron. -- Television has proved that people will look at anything rather than each other. -- Ann Landers -- http://www.olgiati-in-paraguay.org -- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, 10 Jun 2018 15:08:31 +0100, Rowland wrote in message <20180610150831.64627...@devstation.samdom.example.com>: > https://unix.stackexchange.com/questions/252936/grub2-boot-to-a-second-another-hard-disk > > Or failing that, google for the answer ;-) ..https://www.dedoimedo.com/computers/grub-2.html has e.g. 8. GRUB 2 recovery A. Recover from failed boots -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, Jun 10, 2018 at 02:08:29PM -0400, Haines Brown wrote: > The suggestion to disconnect the sda drive while I install the same > version of the operating system on sdc occurred to me, but I worried > about the effect of the resulting change in drive designations. In my > case, by disconnecting sda my sdb becomes sda and my sdc becomes sdb. > Will all of this sort itself out when I reconnect the old sda drive and > boot it? After installing ascii on sdc I probably will have to select > sda as the drive to boot in BIOS and then run update-grub after it is > up. This is exactly why modern d-i and grub use those unsightly UUIDs instead of user-friendly "sda". You don't want the system to break just because you removed one of the disks, or this time one of them took a few seconds longer to spin up and thus lost a race. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts ⣾⠁⢰⠒⠀⣿⡁ productivity. You can read it, too, you just need the ⢿⡄⠘⠷⠚⠋⠀ right music while doing so. I recommend Skepticism ⠈⠳⣄ (funeral doom metal). ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, Jun 10, 2018 at 04:07:17PM +0100, Rowland Penny wrote: > What you are talking about doing is akin to dual-booting, just on > different disks i.e. you will only be able to boot one distro. > > Rowland Yes. In the past I've always had multiple hard drives in one machine, each with an operating system and its own boot menu. This because I've become paranoid over the years and always want the option of which drive on the machine to boot. I suspect, though, that these disks always had at least different versions of the operating system, and what I'm doing now is trying to install ascii 2.0 on a disk in a system that already has a disk with ascii-rc on it. Do you know if I wouldn't have had the problem had I tried to install devuan testing or experimental on sdc with ascii on sda? The suggestion to disconnect the sda drive while I install the same version of the operating system on sdc occurred to me, but I worried about the effect of the resulting change in drive designations. In my case, by disconnecting sda my sdb becomes sda and my sdc becomes sdb. Will all of this sort itself out when I reconnect the old sda drive and boot it? After installing ascii on sdc I probably will have to select sda as the drive to boot in BIOS and then run update-grub after it is up. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On 2018-06-10 11:07, Renaud (Ron) OLGIATI wrote: On Sun, 10 Jun 2018 10:48:28 -0500 goli...@dyne.org wrote: > A work-around for your problem: > Install each OS individually on a HD (disconnecting the other bootable > ones if need be) and install Grub on the mbr of that HD. > When booting, press F8 (or whichever your BIOS uses) to bring up the > Boot Menu, and choose there the HD you want to boot from. I have done exactly that more than once. No chance of an 'oops' when only one disk is available for install. Just make sure it's the disk you want to write to. Just have to keep a post-it on the monitor, to remind you which HD has what ;-3) Cheers, Ron. I actually keep a small sticky label on the drive itself. ;) golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, 10 Jun 2018 10:48:28 -0500 goli...@dyne.org wrote: > > A work-around for your problem: > > Install each OS individually on a HD (disconnecting the other bootable > > ones if need be) and install Grub on the mbr of that HD. > > When booting, press F8 (or whichever your BIOS uses) to bring up the > > Boot Menu, and choose there the HD you want to boot from. > I have done exactly that more than once. No chance of an 'oops' when > only one disk is available for install. Just make sure it's the disk > you want to write to. Just have to keep a post-it on the monitor, to remind you which HD has what ;-3) Cheers, Ron. -- Dieu créa l'homme, et ne le trouvant pas assez seul, il lui donna une compagne pour lui faire mieux sentir sa solitude. -- Paul Valéry -- http://www.olgiati-in-paraguay.org -- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On 2018-06-10 10:08, Renaud (Ron) OLGIATI wrote: A work-around for your problem: Install each OS individually on a HD (disconnecting the other bootable ones if need be) and install Grub on the mbr of that HD. When booting, press F8 (or whichever your BIOS uses) to bring up the Boot Menu, and choose there the HD you want to boot from. Cheers, Ron. I have done exactly that more than once. No chance of an 'oops' when only one disk is available for install. Just make sure it's the disk you want to write to. golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
A work-around for your problem: Install each OS individually on a HD (disconnecting the other bootable ones if need be) and install Grub on the mbr of that HD. When booting, press F8 (or whichever your BIOS uses) to bring up the Boot Menu, and choose there the HD you want to boot from. Cheers, Ron. -- All true wisdom is found in sig-files. -- http://www.olgiati-in-paraguay.org -- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, 10 Jun 2018 10:18:24 -0400 Haines Brown wrote: > On Sun, Jun 10, 2018 at 12:36:02PM +0100, Simon Hobson wrote: > > > I think you may be confused about what this section is doing. You > > are telling the installer a) what to do with a disk & it's > > partitions (eg, should it format a partition), and b) where they > > should be mounted. So for your partitions on sda, you tell it NOT > > to format them and not to mount them anywhere - I certainly recall > > those being options in the Debian installer, you may need to go > > into expert mode. Alternatively, tell the installer NOT to format > > them and set a different mount point > > (eg /jessie, /jessie/boot, ...) When you set a mount point, it's > > telling the installer two things : where to mount the filesystem > > during the install, and what to put in the installed system's > > fstab. If you tell it to do nothing with the partitions/filesystems > > on sda, then they will simply be left alone - but watch put for > > grub install later on, you don't want to damage the grub that's > > already installed. So don't format the partitions on sda, don't > > mount them anywhere, and you'll end up with a new install on sdc > > that just ignores the system already on sda - but as mentioned, be > > careful when it comes to grub install time. Then (I assume through > > the system BIOS) you'll be able to boot using the old system & it's > > grub on sda, or the new system & it's grub on sdc. > > Don't underestimate my ability to get confused, especially when a > practice I've followed for years no longer works. It may be the > difficulty arises now because two of the machine's disks are for ascii > (one rc and the other stable), and jessie is on sdb. Does the conflict > over use of \ only happen if operating system versions happen to be > the same? If so, I wonder if an expert installer could be warned of > this and what to do about it. For example, the error message that > pops up could be more informative. > > In the partitioner, when I go to edit a partition, one option is to > "use as:" If I specify to use as ext4, then the additional > settings become available of whether to format the partition and set > its mount point. If instead I chose "do not use", I no longer have the > option to format and define a mount point. > > That is as you say, but your comment about watching out for GRUB later > on in the installation worries me. You warn me that I should not allow > grub to "damage" (confuse?) the grub on sda, but the installer asks a > question that I do not find to be clear. When installing GRUB and > after the installer discovers what operating systems happen to be > accessible for the installation, it tells me it is safe to install > GRUB in the mbr of the first drive, which in my case is sda. My > intent is to leave GRUB as it is on sda and to install it instead on > sdc. However, it then asks whether to install it in the mbr. To which > drive does this refer? Is it asking if I want to install GRUB in the > mbr of the first drive, sda, or is it asking simply whether to > install GRUB the mbr on whatever drive I next install GRUB? > What you are talking about doing is akin to dual-booting, just on different disks i.e. you will only be able to boot one distro. Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, Jun 10, 2018 at 12:36:02PM +0100, Simon Hobson wrote: > I think you may be confused about what this section is doing. You are > telling the installer a) what to do with a disk & it's partitions (eg, > should it format a partition), and b) where they should be mounted. > So for your partitions on sda, you tell it NOT to format them and not > to mount them anywhere - I certainly recall those being options in the > Debian installer, you may need to go into expert mode. Alternatively, > tell the installer NOT to format them and set a different mount point > (eg /jessie, /jessie/boot, ...) When you set a mount point, it's > telling the installer two things : where to mount the filesystem > during the install, and what to put in the installed system's > fstab. If you tell it to do nothing with the partitions/filesystems on > sda, then they will simply be left alone - but watch put for grub > install later on, you don't want to damage the grub that's already > installed. So don't format the partitions on sda, don't mount them > anywhere, and you'll end up with a new install on sdc that just > ignores the system already on sda - but as mentioned, be careful when > it comes to grub install time. Then (I assume through the system > BIOS) you'll be able to boot using the old system & it's grub on sda, > or the new system & it's grub on sdc. Don't underestimate my ability to get confused, especially when a practice I've followed for years no longer works. It may be the difficulty arises now because two of the machine's disks are for ascii (one rc and the other stable), and jessie is on sdb. Does the conflict over use of \ only happen if operating system versions happen to be the same? If so, I wonder if an expert installer could be warned of this and what to do about it. For example, the error message that pops up could be more informative. In the partitioner, when I go to edit a partition, one option is to "use as:" If I specify to use as ext4, then the additional settings become available of whether to format the partition and set its mount point. If instead I chose "do not use", I no longer have the option to format and define a mount point. That is as you say, but your comment about watching out for GRUB later on in the installation worries me. You warn me that I should not allow grub to "damage" (confuse?) the grub on sda, but the installer asks a question that I do not find to be clear. When installing GRUB and after the installer discovers what operating systems happen to be accessible for the installation, it tells me it is safe to install GRUB in the mbr of the first drive, which in my case is sda. My intent is to leave GRUB as it is on sda and to install it instead on sdc. However, it then asks whether to install it in the mbr. To which drive does this refer? Is it asking if I want to install GRUB in the mbr of the first drive, sda, or is it asking simply whether to install GRUB the mbr on whatever drive I next install GRUB? Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, 10 Jun 2018 08:55:55 -0400 Haines Brown wrote: > On Sun, Jun 10, 2018 at 10:05:48AM +0200, Didier Kryn wrote: > > Le 10/06/2018 à 04:01, Haines Brown a écrit : > > >On Sat, Jun 09, 2018 at 10:36:46PM +0100, Simon Hobson wrote: > > >>Haines Brown wrote: > > >> > > >>>In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a > > >>>primary partition that is bootable and the mount point /. > > >>You probably want to set this partition to unused (or whatever > > >>it's > > > called, it's a looong time since I last did this) so that it > > > doesn't appear in the mount point table (eventually in fstab of > > > the new install). I think what you are telling it is that you > > > want sda1 to mounted as / IN THIS INSTALLATION and that then > > > clashes with your new / (on sdc) that you're trying to install to. > > > In the partitionner (which is not only a partitionner, but > > generates the fstab and the filesystems), you should select "dont > > use the partition" on every partition which is not in sdc. Click on > > "use partition as" and select "dont use the partition". > > Didier, that seems to have done the trick. I apologize for having been > too hasty. Where the partitioner asks what to use a partition as, > because the top options were simply file systems, I interpreted it to > be merely for selecting file system and did not notice the "don't > use" option at the bottom. When I marked sda partitions not to be > used, I was able to save the sdc partition table and proceed with the > installation. > > Now that installation of ascii 2.0 on sdc is underway and before going > further I must figure out how to recover a use of partitions on sda. I > assume that were I to use the menu to revert to partitioning and > restore usage of sda partitions I'll just end up with the same > problem of a competition of sda and sdc for use of /. > > When I execute a shell toward the end of installation, can I use it to > run the command "parted /dev/sda set 1 boot on" both to enable sda1 > and to make it bootable at the same time? Would the command > "parted /dev/sda set 2 on" simply re-enable the second partition? I > found the parted manual unclear on this point. > I am fairly sure you will need to set up grub2 to do this, try reading this: https://unix.stackexchange.com/questions/252936/grub2-boot-to-a-second-another-hard-disk Or failing that, google for the answer ;-) Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, Jun 10, 2018 at 10:05:48AM +0200, Didier Kryn wrote: > Le 10/06/2018 à 04:01, Haines Brown a écrit : > >On Sat, Jun 09, 2018 at 10:36:46PM +0100, Simon Hobson wrote: > >>Haines Brown wrote: > >> > >>>In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a primary > >>>partition that is bootable and the mount point /. > >>You probably want to set this partition to unused (or whatever it's > > called, it's a looong time since I last did this) so that it doesn't > > appear in the mount point table (eventually in fstab of the new > > install). I think what you are telling it is that you want sda1 to > > mounted as / IN THIS INSTALLATION and that then clashes with your new > > / (on sdc) that you're trying to install to. > In the partitionner (which is not only a partitionner, but generates the > fstab and the filesystems), you should select "dont use the partition" on > every partition which is not in sdc. Click on "use partition as" and > select "dont use the partition". Didier, that seems to have done the trick. I apologize for having been too hasty. Where the partitioner asks what to use a partition as, because the top options were simply file systems, I interpreted it to be merely for selecting file system and did not notice the "don't use" option at the bottom. When I marked sda partitions not to be used, I was able to save the sdc partition table and proceed with the installation. Now that installation of ascii 2.0 on sdc is underway and before going further I must figure out how to recover a use of partitions on sda. I assume that were I to use the menu to revert to partitioning and restore usage of sda partitions I'll just end up with the same problem of a competition of sda and sdc for use of /. When I execute a shell toward the end of installation, can I use it to run the command "parted /dev/sda set 1 boot on" both to enable sda1 and to make it bootable at the same time? Would the command "parted /dev/sda set 2 on" simply re-enable the second partition? I found the parted manual unclear on this point. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
Haines Brown wrote: >> You probably want to set this partition to unused (or whatever it's >> called, it's a looong time since I last did this) so that it doesn't >> appear in the mount point table (eventually in fstab of the new >> install). I think what you are telling it is that you want sda1 to >> mounted as / IN THIS INSTALLATION and that then clashes with your new >> / (on sdc) that you're trying to install to. > > In "typical usage:" option when configuring the root partition, there is > no option that would disable it. In any case, I don't want to disable > it, but to be able to boot any disk and use its grub menu to boot it or > any other disk. I've always been able to do that. I think you may be confused about what this section is doing. You are telling the installer a) what to do with a disk & it's partitions (eg, should it format a partition), and b) where they should be mounted. So for your partitions on sda, you tell it NOT to format them and not to mount them anywhere - I certainly recall those being options in the Debian installer, you may need to go into expert mode. Alternatively, tell the installer NOT to format them and set a different mount point (eg /jessie, /jessie/boot, ...) When you set a mount point, it's telling the installer two things : where to mount the filesystem during the install, and what to put in the installed system's fstab. If you tell it to do nothing with the partitions/filesystems on sda, then they will simply be left alone - but watch put for grub install later on, you don't want to damage the grub that's already installed. So don't format the partitions on sda, don't mount them anywhere, and you'll end up with a new install on sdc that just ignores the system already on sda - but as mentioned, be careful when it comes to grub install time. Then (I assume through the system BIOS) you'll be able to boot using the old system & it's grub on sda, or the new system & it's grub on sdc. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sat, Jun 09, 2018 at 10:36:46PM +0100, Simon Hobson wrote: > Haines Brown wrote: > > > In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a primary > > partition that is bootable and the mount point /. > You probably want to set this partition to unused (or whatever it's called, it's a looong time since I last did this) so that it doesn't appear in the mount point table (eventually in fstab of the new install). I think what you are telling it is that you want sda1 to mounted as / IN THIS INSTALLATION and that then clashes with your new / (on sdc) that you're trying to install to. In "typical usage:" option when configuring the root partition, there is no option that would disable it. In any case, I don't want to disable it, but to be able to boot any disk and use its grub menu to boot it or any other disk. I've always been able to do that. It occurs to me that I could simply disconnect the SATA cable from my sda and then partition sdc and after installation reconnect sda and run update-grub on the disks. But I hesitate to do it because then the sda/sdc identity of the disk would change and I might end up unable to boot either disk. Another approach might be to boot sda run fdisk on sdc and then do an installation on sdc without partitioning it. Incidentally, on sdb I have have installed an old Debian (Etch?). When I try to partition sdc it does not want to use its root partition. only the root partition of sda. I suspect something has changed between Jessie and Ascii. The partitioner in devuan install I suppose is parted, but not sure. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On 06/09/2018 01:13 PM, Haines Brown wrote: I'm installing ascii on a disk, sdc, in a machine that has two other disks, one of which, sda already has a bootable devuan jessie on it. The installation goes well until I go to write my partitioning of sdc to disk. I get the error message: "Two file systems are assigned to the same mount point (/): SCSII (0,0,0), partition #1 (sda) and SCSI3 (0,0,0), partition #1, (sdc). It is true that partition 1 of sda is a bootable primary partition, and I want to do the same for sdc. I've always had multiple independently bootable disks with their own GRUB on a machine. This is the first time I've run into trouble with it. In installation options for sdc, I did ask to have a MBR installed. Why does an installation on one disk care about what happens to be on another unmounted disk? You are using fstab and assigning the partitions how you want them to be used? -- Jimmy Johnson Devuan ASCII - TDE Trinity R14.0.5 - AMD A8-7600 - EXT4 at sda6 Registered Linux User #380263 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
Haines Brown wrote: > In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a primary > partition that is bootable and the mount point /. You probably want to set this partition to unused (or whatever it's called, it's a looong time since I last did this) so that it doesn't appear in the mount point table (eventually in fstab of the new install). I think what you are telling it is that you want sda1 to mounted as / IN THIS INSTALLATION and that then clashes with your new / (on sdc) that you're trying to install to. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sat, Jun 09, 2018 at 10:19:01PM +0200, Didier Kryn wrote: > Le 09/06/2018 à 22:13, Haines Brown a écrit : > >I'm installing ascii on a disk, sdc, in a machine that has two other disks, > >one of which, sda already has a bootable devuan jessie on it. > > > >The installation goes well until I go to write my partitioning of sdc to > >disk. I get the error message: "Two file systems are assigned to the same > >mount point (/): SCSII (0,0,0), partition #1 (sda) and SCSI3 (0,0,0), > >partition #1, (sdc). > > > >It is true that partition 1 of sda is a bootable primary partition, and > >I want to do the same for sdc. I've always had multiple independently > >bootable disks with their own GRUB on a machine. This is the first time > >I've run into trouble with it. In installation options for sdc, I did > >ask to have a MBR installed. > > > >Why does an installation on one disk care about what happens to be on > >another unmounted disk? > > First, check carefull y what you do in the partitionning dialog. sda > shouldn't be used at all by the system you install, but I suspect you have > maybe marked it as used in some way. Thanks, Didier, In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a primary partition that is bootable and the mount point /. When I edit this partition, it says it is on sda. Disk sdc is ST1000MN0011, and it also has a bootable partition #1. When I edit it, it says I'm editing disk ST1000MN0011 partition #1 of sdc. I give it / as mount point, make it bootable, and the label "root". Partition #1 on sda is has mount point /, the mount options I leave as the defaults, label I left out the label, but now label it "root". This should make no difference as far as I can see. I leave typical usage as "stardard". I don't know what standard options refers to, but I should think standard option would not cause this disk to interfere with others. But I get the error, "Identical mount points for two file systems." Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
Le 09/06/2018 à 22:13, Haines Brown a écrit : I'm installing ascii on a disk, sdc, in a machine that has two other disks, one of which, sda already has a bootable devuan jessie on it. The installation goes well until I go to write my partitioning of sdc to disk. I get the error message: "Two file systems are assigned to the same mount point (/): SCSII (0,0,0), partition #1 (sda) and SCSI3 (0,0,0), partition #1, (sdc). It is true that partition 1 of sda is a bootable primary partition, and I want to do the same for sdc. I've always had multiple independently bootable disks with their own GRUB on a machine. This is the first time I've run into trouble with it. In installation options for sdc, I did ask to have a MBR installed. Why does an installation on one disk care about what happens to be on another unmounted disk? First, check carefull y what you do in the partitionning dialog. sda shouldn't be used at all by the system you install, but I suspect you have maybe marked it as used in some way. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ascii 2.0 installation confused by mount points
I'm installing ascii on a disk, sdc, in a machine that has two other disks, one of which, sda already has a bootable devuan jessie on it. The installation goes well until I go to write my partitioning of sdc to disk. I get the error message: "Two file systems are assigned to the same mount point (/): SCSII (0,0,0), partition #1 (sda) and SCSI3 (0,0,0), partition #1, (sdc). It is true that partition 1 of sda is a bootable primary partition, and I want to do the same for sdc. I've always had multiple independently bootable disks with their own GRUB on a machine. This is the first time I've run into trouble with it. In installation options for sdc, I did ask to have a MBR installed. Why does an installation on one disk care about what happens to be on another unmounted disk? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
