Please Help: upgrade from 8.2 to 9 problem
Hi,
I have a PIII/800Mhz 256MB RAM HP notebook, which has ben running Suse 8.2
for some time and 8.0 for sometime before that. I was upgrading from 8.2
to 9.
/dev/hda1 is swap, /dev/hda2 is boot, /dev/hda3 is home.
After (**SLOW**) installation from the DVD, got a success message and
rebooted. KDE's log in window appeared. I logged in as a user and whil the
login prompts disappeared, leaving the KDE Welcome wallpaper,nothing
hapened. I opened a terminal window and logged in as a user. Got prompted
for the password, entered it, got told, You have mail in ... and then the
cursor gflashed but did not give me a nick@machine prompt. Just flashed at
me. Opened another terminal window and logged in as root - same thing.
Called Suse installation support. No help. But they did have me make a log
in with the rescue function of the install dvd and make a floppy of the
boot messages and hwinfo (below).
Then they went home for the weekend. Meanwhile my machine still completely
down.
Please, please can anyone be of help?
Nick
Disk /dev/hda: 60.0 GB, 60011642880 bytes
255 heads, 63 sectors/track, 7296 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 99 795186 82 Linux swap
/dev/hda2 * 100 3363 26218080 83 Linux
/dev/hda3 3364 5974 20972857+ 83 Linux
/dev/hda4 5975 7296 10618965 83 Linux
Cannot find map file.
Loaded 596 symbols from 21 modules.
klogd 1.4.1, log source = ksyslog started.
<4>Linux version 2.4.21-99-default (root@i386.suse.de) (gcc version 3.3.1
(SuSE Linux)) #1 Wed Sep 24 13:30:51 UTC 2003
<6>BIOS-provided physical RAM map:
<4> BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
<4> BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
<4> BIOS-e820: 00000000000eac00 - 0000000000100000 (reserved)
<4> BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
<4> BIOS-e820: 000000000fff0000 - 000000000ffffc00 (ACPI data)
<4> BIOS-e820: 000000000ffffc00 - 0000000010000000 (ACPI NVS)
<4> BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
<5>757MB vmalloc/ioremap area available.
<5>0MB HIGHMEM available.
<5>255MB LOWMEM available.
<7>ACPI: have wakeup address 0xc0001000
<4>On node 0 totalpages: 65520
<4>zone(0): 4096 pages.
<4>zone(1): 61424 pages.
<4>zone(2): 0 pages.
<5>ACPI disabled because your bios is from 1992 and too old
<5>You can enable it with acpi=force
<4>Building zonelist for node : 0
<4>Kernel command line: BOOT_IMAGE=linux SuSE=,1203200080,81AAC7B0.,
initrd=initrd ramdisk_size=65536 rescue=1 vga=0x317 splash=silent
<6>bootsplash: silent mode.
<6>Initializing CPU#0
<4>Detected 696.982 MHz processor.
<4>Console: colour dummy device 80x25
<4>Calibrating delay loop... 1389.36 BogoMIPS
<6>Memory: 250288k/262080k available (1590k kernel code, 11404k reserved,
605k data, 160k init, 0k highmem)
<6>Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
<6>Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
<6>Mount cache hash table entries: 512 (order: 0, 4096 bytes)
<4>Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
<4>Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>CPU: L1 I cache: 16K, L1 D cache: 16K
<6>CPU: L2 cache: 256K
<5>CPU serial number disabled.
<6>Intel machine check architecture supported.
<6>Intel machine check reporting enabled on CPU#0.
<7>CPU: After generic, caps: 0383f9ff 00000000 00000000 00000000
<7>CPU: Common caps: 0383f9ff 00000000 00000000 00000000
<4>CPU: Intel Pentium III (Coppermine) stepping 06
<6>Enabling fast FPU save and restore... done.
<6>Enabling unmasked SIMD FPU exception support... done.
<6>Checking 'hlt' instruction... OK.
<4>POSIX conformance testing by UNIFIX
<4>mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
<4>mtrr: detected mtrr type: Intel
<6>ACPI: Subsystem revision 20030619
<6>ACPI: Disabled via command line (acpi=off)
<6>PCI: PCI BIOS revision 2.10 entry at 0xfd9be, last bus=1
<6>PCI: Using configuration type 1
<6>PCI: Probing PCI hardware
<4>PCI: Probing PCI hardware (bus 00)
<6>PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
<6>PCI: Found IRQ 11 for device 00:04.0
<6>PCI: Sharing IRQ 11 with 00:04.1
<6>PCI: Sharing IRQ 11 with 01:01.0
<3>PCI: Cannot allocate resource region 4 of device 00:07.1
<6>Limiting direct PCI/PCI transfers.
<6>Linux NET4.0 for Linux 2.4
<6>Based upon Swansea University Computer Society NET3.039
<4>Initializing RT netlink socket
<6>apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
<4>PISCH: Plug In Scheduler Interface (Version 6)
<4>Starting kswapd
<4>bigpage subsystem: allocated 0 bigpages (=0MB).
<4>kinoded started
<5>VFS: Disk quotas vdquot_6.5.1
<5>aio_setup: num_physpages = 16380
<5>aio_setup: sizeof(struct page) = 48
<6>vesafb: framebuffer at 0xf0000000, mapped to 0xd0810000, size 8192k
<6>vesafb: mode is 1024x768x16, linelength=2048, pages=4
<6>vesafb: protected mode interface info at c000:8943
<6>vesafb: scrolling: redraw
<6>vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
<6>bootsplash 3.0.9-2003/09/08: looking for picture.... silenjpeg size
22326 bytes, found (1024x768, 11098 bytes, v3).
<6>bootsplash: silent jpeg found.
<6>bootsplash: silent jpeg found.
<4>Console: switching to colour frame buffer device 118x38
<6>fb0: VESA VGA frame buffer device
<4>pty: 256 Unix98 ptys configured
<6>Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS
MULTIPORT SHARE_IRQ SERIAL_PCI enabled
<6>ttyS00 at 0x03f8 (irq = 4) is a 16550A
<6>Real Time Clock Driver v1.10e
<6>Floppy drive(s): fd0 is 1.44M
<6>FDC 0 is a post-1991 82077
<4>RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
<6>loop: loaded (max 16 devices)
<6>Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
<6>ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
<6>PIIX4: IDE controller at PCI slot 00:07.1
<6>PIIX4: chipset revision 1
<6>PIIX4: not 100%% native mode: will probe irqs later
<6> ide0: BM-DMA at 0x1080-0x1087, BIOS settings: hda:DMA, hdb:pio
<6> ide1: BM-DMA at 0x1088-0x108f, BIOS settings: hdc:DMA, hdd:pio
<4>hda: TOSHIBA MK6021GAS, ATA DISK drive
<4>blk: queue c03bf900, I/O limit 4095Mb (mask 0xffffffff)
<4>hdc: TOSHIBA DVD-ROM SD-C2502, ATAPI CD/DVD-ROM drive
<4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
<4>ide1 at 0x170-0x177,0x376 on irq 15
<4>hda: attached ide-disk driver.
<4>hda: host protected area => 1
<6>hda: 117210240 sectors (60012 MB), CHS=7296/255/63, UDMA(33)
<6>ide-floppy driver 0.99.newide
<6>Partition check:
<6> hda: hda1 hda2 hda3 hda4
<6>ide-floppy driver 0.99.newide
<6>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
<6>md: Autodetecting RAID arrays.
<6>md: autorun ...
<6>md: ... autorun DONE.
<6>NET4: Linux TCP/IP 1.0 for NET4.0
<6>IP Protocols: ICMP, UDP, TCP, IGMP
<6>IP: routing cache hash table of 2048 buckets, 16Kbytes
<6>TCP: Hash tables configured (established 16384 bind 32768)
<6>Linux IP multicast router 0.06 plus PIM-SM
<6>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
<6>cryptoapi: loaded
<5>RAMDISK: Compressed image found at block 0
<6>Freeing initrd memory: 5364k freed
<4>VFS: Mounted root (minix filesystem).
<6>ide-floppy driver 0.99.newide
<6>Non-volatile memory driver v1.2
<6>SCSI subsystem driver Revision: 1.00
<4>hdc: attached ide-cdrom driver.
<6>hdc: ATAPI 24X DVD-ROM drive, 128kB Cache
<6>Uniform CD-ROM driver Revision: 3.12
<6>usb.c: registered new driver usbdevfs
<6>usb.c: registered new driver hub
<6>usb-uhci.c: $Revision: 1.275 $ time 13:50:22 Sep 24 2003
<6>usb-uhci.c: High bandwidth mode enabled
<6>PCI: Found IRQ 5 for device 00:07.2
<6>usb-uhci.c: USB UHCI at I/O 0x1060, IRQ 5
<4>usb-uhci.c: Detected 2 ports
<6>usb.c: new USB bus registered, assigned bus number 1
<6>hub.c: USB hub found
<6>hub.c: 2 ports detected
<6>usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
<6>usb.c: registered new driver hiddev
<6>usb.c: registered new driver hid
<6>hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik
ns >Hi, ns >I have a PIII/800Mhz 256MB RAM HP notebook, which has ben running Suse 8.2 ns >for some time and 8.0 for sometime before that. I was upgrading from 8.2 ns >to 9. Try rm -rf /tmp/* and remove anything in your user's home directory named *cop* (any case. ls -la - some of them are dotfiles). Reboot and try again. You could also try making a new use and logging into KDE as that user to see if the problems go away. Do you have a enough free disk space? I would suggest that you back up your data and reinstall. At least that way you'd have a nice clean system. JW
JW said:
ns >Hi, ns >I have a PIII/800Mhz 256MB RAM HP notebook, which has ben running Suse 8.2 ns >for some time and 8.0 for sometime before that. I was upgrading from 8.2 ns >to 9.
Try rm -rf /tmp/* and remove anything in your user's home directory named *cop* (any case. ls -la - some of them are dotfiles). Reboot and try again.
Actually I did the first, but not the second (fstab didn't show /dev/hda3 in the rescue mode) No soap. On reboot it complained that it was read only and that it couldn't fsck.
You could also try making a new use and logging into KDE as that user to see if the problems go away.
Not unless I can mount the /home directory in /dev/hda3, which I can't yet!
Do you have a enough free disk space?
More than enough, . ,
I would suggest that you back up your data and reinstall. At least that way you'd have a nice clean system.
THink that's the best option? Thanks! Nick
JW
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Saturday 27 March 2004 00.07, ns@nickselby.com wrote:
Hi, I have a PIII/800Mhz 256MB RAM HP notebook, which has ben running Suse 8.2 for some time and 8.0 for sometime before that. I was upgrading from 8.2 to 9.
/dev/hda1 is swap, /dev/hda2 is boot, /dev/hda3 is home.
After (**SLOW**) installation from the DVD, got a success message and rebooted. KDE's log in window appeared. I logged in as a user and whil the login prompts disappeared, leaving the KDE Welcome wallpaper,nothing hapened. I opened a terminal window and logged in as a user. Got prompted for the password, entered it, got told, You have mail in ... and then the cursor gflashed but did not give me a nick@machine prompt. Just flashed at me. Opened another terminal window and logged in as root - same thing.
Called Suse installation support. No help. But they did have me make a log in with the rescue function of the install dvd and make a floppy of the boot messages and hwinfo (below).
Then they went home for the weekend. Meanwhile my machine still completely down.
Please, please can anyone be of help?
Nick
Disk /dev/hda: 60.0 GB, 60011642880 bytes 255 heads, 63 sectors/track, 7296 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/hda1 1 99 795186 82 Linux swap /dev/hda2 * 100 3363 26218080 83 Linux /dev/hda3 3364 5974 20972857+ 83 Linux /dev/hda4 5975 7296 10618965 83 Linux
What is supposed to be on those partitions? Can you mount them at all? Say, for example, that hda2 is /, then does mkdir tmp mount /dev/hda2 tmp work? What, then, do you see in tmp/var/log/messages from your failed (flashing cursor) attempted login? Next try would be cd tmp chroot . Any interesting error messages? The boot log you posted looks like it's from the rescue system. It doesn't tell us anything interesting from what I can see. My guess is that the problem is something to do with packages that didn't get updated properly. If this is indeed the problem, then you may have to be sneaky in correcting it
I've moved forward: Anders Johansson said:
On Saturday 27 March 2004 00.07, ns@nickselby.com wrote:
<snip>the login prompts disappeared, leaving the KDE Welcome wallpaper,nothing hapened. I opened a terminal window and logged in as a user. Got prompted for the password, entered it, got told, You have mail in ... and then the cursor gflashed but did not give me a nick@machine prompt. Just flashed at me. Opened another terminal window and logged in as root - same thing.
</snip>
What is supposed to be on those partitions? Can you mount them at all? Say, for example, that hda2 is /, then does
mkdir tmp mount /dev/hda2 tmp
work? What, then, do you see in tmp/var/log/messages from your failed (flashing cursor) attempted login?
Next try would be
cd tmp chroot .
Any interesting error messages?
The boot log you posted looks like it's from the rescue system. It doesn't tell us anything interesting from what I can see.
My guess is that the problem is something to do with packages that didn't get updated properly. If this is indeed the problem, then you may have to be sneaky in correcting it
I found that the problems were two fold: First, /hda3 which is the home partition, was in need of a --rebuild-tree and I did that. I then re-installed cleanly - Suse 9.0 onto /dev/hda2 This let me boot fully and get into KDE. When I noticed the OTHER problem and the real issue: I was unable (or didn't see it) to tell how to let YAST know that the home directory for all my files was on /dev/hda3 . It asked me the user name and passwrd and I told it, but as I hadn't had the chance yet to put /dev/hda3 into the ftab at the time, it didn't give me the option to use /dev/hda3/username as the home directory. I was able to create a user on the new /dev/hda2/home directory, and I was able to create a user using the directory /dev/hda3/username directory. HOWEVER, while I can log into the first, when I try to log into the second KDE complains that it can't find files, including dcop server, and crashes. Obviously, because the config files in that directory are left over from when iut was a home directory in my Suse 8.2 installation. So: I guess the question is, which .files should I replace in the old -dev/hda3/username - directory in order that they be updated by 9.0's Yast when it creates a user? How can I replace the config files in the /dev/hda3/username director[es] so that the new installation will recognize /dev/hda3 as "home" and delete the /home directory in /dev/hda2 ? Thanks in advance, Nick
On Saturday 27 March 2004 18.30, ns@nickselby.com wrote:
I was unable (or didn't see it) to tell how to let YAST know that the home directory for all my files was on /dev/hda3 .
You could have done it in the "expert partitioning" dialog. Simply select "/home" as the mount point for hda3 and tell it not to format it. It's possible to do that in the installation.
It asked me the user name and passwrd and I told it, but as I hadn't had the chance yet to put /dev/hda3 into the ftab at the time, it didn't give me the option to use /dev/hda3/username as the home directory.
I was able to create a user on the new /dev/hda2/home directory, and I was able to create a user using the directory /dev/hda3/username directory. HOWEVER, while I can log into the first, when I try to log into the second KDE complains that it can't find files, including dcop server, and crashes. Obviously, because the config files in that directory are left over from when iut was a home directory in my Suse 8.2 installation.
So: I guess the question is, which .files should I replace in the old -dev/hda3/username - directory in order that they be updated by 9.0's Yast when it creates a user? How can I replace the config files in the /dev/hda3/username director[es] so that the new installation will recognize /dev/hda3 as "home" and delete the /home directory in /dev/hda2 ?
Well, you don't want to delete /home on hda2, you want to use it as a mount point for hda3. Log in as root (that way, /home will be unused for the duration of this exercise), delete the directories you have under your new /home (or move them to hda3, depending on whether you want to keep them or not), then add a line to fstab like /dev/hda3 /home reiserfs defaults 1 2 (all in one line, naturally) Then unmount hda3 in case it is already mounted, and do "mount /home". If you already have a line in fstab pointing to hda3, then delete it. Then you're done. As for the KDE config files, the quickie way is to delete or rename /home/<user>/.kde and let it get regenerated on login. Also, in case you didn't already check it (you didn't mention it so I don't know) make sure that the home directory is actually owned by the new user you created. If you tell YaST's user creation that the home dir should be a preexisting directory, it may not be (no, not a bug, there are times when you don't want a home directory to be owned by the user, but it does make logging in with that user a bit more difficult)
**Yay! Thanks! One teeny problem left: Anders Johansson said:
On Saturday 27 March 2004 18.30, ns@nickselby.com wrote:
I was unable (or didn't see it) to tell how to let YAST know that the home directory for all my files was on /dev/hda3 .
You could have done it in the "expert partitioning" dialog. Simply select "/home" as the mount point for hda3 and tell it not to format it. It's possible to do that in the installation.
Never saw the dialog. Must be user error.
It asked me the user name and passwrd and I told it, but as I hadn't had the chance yet to put /dev/hda3 into the ftab at the time, it didn't give me the option to use /dev/hda3/username as the home directory.
I was able to create a user on the new /dev/hda2/home directory, and I was able to create a user using the directory /dev/hda3/username directory. HOWEVER, while I can log into the first, when I try to log into the second KDE complains that it can't find files, including dcop server, and crashes. Obviously, because the config files in that directory are left over from when iut was a home directory in my Suse 8.2 installation.
So: I guess the question is, which .files should I replace in the old -dev/hda3/username - directory in order that they be updated by 9.0's Yast when it creates a user? How can I replace the config files in the /dev/hda3/username director[es] so that the new installation will recognize /dev/hda3 as "home" and delete the /home directory in /dev/hda2 ?
Well, you don't want to delete /home on hda2, you want to use it as a mount point for hda3.
Ah, yes. I do.
Log in as root (that way, /home will be unused for the duration of this exercise), delete the directories you have under your new /home (or move them to hda3, depending on whether you want to keep them or not), then add a line to fstab like
/dev/hda3 /home reiserfs defaults 1 2
(all in one line, naturally)
Then unmount hda3 in case it is already mounted, and do "mount /home". If you already have a line in fstab pointing to hda3, then delete it. Then you're done.
From your lips to my machine's ears. Done.
As for the KDE config files, the quickie way is to delete or rename /home/<user>/.kde and let it get regenerated on login.
Done too! I can log in and it finds all the old files no worries. Another HAPPY ending thanks to the wonderful people on this list.
Also, in case you didn't already check it (you didn't mention it so I don't know) make sure that the home directory is actually owned by the new user you created. If you tell YaST's user creation that the home dir should be a preexisting directory, it may not be (no, not a bug, there are times when you don't want a home directory to be owned by the user, but it does make logging in with that user a bit more difficult)
It prompted me: You want to set this user's home directory to /home/[user] , which this user currently owns? So I said yes. But I could see the proble if this user didn't own it. THANK YOU anders! Nick
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Thanks to all who posted The problems were: 1. /dev/hda3 needed a tree rebuild 2. I deleted the .kde directory from the [user] subdirectories on the /dev/ hda3 drive 3. changed fstab to mount /dev/hda3 as /home 4. Recreated users with the home directories of /home/[user] and said yes when told that the user already owned that directory 5. the .kde files were recreated when I logged in, Thank you again, all of you on the list, for the help. nick On Saturday 27 March 2004 19:16, ns@nickselby.com wrote:
**Yay! Thanks! One teeny problem left:
Anders Johansson said:
On Saturday 27 March 2004 18.30, ns@nickselby.com wrote:
I was unable (or didn't see it) to tell how to let YAST know that the home directory for all my files was on /dev/hda3 .
You could have done it in the "expert partitioning" dialog. Simply select "/home" as the mount point for hda3 and tell it not to format it. It's possible to do that in the installation.
Never saw the dialog. Must be user error.
It asked me the user name and passwrd and I told it, but as I hadn't had the chance yet to put /dev/hda3 into the ftab at the time, it didn't give me the option to use /dev/hda3/username as the home directory.
I was able to create a user on the new /dev/hda2/home directory, and I was able to create a user using the directory /dev/hda3/username directory. HOWEVER, while I can log into the first, when I try to log into the second KDE complains that it can't find files, including dcop server, and crashes. Obviously, because the config files in that directory are left over from when iut was a home directory in my Suse 8.2 installation.
So: I guess the question is, which .files should I replace in the old -dev/hda3/username - directory in order that they be updated by 9.0's Yast when it creates a user? How can I replace the config files in the /dev/hda3/username director[es] so that the new installation will recognize /dev/hda3 as "home" and delete the /home directory in /dev/hda2 ?
Well, you don't want to delete /home on hda2, you want to use it as a mount point for hda3.
Ah, yes. I do.
Log in as root (that way, /home will be unused for the duration of this exercise), delete the directories you have under your new /home (or move them to hda3, depending on whether you want to keep them or not), then add a line to fstab like
/dev/hda3 /home reiserfs defaults 1 2
(all in one line, naturally)
Then unmount hda3 in case it is already mounted, and do "mount /home". If you already have a line in fstab pointing to hda3, then delete it. Then you're done.
From your lips to my machine's ears. Done.
As for the KDE config files, the quickie way is to delete or rename /home/<user>/.kde and let it get regenerated on login.
Done too! I can log in and it finds all the old files no worries.
Another HAPPY ending thanks to the wonderful people on this list.
Also, in case you didn't already check it (you didn't mention it so I don't know) make sure that the home directory is actually owned by the new user you created. If you tell YaST's user creation that the home dir should be a preexisting directory, it may not be (no, not a bug, there are times when you don't want a home directory to be owned by the user, but it does make logging in with that user a bit more difficult)
It prompted me: You want to set this user's home directory to /home/[user] , which this user currently owns?
So I said yes. But I could see the proble if this user didn't own it.
THANK YOU anders!
Nick
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
*** Reply to message from ns@nickselby.com on Fri, 26 Mar 2004 18:07:34 -0500 (EST)***
I have a PIII/800Mhz 256MB RAM HP notebook, which has ben running Suse 8.2 for some time and 8.0 for sometime before that. I was upgrading from 8.2
okay, maybe it's just my confusion but could we havbe a "clarification of terms" please.. when you say "upgrading" are you talking about a new clean install, or an "update" which isn't the best way to do it, but will work on occassion.. Usually w/ a lot of care and gentle persuesion... Tho , I think I would just get anything like Partition Magic and erase whatever is there, format the drive as fat 32 and start over ( that way Suse will either ask if you want it to use all the disk , or present you w/ a partition scheme which reserves some amount of space for windows... which you then delete and turn into /home, or any other mount point you like.. The only reason to overwrite w/ a fat32 system is at that point you tell Suse to reformat and at least you have a clean starting point... No partition majic? any old windows install disk will certainly attempt to overwrite your drive... none of those ( lucky you! (G) ) make certain you tell Suse's install to reformat each segment in your install scheme.. like I said, starting w/ a clean drive at least lets you isolate the bad things that might happen to something in the install certainly, otherwise there is all this other stuff to check thru.. Since you've upgraded before , you probably already backed up everything important to you. One other thing, IF you have a usb card reader w/ nothing in the slots, the install has hung at that spot on a couple of my boxes here. However, solution was simple, unplug usb reader, or put a car into it that has something it can read... unplug is the fastest thing, and when it's plugged in after you get a desktop 9.0 is very quick about recognising it, AS LONG AS THERE IS A DISK (CF or whatever) THAT HAS DATA ON IT... it will simply pop up on your DT w/ windows C or D or ??? however many slots you have w/ data cards in them... -- j -- nemo me impune lacessit it's just an afterthought; okay ? : Drilling for oil is boring.
Hi, From my point of view it seems that hda3 is not being mounted. If all home directories are there then the system will try to find the home directory as you log in. When it cannot find the home directory in question, it just stops there. The strange thing is that the problem is also showing when you log as root. If I were you I would boot from the cd, go into shell prompt, mount the file systems manually and do an fsck on them, one at a time. Thanks Geoffrey Said SuSE Linux 8.0 Malta ns@nickselby.com (27/3/04 12?07):
Hi, I have a PIII/800Mhz 256MB RAM HP notebook, which has ben running Suse 8.2 for some time and 8.0 for sometime before that. I was upgrading from 8.2 to 9.
/dev/hda1 is swap, /dev/hda2 is boot, /dev/hda3 is home.
After (**SLOW**) installation from the DVD, got a success message and rebooted. KDE's log in window appeared. I logged in as a user and whil the login prompts disappeared, leaving the KDE Welcome wallpaper,nothing hapened. I opened a terminal window and logged in as a user. Got prompted for the password, entered it, got told, You have mail in ... and then the cursor gflashed but did not give me a nick@machine prompt. Just flashed at me. Opened another terminal window and logged in as root - same thing.
Called Suse installation support. No help. But they did have me make a log in with the rescue function of the install dvd and make a floppy of the boot messages and hwinfo (below).
Then they went home for the weekend. Meanwhile my machine still completely down.
Please, please can anyone be of help?
Nick
Disk /dev/hda: 60.0 GB, 60011642880 bytes 255 heads, 63 sectors/track, 7296 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/hda1 1 99 795186 82 Linux swap /dev/hda2 * 100 3363 26218080 83 Linux /dev/hda3 3364 5974 20972857+ 83 Linux /dev/hda4 5975 7296 10618965 83 Linux Cannot find map file. Loaded 596 symbols from 21 modules. klogd 1.4.1, log source = ksyslog started. <4>Linux version 2.4.21-99-default (root@i386.suse.de) (gcc version 3.3.1 (SuSE Linux)) #1 Wed Sep 24 13:30:51 UTC 2003 <6>BIOS-provided physical RAM map: <4> BIOS-e820: 0000000000000000 - 000000000009f400 (usable) <4> BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved) <4> BIOS-e820: 00000000000eac00 - 0000000000100000 (reserved) <4> BIOS-e820: 0000000000100000 - 000000000fff0000 (usable) <4> BIOS-e820: 000000000fff0000 - 000000000ffffc00 (ACPI data) <4> BIOS-e820: 000000000ffffc00 - 0000000010000000 (ACPI NVS) <4> BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved) <5>757MB vmalloc/ioremap area available. <5>0MB HIGHMEM available. <5>255MB LOWMEM available. <7>ACPI: have wakeup address 0xc0001000 <4>On node 0 totalpages: 65520 <4>zone(0): 4096 pages. <4>zone(1): 61424 pages. <4>zone(2): 0 pages. <5>ACPI disabled because your bios is from 1992 and too old <5>You can enable it with acpi=force <4>Building zonelist for node : 0 <4>Kernel command line: BOOT_IMAGE=linux SuSE=,1203200080,81AAC7B0., initrd=initrd ramdisk_size=65536 rescue=1 vga=0x317 splash=silent <6>bootsplash: silent mode. <6>Initializing CPU#0 <4>Detected 696.982 MHz processor. <4>Console: colour dummy device 80x25 <4>Calibrating delay loop... 1389.36 BogoMIPS <6>Memory: 250288k/262080k available (1590k kernel code, 11404k reserved, 605k data, 160k init, 0k highmem) <6>Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) <6>Inode cache hash table entries: 16384 (order: 5, 131072 bytes) <6>Mount cache hash table entries: 512 (order: 0, 4096 bytes) <4>Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes) <4>Page-cache hash table entries: 65536 (order: 6, 262144 bytes) <6>CPU: L1 I cache: 16K, L1 D cache: 16K <6>CPU: L2 cache: 256K <5>CPU serial number disabled. <6>Intel machine check architecture supported. <6>Intel machine check reporting enabled on CPU#0. <7>CPU: After generic, caps: 0383f9ff 00000000 00000000 00000000 <7>CPU: Common caps: 0383f9ff 00000000 00000000 00000000 <4>CPU: Intel Pentium III (Coppermine) stepping 06 <6>Enabling fast FPU save and restore... done. <6>Enabling unmasked SIMD FPU exception support... done. <6>Checking 'hlt' instruction... OK. <4>POSIX conformance testing by UNIFIX <4>mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au) <4>mtrr: detected mtrr type: Intel <6>ACPI: Subsystem revision 20030619 <6>ACPI: Disabled via command line (acpi=off) <6>PCI: PCI BIOS revision 2.10 entry at 0xfd9be, last bus=1 <6>PCI: Using configuration type 1 <6>PCI: Probing PCI hardware <4>PCI: Probing PCI hardware (bus 00) <6>PCI: Using IRQ router PIIX [8086/7110] at 00:07.0 <6>PCI: Found IRQ 11 for device 00:04.0 <6>PCI: Sharing IRQ 11 with 00:04.1 <6>PCI: Sharing IRQ 11 with 01:01.0 <3>PCI: Cannot allocate resource region 4 of device 00:07.1 <6>Limiting direct PCI/PCI transfers. <6>Linux NET4.0 for Linux 2.4 <6>Based upon Swansea University Computer Society NET3.039 <4>Initializing RT netlink socket <6>apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16) <4>PISCH: Plug In Scheduler Interface (Version 6) <4>Starting kswapd <4>bigpage subsystem: allocated 0 bigpages (=0MB). <4>kinoded started <5>VFS: Disk quotas vdquot_6.5.1 <5>aio_setup: num_physpages = 16380 <5>aio_setup: sizeof(struct page) = 48 <6>vesafb: framebuffer at 0xf0000000, mapped to 0xd0810000, size 8192k <6>vesafb: mode is 1024x768x16, linelength=2048, pages=4 <6>vesafb: protected mode interface info at c000:8943 <6>vesafb: scrolling: redraw <6>vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0 <6>bootsplash 3.0.9-2003/09/08: looking for picture.... silenjpeg size 22326 bytes, found (1024x768, 11098 bytes, v3). <6>bootsplash: silent jpeg found. <6>bootsplash: silent jpeg found. <4>Console: switching to colour frame buffer device 118x38 <6>fb0: VESA VGA frame buffer device <4>pty: 256 Unix98 ptys configured <6>Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enabled <6>ttyS00 at 0x03f8 (irq = 4) is a 16550A <6>Real Time Clock Driver v1.10e <6>Floppy drive(s): fd0 is 1.44M <6>FDC 0 is a post-1991 82077 <4>RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize <6>loop: loaded (max 16 devices) <6>Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 <6>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx <6>PIIX4: IDE controller at PCI slot 00:07.1 <6>PIIX4: chipset revision 1 <6>PIIX4: not 100%% native mode: will probe irqs later <6> ide0: BM-DMA at 0x1080-0x1087, BIOS settings: hda:DMA, hdb:pio <6> ide1: BM-DMA at 0x1088-0x108f, BIOS settings: hdc:DMA, hdd:pio <4>hda: TOSHIBA MK6021GAS, ATA DISK drive <4>blk: queue c03bf900, I/O limit 4095Mb (mask 0xffffffff) <4>hdc: TOSHIBA DVD-ROM SD-C2502, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <4>hda: attached ide-disk driver. <4>hda: host protected area => 1 <6>hda: 117210240 sectors (60012 MB), CHS=7296/255/63, UDMA(33) <6>ide-floppy driver 0.99.newide <6>Partition check: <6> hda: hda1 hda2 hda3 hda4 <6>ide-floppy driver 0.99.newide <6>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 <6>md: Autodetecting RAID arrays. <6>md: autorun ... <6>md: ... autorun DONE. <6>NET4: Linux TCP/IP 1.0 for NET4.0 <6>IP Protocols: ICMP, UDP, TCP, IGMP <6>IP: routing cache hash table of 2048 buckets, 16Kbytes <6>TCP: Hash tables configured (established 16384 bind 32768) <6>Linux IP multicast router 0.06 plus PIM-SM <6>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. <6>cryptoapi: loaded <5>RAMDISK: Compressed image found at block 0 <6>Freeing initrd memory: 5364k freed <4>VFS: Mounted root (minix filesystem). <6>ide-floppy driver 0.99.newide <6>Non-volatile memory driver v1.2 <6>SCSI subsystem driver Revision: 1.00 <4>hdc: attached ide-cdrom driver. <6>hdc: ATAPI 24X DVD-ROM drive, 128kB Cache <6>Uniform CD-ROM driver Revision: 3.12 <6>usb.c: registered new driver usbdevfs <6>usb.c: registered new driver hub <6>usb-uhci.c: $Revision: 1.275 $ time 13:50:22 Sep 24 2003 <6>usb-uhci.c: High bandwidth mode enabled <6>PCI: Found IRQ 5 for device 00:07.2 <6>usb-uhci.c: USB UHCI at I/O 0x1060, IRQ 5 <4>usb-uhci.c: Detected 2 ports <6>usb.c: new USB bus registered, assigned bus number 1 <6>hub.c: USB hub found <6>hub.c: 2 ports detected <6>usb-uhci.c: v1.275:USB Universal Host Controller Interface driver <6>usb.c: registered new driver hiddev <6>usb.c: registered new driver hid <6>hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik
<6>hid-core.c: USB HID support drivers <6>Initializing USB Mass Storage driver... <6>usb.c: registered new driver usb-storage <6>USB Mass Storage support registered. <4>VFS: Can't find a Minix or Minix V2 filesystem on device 02:00. <4>VFS: Can't find ext2 filesystem on dev fd(2,0). <6>Linux Kernel Card Services 3.1.22 <6> options: [pci] [cardbus] [pm] <6>PCI: Found IRQ 11 for device 00:04.0 <6>PCI: Sharing IRQ 11 with 00:04.1 <6>PCI: Sharing IRQ 11 with 01:01.0 <6>PCI: Found IRQ 11 for device 00:04.1 <6>PCI: Sharing IRQ 11 with 00:04.0 <6>PCI: Sharing IRQ 11 with 01:01.0 <4>Yenta IRQ list 0698, PCI irq11 <4>Socket status: 30000010 <4>Yenta IRQ list 0698, PCI irq11 <4>Socket status: 30000010 <6>cs: IO port probe 0x0c00-0x0cff: clean. <6>cs: IO port probe 0x0820-0x08ff: clean. <6>cs: IO port probe 0x0800-0x080f: clean. <6>cs: IO port probe 0x03e0-0x04ff: excluding 0x4d0-0x4d7 <6>cs: IO port probe 0x0100-0x03af: excluding 0x378-0x37f <6>cs: IO port probe 0x0a00-0x0aff: clean. <6>cs: memory probe 0xa0000000-0xa0ffffff: clean. <7>ISO 9660 Extensions: Microsoft Joliet Level 3 <7>ISO 9660 Extensions: RRIP_1991A <6>Linux Tulip driver version 0.9.15-pre12 (Nov 11, 2002) <6>PCI: Found IRQ 11 for device 00:10.0 <4>SMC1255 card found with board_id: 0 <6>eth0: ADMtek Comet rev 17 at 0x1c00, 00:D0:59:31:57:27, IRQ 11. <4>VFS: Mounted root (ext2 filesystem) readonly. <5>Trying to move old root to /initrd ... failed <5>Unmounting old root <5>Trying to free ramdisk memory ... okay <6>Freeing unused kernel memory: 160k freed <6>md: Autodetecting RAID arrays. <6>md: autorun ... <6>md: ... autorun DONE. Kernel logging (ksyslog) stopped. Kernel log daemon terminating. Boot logging started on /dev/tty1(/dev/console) at Fri Mar 26 10:58:24 2004
<notice>run boot scripts (setserial boot.proc) Configuring serial ports... ttyS0 at 0x03f8 (irq = 4) is a 16550A Configured serial ports done<notice>exit status of (setserial boot.proc) is (0 0) <notice>run boot scripts (boot.md) <notice>exit status of (boot.md) is (0) <notice>run boot scripts (boot.lvm) Activating swap-devices in /etc/fstab... done<notice>exit status of (boot.lvm) is (0) <notice>run boot scripts (boot.localfs) Checking file systems... fsck 1.34 (25-Jul-2003) doneMounting local file systems... proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) nothing was mounted done<notice>exit status of (boot.localfs) is (0) <notice>run boot scripts (boot.crypto) <notice>exit status of (boot.crypto) is (0) <notice>run boot scripts (boot.swap boot.restore_permissions boot.klog) Activating remaining swap-devices in /etc/fstab... doneMounting shared memory FS on /dev/shmdone Restore device permissionsdone Creating /var/log/boot.msg done<notice>killproc: kill(212,29) <notice>exit status of (boot.swap boot.restore_permissions boot.klog) is (0 0 0) <notice>run boot scripts (boot.idedma boot.clock) Setting up the CMOS clockdone Setting up linker cache (/etc/ld.so.cache) using ldconfigdone <notice>exit status of (boot.idedma boot.clock) is (0 0) <notice>run boot scripts (boot.ldconfig) <notice>exit status of (boot.ldconfig) is (0) <notice>run boot scripts (boot.localnet) Setting up hostname 'Rescue'done Setting up loopback interface done <notice>exit status of (boot.localnet) is (0) <notice>run boot scripts (boot.ipconfig) Enabling syn flood protectiondone Disabling IP forwardingdone <notice>exit status of (boot.ipconfig) is (0) System Boot Control: The system has been setup System Boot Control: Running /etc/init.d/boot.local Fri Mar 26 10:58:29 UTC 2004 no modification in inittab needed for: tty1 done<notice>killproc: kill(335,3) <notice>
Boot logging started on /dev/tty1(/dev/console) at Fri Mar 26 10:58:29 2004
Master Resource Control: previous runlevel: N, switching to runlevel: 3 Initializing random number generatordone <notice>start services (random) <notice>exit status of (random) is (0) <notice>start services (syslog) Starting syslog services<notice>startproc: execve (/sbin/syslogd) [ /sbin/syslogd ], [ SuSE=,1203200080,81AAC7B0., rescue=1 CONSOLE=/dev/console TERM=linux SHELL=/bin/sh progress=1 INIT_VERSION=sysvinit-2.82 initrd=initrd REDIRECT=/dev/tty1 COLUMNS=118 PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin vga=0x317 RUNLEVEL=3 PWD=/ PREVLEVEL=N LINES=38 HOME=/ SHLVL=2 BOOT_IMAGE=linux splash=silent sscripts=4 _=/sbin/startproc DAEMON=/sbin/syslogd ] <notice>startproc: execve (/sbin/klogd) [ /sbin/klogd -c 1 -2 ], [ SuSE=,1203200080,81AAC7B0., rescue=1 CONSOLE=/dev/console TERM=linux SHELL=/bin/sh progress=1 INIT_VERSION=sysvinit-2.82 initrd=initrd REDIRECT=/dev/tty1 COLUMNS=118 PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin vga=0x317 RUNLEVEL=3 PWD=/ PREVLEVEL=N LINES=38 HOME=/ SHLVL=2 BOOT_IMAGE=linux splash=silent sscripts=4 _=/sbin/startproc DAEMON=/sbin/klogd ] done <notice>exit status of (syslog) is (0) <notice>start services (portmap) Starting RPC portmap daemon<notice>startproc: execve (/sbin/portmap) [ /sbin/portmap ], [ SuSE=,1203200080,81AAC7B0., rescue=1 CONSOLE=/dev/console TERM=linux SHELL=/bin/sh progress=2 INIT_VERSION=sysvinit-2.82 initrd=initrd REDIRECT=/dev/tty1 COLUMNS=118 PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin vga=0x317 RUNLEVEL=3 PWD=/ PREVLEVEL=N LINES=38 HOME=/ SHLVL=2 BOOT_IMAGE=linux splash=silent sscripts=4 _=/sbin/startproc DAEMON=/sbin/portmap ] done Starting Name Service Cache Daemon<notice>exit status of (portmap) is (0) <notice>start services (nscd) <notice>startproc: execve (/usr/sbin/nscd) [ /usr/sbin/nscd ], [ SuSE=,1203200080,81AAC7B0., rescue=1 CONSOLE=/dev/console TERM=linux SHELL=/bin/sh progress=3 INIT_VERSION=sysvinit-2.82 initrd=initrd REDIRECT=/dev/tty1 COLUMNS=118 PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin vga=0x317 RUNLEVEL=3 PWD=/ PREVLEVEL=N LINES=38 HOME=/ SHLVL=2 BOOT_IMAGE=linux splash=silent sscripts=4 _=/sbin/startproc DAEMON=/usr/sbin/nscd ] done Master Resource Control: runlevel 3 has been reached <notice>exit status of (nscd) is (0) <notice>killproc: kill(473,3)
-- Nick Selby, Flyguides, Inc 103 Foulk Rd, Suite 202, Wilmington, DE 19803 USA 1-866-FLYGUIDES (1-866-359-4843)| Ex-US: 1-302-691-6056 http://flyguides.com | nick.selby@flyguides.com US Fax: 1-302-652-8667 US Mobile: +1 347 804 4410
Germany phone: 49 892 737 4527/8 Germany fax: 49 892 737 4529 UK Mobile: +44 781 592 5713
Flyguides(r) is a registered trademark of Flyguides, Inc.
Attachments:
info.txt 13 k [ text/plain ] download | view
Delete & Prev | Delete & Next Move to: INBOX INBOX.Drafts INBOX.Sent INBOX.Trash INBOX/suse-list INBOX/Test
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-----Original Message-----
From: "Said Geoffrey at MITTS"
Hi,
From my point of view it seems that hda3 is not being mounted. If all home directories are there then the system will try to find the home directory as you log in. When it cannot find the home directory in question, it just stops there.
The strange thing is that the problem is also showing when you log as root. If I were you I would boot from the cd, go into shell prompt, mount the file systems manually and do an fsck on them, one at a time.
You -don't- run fsck on mounted filesystems. Run fsck on them one at a time and then mount them. Ken
Sorry for the mistake Thanks Geoffrey Ken Schneider (27/3/04 12?48):
-----Original Message----- From: "Said Geoffrey at MITTS"
To: suse-linux-e@suse.com Date: 27 Mar 2004 08:46:00 +0100 Subject: [SLE] Re:[SLE] Please Help: upgrade from 8.2 to 9 problem Hi,
From my point of view it seems that hda3 is not being mounted. If all home directories are there then the system will try to find the home directory as you log in. When it cannot find the home directory in question, it just stops there.
The strange thing is that the problem is also showing when you log as root. If I were you I would boot from the cd, go into shell prompt, mount the file systems manually and do an fsck on them, one at a time.
You -don't- run fsck on mounted filesystems. Run fsck on them one at a time and then mount them.
Ken
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (7)
-
Anders Johansson
-
jfweber@bellsouth.net
-
JW
-
Ken Schneider
-
Nick
-
ns@nickselby.com
-
Said Geoffrey@MITTS