LinuxQuestions.org - UNABLE TO LOG INTO FEDORA 9 UPGRADE 64bit

Page 3 of 3

Show 50 post(s) from this thread on one page

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - UNABLE TO LOG INTO FEDORA 9 UPGRADE 64bit (https://www.linuxquestions.org/questions/linux-newbie-8/unable-to-log-into-fedora-9-upgrade-64bit-671604/)

ironhorse99

12-10-2008 07:47 PM

I'm afraid this does nothing at all. I typed it in verbatim the only exception being once I didn't include quotes where my name would go. All it did was return sh-3.2#.

forrestt

12-11-2008 07:58 AM

Sorry to take so long to get back to you. This makes it look like you don't have a shell specified in /etc/passwd. Go back into rescue mode and make sure. Remember, you will need to get a chrooted environment by running "chroot /mnt/sysimage' (you needed to do that for the previous instrctions as well).

Run the following:

Code:

grep username /etc/passwd

grep root /etc/passwd

You should see a line like the following:

Code:

username:x:1234:1234:Your Name:/home/username:/bin/bash

If you don't see something after the last ':' then you don't have a shell. Run:

Code:

/usr/bin/chsh -s /bin/bash username

/usr/bin/chsh -s /bin/bash root

You should then be able to reboot and log in.

If you do see something after the last ':' let me know what it is.

Forrest

ironhorse99

12-11-2008 12:02 PM

Forrestt: The response to the first code was: mike:x:500:500:mike v:/home/mike:/bin/bash.
I rebooted but nothing changed.
I'm thinking at this point there's no practical solution to this problem. I have a backup drive that has ver.7 kde that I just discovered within the last several days. I have in the past tried to retrieve files from an older version of linux when a newer verion was installed on my PC but have never been able to mount the drive. Can you explain how I can accomplish this. My PC has four 5 1/4 slots with removable drive bays installed so its very easy to go from one Op.Sys.to another. If I can pull my files then I think I'll do a DoD wipe of the drive/check it for errors with spinrite & load ver.9 Kde and be done with it. I want to thank you so much for all your help & if you didn't live so far away I'd have you over for the biggest Porterhouse you've ever had.Thanks Again, Mike

forrestt

12-11-2008 08:32 PM

There really isn't any need to DoD wipe your disk until you are totally done with it (i.e. you are about to throw it away or sell it). Reformatting it is enough.

I'd like for you to do one more thing for me though. Boot back into rescue mode, go into your chrooted environment, and run: 'cat /etc/fstab' and post the contents back here. After that, I can give you much cleaner commands to mount your current drive after booting from the ver.7 drive.

Let me know,

Forrest

ironhorse99

12-11-2008 10:50 PM

Ok....here goes:

UUID=0ac93530-7ea2-43dd-9385-8d5a820b2681 / ext3 defaults 1 1
UUID=5baddc75-f937-4fd6-96c7-2369bebd8132 /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0

I'm not even going to ask what this is although I do recognise the hex sys.

When you get time let me know how to mount that drive so I can get my files while running Version 7. Thanks, Mike

forrestt

12-12-2008 08:04 AM

OK, boot with both disks in the system and ver 7 as the boot disk. After it is up, run the following:

Code:

mkdir -p /mnt/olddisk

echo 'UUID=0ac93530-7ea2-43dd-9385-8d5a820b2681 /mnt/olddisk ext3 defaults 1 2' >> /etc/fstab

mount /mnt/olddisk

ls /mnt/olddisk

You should see your files from the ver 9 system.

HTH

Forrest

ironhorse99

12-12-2008 09:17 AM

Thanks Forrestt. What if anything did that info I posted give you. Mike

ironhorse99

12-12-2008 09:07 PM

[QUOTE=forrestt;3372989]OK, boot with both disks in the system and ver 7 as the boot disk. After it is up, run the following:

Forrestt: I'm getting a message stating: special device UUID(and the string you ask me to input)does not exist. What now??? Mike

forrestt

12-12-2008 09:14 PM

OK, try running: "sudo lvdisplay" with the ver7 as boot disk and both drives in the system and post the output here.

Forrest

ironhorse99

12-12-2008 09:32 PM

Here it is:

[root@localhost mike]# sudo lvdisplay
WARNING: Duplicate VG name VolGroup00: Existing 12r5xI-sWQc-Caev-8fzs-HBEO-6Hy5-0CeG0B (created here) takes precedence over 6L8Ih2-TDTe-q00N-dhHl-QYhk-eqnq-vXkl3M
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID 8VIvcA-HY2P-p6H3-Awz1-383B-4LDE-uhB2Tx
LV Write Access read/write
LV Status available
# open 1
LV Size 17.06 GB
Current LE 546
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID b7rpru-5dcN-qyYp-cudk-Wudc-VZNc-NQRC1y
LV Write Access read/write
LV Status available
# open 1
LV Size 1.44 GB
Current LE 46
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:1

[root@localhost mike]#

forrestt

12-12-2008 09:39 PM

OK, read this thread and follow the advice it lays out. Let me know how things go.

HTH

Forrest

ironhorse99

12-12-2008 10:22 PM

Forrestt: Wow..there's just too much there to absorb. I don't know where to start. I don't understand why its so difficult to see another drive of the same type.How in the world does anyone wanting to use another drive for storage get it done. I'm not a big fan of windows but this just isn't an issue under that system.It would be cool if someone with the knowhow could incorporate this feature into the next release. I thank you just the same for all your help Forrestt. Mike

ironhorse99

12-14-2008 01:44 PM

Forrestt: You've heard the statement.....if anything can go wrong it will.....lets see...I'll start at the beginning.
1): I found out that the video onboard is S3 Unichrome Pro VGA Adapter. This may come in handy in a few minutes.
2): I wiped the drive & attempted a clean install. What happened is that every time I got the graphic's page early in the install, it would lockup. If I chose install-text mode- the install went ok but I only get black & white screen with text & login name(something it never asked for during install)(I did choose password but nothing was asked about login name)
3): After the install a screen appeared with various config options & if I choose X system config as long as I navigate using the tab key I can move around but If I choose anything with the mouse and/or exit the screen,it locks up.
4): I thought to myself I'll boot my Ver.7 drive which I've never had a problem with & see if there's an update to Ver.9 or perhaps try Ubuntu etc.
You may recall that 1 option we tried was to boot ver.7 with ver.9 in sec.slot to get files from that drive, which didn't work. Now My ver.7 drive won't boot. I get this error:
fsck.ext3: Unable to resolve 'UUID=0ac530-7ea2-43dd-9385-8d5a820b2681'
It attempts this 3 times then tells me an error occurred during the file system check.
Am I really screwed now or can this be saved. I'm thinking that somehow the file system has become corrupted when I had both drives installed. I really need some help now. Mike

ironhorse99

12-26-2008 07:42 PM

Well....its official....The Video chip was the culprit all along. Now I need to get another card & have been told nvidea is the way to go. I downloaded the latest Ubuntu & thankfully this install had a generic vesa driver which at least enabled me to use it till a replacement is installed. Any thoughts on a new card?? Mike

All times are GMT -5. The time now is 02:20 AM.

Page 3 of 3

Show 50 post(s) from this thread on one page