[opensuse-factory] YaST Installer proposal
Yesterday I had a call from a colleague who was installing SLES 10 to a server with 1.9TB partition. She was a bit freaked out because this is a relatively new thing for her to do and after the first phase of Installer, "it is hanging on the splash screen for a very long time doing nothing!" I knew she had a very large partition and so I told her to hit ESC to see what is going on in the background, as I had my suspicions. Sure enough, it had that message "Drive hasn't been checked in 47829 days" (or whatever the specific line is.) I told her to just be patient and let it run its course because she's on a large partition. I've already been seeing this on my machines that have 750GB drives. She had actually tried this on two other similar servers that they had just bought and was starting to think it was some kind of driver issue with that particular model. Obviously, that wasn't the case. In this day and age of larger drives everywhere from the data center to the home user, wouldn't it be a good idea if we had some kind of message between 1st phase and 2nd phase where it says something like "Depending on the size of your hard drive, this may take a while." before going into the second phase of installation? Or maybe this has already been discussed and shot down, in which case, I'll shut up. Bryen --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Bryen wrote:
Yesterday I had a call from a colleague who was installing SLES 10 to a server with 1.9TB partition. She was a bit freaked out because this is a relatively new thing for her to do and after the first phase of Installer, "it is hanging on the splash screen for a very long time doing nothing!"
I knew she had a very large partition and so I told her to hit ESC to see what is going on in the background, as I had my suspicions. Sure enough, it had that message "Drive hasn't been checked in 47829 days" (or whatever the specific line is.) I told her to just be patient and let it run its course because she's on a large partition. I've already been seeing this on my machines that have 750GB drives.
She had actually tried this on two other similar servers that they had just bought and was starting to think it was some kind of driver issue with that particular model. Obviously, that wasn't the case.
In this day and age of larger drives everywhere from the data center to the home user, wouldn't it be a good idea if we had some kind of message between 1st phase and 2nd phase where it says something like "Depending on the size of your hard drive, this may take a while." before going into the second phase of installation?
Or maybe this has already been discussed and shot down, in which case, I'll shut up.
Bryen
I mentioned something similar in a recent post, my daughter tried bringing her PC up over a few days and thought it was hanging in boot. I took a ride over, powered on and discovered it was doing fsck.ext3. Mind you, I thought I had already run "tune2fs -c -1 /dev/sda1" after the install, she must have accidentally switched off the wrong switch on the multi-strip while the box was up. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Bryen napsal(a):
... In this day and age of larger drives everywhere from the data center to the home user, wouldn't it be a good idea if we had some kind of message between 1st phase and 2nd phase where it says something like "Depending on the size of your hard drive, this may take a while." before going into the second phase of installation?
In my opinion, the startup screen is fine unless there is some fsck.ext3 call (usually every 60 days or so? or in case of wrong shutdown/power failure...). Your proposal "Depending on the size of your hard drive, this may take a while." is technically correct but it doesn't provide the information user needs not to panic. My proposal is to detect that there is some fsck run (or another delay in starting the system (more than ... hmm ... 20 seconds?)) and either switch the splash off or provide some progress right in the splash. Bye L. -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.
participants (3)
-
Bryen -
Lukas Ocilka -
Sid Boyce