That wasn't very polite...

cpcnw · 2017-11-10 21:28

Just put another SSD in my system to test out Scorpion and it went and stomped over my boot sector without even asking!

I didn't actually see this happen because I was out of the room at the time but when I got back I was at the 'Finish & Reboot' screen which I did and got straight to the Q4OS login.

I have 2 other discs with other OS's on - would have been nice to have been asked about those...

crosscourt · 2017-11-10 22:10

Youre running three drives? Each drive has a boot sector of its own and Q4OS wouldnt do anything except deal with the drive its being installed on. Partitioned drive thats a whole other ball game, is that what happened?

Bios with separate drives is set to boot a specific drive so no issues if its separate drives.

cpcnw · 2017-11-10 22:16

Yep 3 drives and 3rd one for Scorpion. So thats SATA0,1,2 and I chose full disc on SATA2 [disc3] and it went and stomped the boot sector on SATA0...

Never mind sorted it now and just disconnected the other two drives during the installation, installed then reconnected them. The bios is now the OS selector.

Works for me

q4osteam · 2017-11-10 22:31

cpcnw wrote:

.. it went and stomped the boot sector on SATA0...

If you have installed another system, installer should detect it and do a query before writing grub to the boot sector. If it didn't, it's a bug. We will try to reproduce it and fix as soon as possible.

crosscourt · 2017-11-10 22:34

Ok, absolutely I always recommend to people to disconnect other drives when doing an install even though it shouldnt be an issue, many times it is. On my pc I have Windows 7 and Q4OS 2.4 installed and didnt have any issues but it does happen even with other distros.

So far I havent had this issue on any of my systems using separate OS on multiple drives. I run only one OS per drive for testing purposes with my test system running 7 drives presently.

Last edited by crosscourt (2017-11-10 22:36)

cpcnw · 2017-11-10 23:28

I suspect the installer wrote out to the boot secor of the first disc by default - rather than the one q4os is being installed to...

Last edited by cpcnw (2017-11-10 23:28)

Dai_trying · 2017-11-10 23:28

@cpcnw
Did the installation write grub to both the installation drive (SATA2) AND the primary drive (SATA0)? or just to SATA0?

crosscourt · 2017-11-10 23:29

Gotcha, just curious and even though I havent seen the issue, maybe the devs cant sort this out.

cpcnw · 2017-11-11 07:44

Dai_trying wrote:

@cpcnw
Did the installation write grub to both the installation drive (SATA2) AND the primary drive (SATA0)? or just to SATA0?

I reckon _just_ SATA0 because when I disconnected both the other drives SATA2 wouldn't boot at all. I then did the installation with just SATA2 connected - which worked.

Dai_trying · 2017-11-11 07:57

That would make sense, Grub would default to the primary Hdd when installing and you would need to tell it to be installed in another partition if that is desired. It's another argument to use the live-cd for installing I get a screen (before actual installation starts) telling me exactly what will be formatted what will be mounted and where grub is going which (IMO) is a must with multi-booting.
I am guessing you used the installation disc rather than the live-cd?...

crosscourt · 2017-11-11 17:29

I use the installation disk almost exclusively and havent had any issues in both my test system and main system with multiple drives.
I use the classic install which gives you a bit more control than the automated/no questions asked version.

Dai_trying · 2017-11-11 22:44

I think the actual issue is that when performing installs, the installation iso is not always clear (especially to the newer users) regarding grub installation, whereas the live-cd gives a summary screen (before installation starts) telling you if grub is being installed and where, partitions that will be formatted (swap is not formatted by default with live-cd) and partitions that will be mounted (including EFI boot partition if required) so I much prefer to be able to double check everything before the installation starts, and always prefer (and promote) this method.

crosscourt · 2017-11-11 22:49

Its not as obvious as the live cd granted but its there and i would hope people are paying attention to the install until its finished. Thats a recipe for issues even with the live cd. Things do crop up at times and its best to be a good custodian.

Dai_trying · 2017-11-11 22:53

Yes, it is there, and tbh I don't always monitor what is going on with my installs as I tend to fill my time doing something else just as constructive (putting the kettle on for coffee usually )

crosscourt · 2017-11-11 22:56

Your experienced and have done many installs, you know your hardware. Some people run hardware thats got some issues so things can happen if youre not careful. Others have used other distros and have some bad habits as we've seen onsite recently and make inadvertent mistakes.

Dai_trying · 2017-11-11 22:59

I do think things are always improving with installation though, I can remember the early days of my Linux adventures and they really were fraught with danger, back then you wouldn't blink during an install in case something shot up the screen that you needed to see.

crosscourt · 2017-11-11 23:03

I remember those days and I have to say I havent lost that habit of keeping watch. The Q4OS installation disk/ no questions asked is a godsend as I can slip it in and install it on 5-10 machines at a time and walk away, as I rarely have issues with a single OS/single hard drive install.

Dai_trying · 2017-11-11 23:05

It is great to have that sort of confidence in an operating system

crosscourt · 2017-11-11 23:08

Yes it is and right now Q4OS is the only distro Ive used that Im able to do that with that level of confidence. When youve got a couple of people installing like that we can get a lot of systems done very quickly. The number of systems we have done with Q4OS is quite high presently.

q4osteam · 2017-11-12 13:03

We can confirm the issue. It's related only to classic-install from 'install-cd' media, if Q4OS is to be placed next to another operating system already installed. It seems to be a bug in the Debian preseeding logic, so the next step is to reproduce it on a pure Debian system and report at the appropriate site.

We have submitted a new ticket at our bugtracker, see https://sourceforge.net/p/q4os/tickets/65/ , any comments and findings would be appreciated, please post them there.

crosscourt · 2017-11-12 19:59

Only the classic install, interesting, will have to give it a look.

Q4OS Forum

#1 2017-11-10 21:28

That wasn't very polite...

#2 2017-11-10 22:10

Re: That wasn't very polite...

#3 2017-11-10 22:16

Re: That wasn't very polite...

#4 2017-11-10 22:31

Re: That wasn't very polite...

#5 2017-11-10 22:34

Re: That wasn't very polite...

#6 2017-11-10 23:28

Re: That wasn't very polite...

#7 2017-11-10 23:28

Re: That wasn't very polite...

#8 2017-11-10 23:29

Re: That wasn't very polite...

#9 2017-11-11 07:44

Re: That wasn't very polite...

#10 2017-11-11 07:57

Re: That wasn't very polite...

#11 2017-11-11 17:29

Re: That wasn't very polite...

#12 2017-11-11 22:44

Re: That wasn't very polite...

#13 2017-11-11 22:49

Re: That wasn't very polite...

#14 2017-11-11 22:53

Re: That wasn't very polite...

#15 2017-11-11 22:56

Re: That wasn't very polite...

#16 2017-11-11 22:59

Re: That wasn't very polite...

#17 2017-11-11 23:03

Re: That wasn't very polite...

#18 2017-11-11 23:05

Re: That wasn't very polite...

#19 2017-11-11 23:08

Re: That wasn't very polite...

#20 2017-11-12 13:03

Re: That wasn't very polite...

#21 2017-11-12 19:59

Re: That wasn't very polite...

Board footer