I installed the new open suse 12.3 ver I down loaded some repositorys (bad move now I know) .
when I try logging in I get this
doing fast boot
creating device node with udev
welcome to emergency mode! after logging in type, “journalct1 -b” to view system logs, “systemct1 to re boot” to try again to boot in default mode.
((( below all this )))
give root password for log in: nothing i type in works doesnot seem to acsept any thing i type what ever i type i get "wrong pass word.
the login screen I get is
open suse 12.3
advanced options for open 12.3
windows 7 (loader) (on/dev/ sda 1)
windows 7 (loader) (on/dev/sda 2)
windows recovery environment (loader ) ( on dev/sda4)
can delete repositorys or delete open suse 12.3 and reinstall
I have looked all thru my hard drives and can not fid any thing for 12.3
HELP I like 12.3 the little I have seen THANK YOU very much john
>
> I installed the new open suse 12.3 ver I down loaded some repositorys
> (bad move now I know) .
> when I try logging in I get this
> doing fast boot
> creating device node with udev
> welcome to emergency mode! after logging in type, “journalct1 -b” to
> view system logs, “systemct1 to re boot” to try again to boot in default
> mode.
> ((( below all this )))
> give root password for log in: nothing i type in works
> doesnot seem to acsept any thing i type what ever i type i get "wrong
> pass word.
> the login screen I get is
>
> open suse 12.3
> advanced options for open 12.3
> windows 7 (loader) (on/dev/ sda 1)
> windows 7 (loader) (on/dev/sda 2)
> windows recovery environment (loader ) ( on dev/sda4)
>
>
> can delete repositorys or delete open suse 12.3 and reinstall
> I have looked all thru my hard drives and can not fid any thing for
> 12.3
> HELP I like 12.3 the little I have seen THANK YOU very much john
>
>
Try selecting the second boot option. The advanced options will give you
even more oportunities to tailor the boot to avoid crashing due to hardware
issues. The advanced options have changed with 12.x so I can’t recall the
exact wording but what you see is typical of a hardware problem which you
can skip from the advanced boot option. Give that a try and see how far you
get and write back.
It sounds like for some reason, one of your partitions is not being mounted. Did you have an external drive or USB thumb drive in when you did the install? Did you attempt to load openSUSE on a different hard drive than sda? There are limitations to the number of partitions you can have on an MBR disk and UEFI and GPT disks can be hard to setup when dual booting with Windows as you can only boot and install from the DVD and you must select an efi boot from your PC UEFI setup to work. For any install to work, openSUSE needs some room to install into. How did you get enough room for openSUSE to be installed? openSUSE normally wants three partitions to install, 1. root /, 2. /home and 3. SWAP. Yuu must decide from where to boot, MBR, Partitions 1, 2, 3 or 4 or an efi Partition on a GPT disk. You cannot boot from a partition higher than 4 unless you installed grub into the MBR (Master Boot Record). It comes down to …
What kind of disk partition do you have? GPT or MBR?
Where did you expect to find enough free room to install openSUSE?
Depending on the disk type, how did you expect to boot up openSUSE?
How many times have you ever successfully installed a Linux Distribution such as openSUSE?
>
> I installed the new open suse 12.3 ver I down loaded some repositorys
> (bad move now I know) .
> when I try logging in I get this
> doing fast boot
> creating device node with udev
> welcome to emergency mode! after logging in type, “journalct1 -b” to
> view system logs, “systemct1 to re boot” to try again to boot in default
> mode.
> ((( below all this )))
> give root password for log in: nothing i type in works
> doesnot seem to acsept any thing i type what ever i type i get "wrong
> pass word.
> the login screen I get is
>
> open suse 12.3
> advanced options for open 12.3
> windows 7 (loader) (on/dev/ sda 1)
> windows 7 (loader) (on/dev/sda 2)
> windows recovery environment (loader ) ( on dev/sda4)
>
>
> can delete repositorys or delete open suse 12.3 and reinstall
> I have looked all thru my hard drives and can not fid any thing for
> 12.3
> HELP I like 12.3 the little I have seen THANK YOU very much john
>
>
Try selecting the second boot option. The advanced options will give you
even more oportunities to tailor the boot to avoid crashing due to hardware
issues. The advanced options have changed with 12.x so I can’t recall the
exact wording but what you see is typical of a hardware problem which you
can skip from the advanced boot option. Give that a try and see how far you
get and write back.
Q. It sounds like for some reason, one of your partitions is not being mounted. Did you have an external drive or USB thumb drive in when you did the install?
A. No both external drvs were disconected
same with the usb drive
Q. How did you get enough room for openSUSE to be installed?
A.I have a one terrabit drive and useing the iso it said partitioning drv
Q. Partitions 1, 2, 3 or 4 or an efi Partition on a GPT disk
A.I do not see any thig other than sda/ 1 , sda/ 2 this is in the boot menu
So to the question of where you are going to install openSUSE, lets get more details.
/dev/sda = One Terabyte
sda1 = Windows 7, what size?
sda2 = Windows 7, What size?
sda4 = Windows 7, What size?
sda? = root / openSUSE Partition, what size?
sda? = /home partition, what size?
sda? = SWAP, 2, 4 or 8 GB most likley
So I am taking specifics here. openSUSE normally tries to create three partitions. The message you got most often comes when a partition on a hard drive, was there during the install, but is not there when you try to startup openSUSE. This can happen for instance if you run the Windows Partition program after installing openSUSE in a dual boot setup with Windows. Tell us more about the PC, what brand & make is it? How old is it? And again, have you ever successfully installed a copy of any Linux distribution before?
doing fast boot
creating device node with udev
welcome to emergency mode! after logging in type, “journalct1 -b” to
view system logs, “systemct1 to re boot” to try again to boot in default
mode.
((( below all this )))
give root password for log in:
there is no flashing cursor
there is no place that accepts input
and all I get for output after type for root password is password incorrect
I am going to move info on my c drive to an external driv and reinstall windows & windows8 SUSE
> the second boot on my menu goes to windows 8 which starts
> thanks john
Not that one. The second one in your previous post was “advanced options
for open 12.3”. Enter that, it has more entries inside, and at least one
of them will be “failsafe”.
Be careful when you answer not to break codes in the post. There was the
word “/QUOTE” inside square brackets - you removed the closing one
making very difficult to know what is yours and what is not.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
>
> I installed the new open suse 12.3 ver I down loaded some repositorys
> (bad move now I know) .
> when I try logging in I get this
> doing fast boot
> creating device node with udev
> welcome to emergency mode! after logging in type, “journalct1 -b” to
> view system logs, “systemct1 to re boot” to try again to boot in default
> mode.
> ((( below all this )))
> give root password for log in: nothing i type in works
> doesnot seem to acsept any thing i type what ever i type i get "wrong
> pass word.
> the login screen I get is
>
> open suse 12.3
> advanced options for open 12.3
> windows 7 (loader) (on/dev/ sda 1)
> windows 7 (loader) (on/dev/sda 2)
> windows recovery environment (loader ) ( on dev/sda4)
>
>
> can delete repositorys or delete open suse 12.3 and reinstall
> I have looked all thru my hard drives and can not fid any thing for
> 12.3
> HELP I like 12.3 the little I have seen THANK YOU very much john
>
>
Try selecting the second boot option. The advanced options will give you
even more oportunities to tailor the boot to avoid crashing due to hardware
issues. The advanced options have changed with 12.x so I can’t recall the
exact wording but what you see is typical of a hardware problem which you
can skip from the advanced boot option. Give that a try and see how far you
get and write back.