Hi all,
What happens locally during a DVD upgrade? are the steps fully documented?
What about the personal datas in /root or /home folders and subfolders?
Thanks for your comments.
On 2014-12-12 15:26, jnowe wrote:
>
> Hi all,
>
> What happens locally during a DVD upgrade? are the steps fully
> documented?
> What about the personal datas in /root or /home folders and subfolders?
kept.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Upgrade with DVD successfully done. But GRUB screen is the 13.2 with showing a selection between Windows 7 and Opensuse 13.1.
And the system keeps rebooting after choosing Linux.
Upgrade process doesnt seem to be mature.
Nevertheless, thanks for your feedback although the upgrade finally failed.
On 2014-12-12 17:46, jnowe wrote:
>
> Upgrade with DVD successfully done. But GRUB screen is the 13.2 with
> showing a selection between Windows 7 and Opensuse 13.1.
No, that is correct. The string is not automatically changed because it
belongs to the system administrator, ie, you, jnowe 
> And the system keeps rebooting after choosing Linux.
Well, that can be analyzed. Give details, please.
> Upgrade process doesnt seem to be mature.
It is very mature, I have used it since the previous century
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
what do you need the boot.log?
[32m OK [0m] Started Show Plymouth Boot Screen.[32m OK [0m] Reached target Paths.
[32m OK [0m] Reached target Basic System.
[32m OK [0m] Found device ST1000DM003-9YN1.
Starting File System Check on /dev/disk/by-uuid/3962059d-c2f6-402f-b09d-cf36fbf0daec…
[32m OK [0m] Started File System Check on /dev/disk/by-uuid/3962059d-c2f6-402f-b09d-cf36fbf0daec.
[32m OK [0m] Started dracut initqueue hook.
[32m OK [0m] Reached target Remote File Systems (Pre).
[32m OK [0m] Reached target Remote File Systems.
Starting dracut pre-mount hook…
[32m OK [0m] Started dracut pre-mount hook.
Mounting /sysroot…
[32m OK [0m] Mounted /sysroot.
[32m OK [0m] Reached target Initrd Root File System.
Starting Reload Configuration from the Real Root…
[32m OK [0m] Started Reload Configuration from the Real Root.
[32m OK [0m] Reached target Initrd File Systems.
[32m OK [0m] Reached target Initrd Default Target.
Welcome to [0;32mopenSUSE 13.2 (Harlequin) (x86_64)[0m!
[[32m OK [0m] Stopped Switch Root.
[32m OK [0m] Stopped target Switch Root.
Stopping File System Check on /dev/disk/by-uuid/3962059d-c2f6-402f-b09d-cf36fbf0daec…
[32m OK [0m] Stopped File System Check on /dev/disk/by-uuid/3962059d-c2f6-402f-b09d-cf36fbf0daec.
Starting Show Plymouth Reboot Screen…
Starting Create dynamic rule for /dev/root link…
Starting Console System Startup Logging…
[32m OK [0m] Listening on Delayed Shutdown Socket.
[32m OK [0m] Listening on /dev/initctl Compatibility Named Pipe.
Starting Shadow /etc/init.d/boot.localfs…
[32m OK [0m] Started Shadow /etc/init.d/boot.localfs.
Starting Tell Plymouth To Write Out Runtime Data…
Starting Create list of required static device nodes for the current kernel…
Mounting Huge Pages File System…
Mounting POSIX Message Queue File System…
[32m OK [0m] Set up automount Arbitrary Executable File Formats File System Automount Point.
[32m OK [0m] Stopped Trigger Flushing of Journal to Persistent Storage.
Stopping Journal Service…
[32m OK [0m] Stopped Journal Service.
Starting Journal Service…
[32m OK [0m] Started Journal Service.
Starting Trigger Flushing of Journal to Persistent Storage…
Expecting device dev-disk-by\x2did-ata\x2dST1000DM003\x2d9YN162_Z1D065NJ\x2dpart2.device…
[32m OK [0m] Listening on udev Kernel Socket.
[32m OK [0m] Listening on udev Control Socket.
Expecting device dev-disk-by\x2did-ata\x2dST1000DM003\x2d9YN162_Z1D065NJ\x2dpart3.device…
Expecting device dev-disk-by\x2did-ata\x2dST3320620AS_9QF3HX08\x2dpart1.device…
[32m OK [0m] Reached target Unmount All Filesystems.
[32m OK [0m] Stopped target Initrd File Systems.
[32m OK [0m] Stopped target Initrd Root File System.
[32m OK [0m] Removed slice system-systemd\x2dfsck.slice.
[1;39m INFO [0m] Update UTMP about System Reboot/Shutdown is not active.
Stopping Setup Virtual Console…
[32m OK [0m] Stopped Setup Virtual Console.
Starting udev Coldplug all Devices…
Starting Store Sound Card State…
[32m OK [0m] Started Create list of required static device nodes for the current kernel.
Starting Create static device nodes in /dev…
[32m OK [0m] Started Tell Plymouth To Write Out Runtime Data.
[32m OK [0m] Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization…
[32m OK [0m] Mounted Huge Pages File System.
[32m OK [0m] Mounted POSIX Message Queue File System.
[32m OK [0m] Started Create dynamic rule for /dev/root link.
[32m OK [0m] Started Trigger Flushing of Journal to Persistent Storage.
[32m OK [0m] Started Console System Startup Logging.
Starting Console System Reboot Logging…
[32m OK [0m] Started Console System Reboot Logging.
[32m OK [0m] Started Show Plymouth Reboot Screen.
[32m OK [0m] Started Create static device nodes in /dev.
Starting udev Kernel Device Manager…
[32m OK [0m] Started udev Kernel Device Manager.
[1;31mFAILED[0m] Failed to start Store Sound Card State.
See “systemctl status alsa-store.service” for details.
[32m OK [0m] Started udev Wait for Complete Device Initialization.
Starting Activation of LVM2 logical volumes…
[32m OK [0m] Started Activation of LVM2 logical volumes.
Starting Activation of LVM2 logical volumes…
[32m OK [0m] Started Activation of LVM2 logical volumes.
[32m OK [0m] Found device ST3320620AS.
Starting File System Check on /dev/disk/by-id/ata-ST3320620AS_9QF3HX08-part1…
[32m OK [0m] Found device ST1000DM003-9YN1.
Starting File System Check on /dev/disk/by-id/ata-ST1000DM003-9YN162_Z1D065NJ-part3…
/dev/sdc1: fsck 0.0% complete…
/dev/sdc1: fsck 0.0% complete…
/dev/sdc1: fsck 0.5% complete…
/dev/sdc1: fsck 1.0% complete…
[32m OK [0m] Found device ST1000DM003-9YN1.
/dev/sdc1: fsck 7.5% complete…
/dev/sdc1: fsck 9.9% complete…
/dev/sdc1: fsck 11.8% complete…
/dev/sdc1: fsck 12.7% complete…
/dev/sdc1: fsck 13.6% complete…
/dev/sdc1: fsck 14.1% complete…
/dev/sdc1: fsck 15.1% complete…
/dev/sdc1: fsck 16.0% complete…
/dev/sdc1: fsck 17.4% complete…
/dev/sdc1: fsck 18.8% complete…
/dev/sdc1: fsck 19.3% complete…
/dev/sdc1: fsck 19.8% complete…
/dev/sdc1: fsck 20.2% complete…
/dev/sdc1: fsck 20.7% complete…
/dev/sdc1: fsck 21.2% complete…
/dev/sdc1: fsck 21.6% complete…
/dev/sdc1: fsck 22.6% complete…
/dev/sdc1: fsck 23.5% complete…
/dev/sdc1: fsck 24.9% complete…
/dev/sdc1: fsck 26.8% complete…
/dev/sdc1: fsck 28.7% complete…
/dev/sdc1: fsck 30.6% complete…
/dev/sdc1: fsck 31.5% complete…
/dev/sdc1: fsck 32.9% complete…
/dev/sdc1: fsck 33.8% complete…
/dev/sdc1: fsck 34.8% complete…
/dev/sdc1: fsck 38.5% complete…
/dev/sdc1: fsck 40.4% complete…
/dev/sdc1: fsck 41.8% complete…
/dev/sdc1: fsck 42.8% complete…
/dev/sdc1: fsck 44.6% complete…
/dev/sdc1: fsck 45.1% complete…
/dev/sdc1: fsck 46.1% complete…
/dev/sdc1: fsck 47.5% complete…
/dev/sdc1: fsck 48.4% complete…
/dev/sdc1: fsck 49.3% complete…
/dev/sdc1: fsck 49.8% complete…
/dev/sdc1: fsck 50.7% complete…
/dev/sdc1: fsck 51.7% complete…
/dev/sdc1: fsck 52.2% complete…
/dev/sdc1: fsck 53.6% complete…
/dev/sdc1: fsck 54.5% complete…
/dev/sdc1: fsck 55.4% complete…
/dev/sdc1: fsck 55.9% complete…
/dev/sdc1: fsck 56.4% complete…
/dev/sdc1: fsck 57.3% complete…
/dev/sdc1: fsck 58.7% complete…
/dev/sdc1: fsck 59.7% complete…
/dev/sdc1: fsck 60.6% complete…
/dev/sdc1: fsck 61.5% complete…
/dev/sdc1: fsck 62.0% complete…
/dev/sdc1: fsck 63.0% complete…
/dev/sdc1: fsck 63.4% complete…
/dev/sdc1: fsck 64.4% complete…
/dev/sdc1: fsck 65.8% complete…
/dev/sdc1: fsck 66.2% complete…
/dev/sdc1: fsck 66.7% complete…
/dev/sdc1: fsck 67.7% complete…
/dev/sdc1: fsck 68.1% complete…
/dev/sdc1: fsck 69.1% complete…
/dev/sdc1: fsck 70.0% complete…
/dev/sdc1: fsck 70.9% complete…
/dev/sdc1: fsck 71.4% complete…
/dev/sdc1: fsck 72.3% complete…
/dev/sdc1: fsck 72.8% complete…
/dev/sdc1: fsck 73.0% complete…
/dev/sdc1: fsck 73.3% complete…
/dev/sdc1: fsck 73.8% complete…
/dev/sdc1: fsck 74.4% complete…
/dev/sdc1: fsck 75.0% complete…
/dev/sdc1: fsck 75.9% complete…
/dev/sdc1: fsck 76.6% complete…
/dev/sdc1: fsck 76.8% complete…
/dev/sdc1: fsck 77.8% complete…
/dev/sdc1: fsck 78.1% complete…
/dev/sdc1: fsck 78.4% complete…
/dev/sdc1: fsck 78.9% complete…
/dev/sdc1: fsck 79.2% complete…
/dev/sdc1: fsck 79.4% complete…
/dev/sdc1: fsck 80.0% complete…
/dev/sdc1: fsck 80.4% complete…
/dev/sdc1: fsck 80.9% complete…
/dev/sdc1: fsck 81.4% complete…
/dev/sdc1: fsck 82.1% complete…
/dev/sdc1: fsck 82.6% complete…
/dev/sdc1: fsck 83.0% complete…
/dev/sdc1: fsck 83.6% complete…
/dev/sdc1: fsck 84.6% complete…
/dev/sdc1: fsck 84.8% complete…
/dev/sdc1: fsck 85.5% complete…
/dev/sdc1: fsck 86.4% complete…
/dev/sdc1: fsck 87.1% complete…
/dev/sdc1: fsck 87.6% complete…
/dev/sdc1: fsck 88.4% complete…
/dev/sdc1: fsck 89.0% complete…
/dev/sdc1: fsck 89.3% complete…
/dev/sdc1: fsck 89.7% complete…
/dev/sdc1: fsck 92.1% complete…
/dev/sdc1: fsck 92.6% complete…
/dev/sdc1: fsck 93.1% complete…
/dev/sdc1: fsck 93.6% complete…
/dev/sdc1: fsck 94.1% complete…
/dev/sdc1: fsck 94.6% complete…
/dev/sdc1: fsck 95.0% complete…
/dev/sdc1: fsck 99.5% complete…
[32m OK [0m] Started File System Check on /dev/disk/by-id/ata-ST3320620AS_9QF3HX08-part1.
/dev/sdd3: fsck 21.8% complete…
/dev/sdd3: fsck 21.8% complete…
/dev/sdd3: fsck 21.9% complete…
/dev/sdd3: fsck 21.9% complete…
/dev/sdd3: fsck 22.0% complete…
/dev/sdd3: fsck 22.0% complete…
/dev/sdd3: fsck 22.1% complete…
/dev/sdd3: fsck 22.2% complete…
/dev/sdd3: fsck 22.3% complete…
/dev/sdd3: fsck 22.3% complete…
/dev/sdd3: fsck 22.4% complete…
/dev/sdd3: fsck 22.5% complete…
/dev/sdd3: fsck 22.6% complete…
/dev/sdd3: fsck 22.6% complete…
/dev/sdd3: fsck 22.8% complete…
/dev/sdd3: fsck 22.9% complete…
/dev/sdd3: fsck 23.0% complete…
/dev/sdd3: fsck 23.1% complete…
/dev/sdd3: fsck 23.1% complete…
/dev/sdd3: fsck 23.4% complete…
/dev/sdd3: fsck 23.6% complete…
/dev/sdd3: fsck 23.6% complete…
/dev/sdd3: fsck 23.8% complete…
/dev/sdd3: fsck 23.8% complete…
/dev/sdd3: fsck 23.8% complete…
/dev/sdd3: fsck 24.0% complete…
/dev/sdd3: fsck 24.2% complete…
/dev/sdd3: fsck 24.3% complete…
/dev/sdd3: fsck 24.3% complete…
/dev/sdd3: fsck 24.4% complete…
/dev/sdd3: fsck 24.4% complete…
/dev/sdd3: fsck 24.4% complete…
/dev/sdd3: fsck 24.5% complete…
/dev/sdd3: fsck 24.5% complete…
/dev/sdd3: fsck 24.5% complete…
/dev/sdd3: fsck 24.5% complete…
/dev/sdd3: fsck 27.4% complete…
/dev/sdd3: fsck 29.6% complete…
/dev/sdd3: fsck 31.5% complete…
/dev/sdd3: fsck 37.5% complete…
/dev/sdd3: fsck 37.8% complete…
/dev/sdd3: fsck 38.0% complete…
/dev/sdd3: fsck 38.3% complete…
/dev/sdd3: fsck 38.6% complete…
/dev/sdd3: fsck 38.8% complete…
/dev/sdd3: fsck 39.4% complete…
/dev/sdd3: fsck 40.5% complete…
/dev/sdd3: fsck 40.7% complete…
/dev/sdd3: fsck 41.3% complete…
/dev/sdd3: fsck 41.6% complete…
/dev/sdd3: fsck 42.1% complete…
/dev/sdd3: fsck 58.1% complete…
/dev/sdd3: fsck 71.3% complete…
/dev/sdd3: fsck 72.0% complete…
/dev/sdd3: fsck 72.9% complete…
/dev/sdd3: fsck 73.9% complete…
/dev/sdd3: fsck 74.9% complete…
/dev/sdd3: fsck 76.0% complete…
/dev/sdd3: fsck 76.5% complete…
/dev/sdd3: fsck 76.7% complete…
/dev/sdd3: fsck 76.9% complete…
/dev/sdd3: fsck 77.7% complete…
/dev/sdd3: fsck 79.3% complete…
/dev/sdd3: fsck 79.6% complete…
/dev/sdd3: fsck 79.8% complete…
/dev/sdd3: fsck 80.6% complete…
/dev/sdd3: fsck 81.2% complete…
/dev/sdd3: fsck 83.1% complete…
/dev/sdd3: fsck 83.9% complete…
/dev/sdd3: fsck 84.1% complete…
/dev/sdd3: fsck 84.6% complete…
/dev/sdd3: fsck 84.9% complete…
/dev/sdd3: fsck 85.0% complete…
/dev/sdd3: fsck 85.2% complete…
/dev/sdd3: fsck 86.7% complete…
/dev/sdd3: fsck 87.3% complete…
/dev/sdd3: fsck 87.8% complete…
/dev/sdd3: fsck 88.3% complete…
/dev/sdd3: fsck 88.5% complete…
/dev/sdd3: fsck 88.7% complete…
/dev/sdd3: fsck 88.8% complete…
/dev/sdd3: fsck 89.4% complete…
/dev/sdd3: fsck 89.6% complete…
/dev/sdd3: fsck 91.0% complete…
/dev/sdd3: fsck 92.3% complete…
/dev/sdd3: fsck 92.6% complete…
/dev/sdd3: fsck 92.9% complete…
/dev/sdd3: fsck 93.2% complete…
/dev/sdd3: fsck 93.5% complete…
/dev/sdd3: fsck 93.7% complete…
/dev/sdd3: fsck 94.0% complete…
/dev/sdd3: fsck 94.3% complete…
/dev/sdd3: fsck 94.5% complete…
/dev/sdd3: fsck 94.6% complete…
/dev/sdd3: fsck 94.7% complete…
/dev/sdd3: fsck 94.8% complete…
/dev/sdd3: fsck 94.8% complete…
/dev/sdd3: fsck 94.9% complete…
/dev/sdd3: fsck 95.0% complete…
/dev/sdd3: fsck 98.3% complete…
[32m OK [0m] Started File System Check on /dev/disk/by-id/ata-ST1000DM003-9YN162_Z1D065NJ-part3.
[32m OK [0m] Reached target Shutdown.
Starting /etc/init.d/halt.local Compatibility…
[32m OK [0m] Started /etc/init.d/halt.local Compatibility.
[32m OK [0m] Reached target Final Step.
Starting Reboot…
Dont understand why this fsck. It was the case with Opensuse 13.1 causing the reboot (this happened after a normal reboot). The drive was tested with seagate tools, it’s ok.
Do you lose power frequently or don’t use correct procedure to shutdown?? It does not have to be a bad drive to corrupt a file system.
On 2014-12-12 23:26, jnowe wrote:
> what do you need the boot.log?
Perfect.
>> [32m OK [0m] Started Show Plymouth Boot Screen.[32m OK [0m]
>> Reached target Paths.
>> [32m OK [0m] Reached target Basic System.
Well, the system is booting.
>> Welcome to [0;32mopenSUSE 13.2 (Harlequin) (x86_64)[0m![/color]
It welcomes you.
>> Starting Show Plymouth Reboot Screen…
??
>> Starting Trigger Flushing of Journal to Persistent Storage…
>> Starting File System Check on
>> /dev/disk/by-id/ata-ST1000DM003-9YN162_Z1D065NJ-part3…
>>
>>
>> /dev/sdc1: fsck 0.0% complete…
…
>> /dev/sdc1: fsck 99.5% complete…
>>
>>
>>
>> [32m OK [0m] Started File System Check on
>> /dev/disk/by-id/ata-ST3320620AS_9QF3HX08-part1.
>>
>>
>> /dev/sdd3: fsck 21.8% complete…
…
>> /dev/sdd3: fsck 98.3% complete…
>>
>>
>>
>> [32m OK [0m] Started File System Check on
>> /dev/disk/by-id/ata-ST1000DM003-9YN162_Z1D065NJ-part3.
>> [32m OK [0m] Reached target Shutdown.
>> Starting /etc/init.d/halt.local Compatibility…
>> [32m OK [0m] Started /etc/init.d/halt.local Compatibility.
>> [32m OK [0m] Reached target Final Step.
>> Starting Reboot…
IMO, you have set the default target to “shutdown”. Check this symlink:
/etc/systemd/system/default.target
A comment: When pasting here computer commands and such, please use a
CODE BLOCK, so that the forum software doesn’t do silly things like
converting URLS to tiny urls, wrap lines, or otherwise hide or alter the
commands you entered. You get them by clicking on the ‘#’ button in the
forum editor. http://susepaste.org/images/15093674.jpg
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I’ve set nothing in this file.
I only reboot or shutdown Linux in the menu of the OS. And the power is stable.
This is what I have in the file you gave me:
[Unit]
Description=Reboot
Documentation=man:systemd.special(7)
DefaultDependencies=no
Requires=systemd-reboot.service
After=systemd-reboot.service
AllowIsolate=yes
[Install]
Alias=ctrl-alt-del.target
What should I do now? remove this?
No. That “file” is just a symlink to what’s set as default target to boot to.
And as the content of your “file” shows, it’s “reboot.target” in your case:
This is what I have in the file you gave me:
[Unit]
Description=Reboot
Documentation=man:systemd.special(7)
DefaultDependencies=no
Requires=systemd-reboot.service
After=systemd-reboot.service
AllowIsolate=yes
[Install]
Alias=ctrl-alt-del.target
What should I do now? remove this?
No. Your system probably won’t boot at all then (I never tried this yet 
).
Press ‘e’ at the boot menu, search for the line starting with “linux” and append ‘5’ at the end, then press ‘F10’ to boot to standard graphical mode.
Then enter YaST->System->Services Manager and set the “Default Target” to “graphical system” or “runlevel 5”.
Or run “sudo systemctl set-default graphical.target”.
but how this happened to me? before the **** came to me, i was disabling the tracker because of high CPU use.
How should I (or anybody else) know?
What exactly did you do to disable tracker?
I know of people that changed that by mistake when they wanted to enable/disable services in YaST’s Services Manager.
PS: I just had a look, and that isn’t even possible any more in 13.2’s YaST.
So there must be a different reason, or you set it wrong on 13.1 already before upgrading.
I changed a setting in desktop search and that’s all. But nothing in Yast. Then i rebooted. And the system kept rebooting and so on.
btw, is it normal to find “my content” in /etc/systemd/system/default.target?
Well, changing a setting in desktop search definitely cannot be the reason.
And you actually need root privileges for that.
Did you install updates? Maybe there’s a buggy package script somewhere?
But I never experienced something like that here.
btw, is it normal to find “my content” in /etc/systemd/system/default.target?
???
Again, default.target is just a symlink, it only points to another file.
It has no content itself at all.
And as you noticed, it should better not point to reboot.target, which has that content you posted.
Normally it should point to runlevel5.target or graphical.target. (all of those are located in /usr/lib/systemd/system/)
Run this to see where it points to:
ls -l /etc/systemd/system/default.target
On 2014-12-13 01:36, jnowe wrote:
> This is what I have in the file you gave me:
No, no. It is not a file, it is a symlink. And you had to find out where it pointed to.
Look, this is mine:
Telcontar:~ # ls -l /etc/systemd/system/default.target
lrwxrwxrwx 1 root root 40 Jun 7 2013 /etc/systemd/system/default.target -> /usr/lib/systemd/system/runlevel3.target
Telcontar:~ #
You probably have this, looking at what you posted:
/etc/systemd/system/default.target -> /usr/lib/systemd/system/reboot.target
which means that the final state of your system is to “reboot”. It will never start. How that came to be, does not matter, it happened.
You have to make it point to something suitable, like graphical.target, multi-user.target, runlevel3.target, runlevel5.target…
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
of course, it does matter.
Fortunately, there is this great forum with great guys who gave me the solution.
Big thanks for solving my issue!
PS: i coud reach you because I still keep Windows
On 2014-12-13 02:56, jnowe wrote:
>
> robin_listas;2682544 Wrote:
>>
>>
>> How that came to be, does not matter, it happened.
> of course, it does matter.
Not really, it does not affect the procedure to solve it
> Fortunately, there is this great forum with great guys who gave me the
> solution.
> Big thanks for solving my issue!
Welcome.
> PS: i coud reach you because I still keep Windows
Well, many of us keep a cd or usb stick that we can boot with a suitable
Linux usable for rescue ops. A very good one, cd size, is the openSUSE
xfce rescue image which you can download from the opensuse.org site.
I’d recommend you prepare it now to be ready for the next time
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)