8.0 - Am I dreaming ...pinch me please !
Man is this one nice version for SuSE! No problems at all to report. Thanks so much for a job well done . /Dee Running Linux since Red Hat 2.0 and SuSE since 5.0.
On Mon, 2002-04-29 at 22:47, W.D. McKinney wrote:
Man is this one nice version for SuSE! No problems at all to report. Thanks so much for a job well done .
/Dee
Running Linux since Red Hat 2.0 and SuSE since 5.0.
Hey Dee and others, Cool Runnings, eh ? I second that. Just as curious, if you have multi partitions already across different drives. You see, I have 4 10k SCSI drives with ,I think, 7/8 partitions. All, bar /boot and /extra running REISERFS. And more importantly 2 swaps partitions also. So, during the upgrade, the system would baulk repeatedly, until I disabled one of the swap partitions. Can you comment on any ideosyncracies here, no matter how hidden ? Cheers -- Kemdi IN_SuSE_d Since 5.2 123792 of counter.li.org ICQ:112290572
On Tuesday 30 April 2002 6:22 am, Uzo Kemdi Anyamele wrote:
On Mon, 2002-04-29 at 22:47, W.D. McKinney wrote:
Man is this one nice version for SuSE! No problems at all to report. Thanks so much for a job well done .
/Dee
Running Linux since Red Hat 2.0 and SuSE since 5.0.
Hey Dee and others,
Cool Runnings, eh ? I second that.
Just as curious, if you have multi partitions already across different drives.
You see, I have 4 10k SCSI drives with ,I think, 7/8 partitions. All, bar /boot and /extra running REISERFS. And more importantly 2 swaps partitions also.
So, during the upgrade, the system would baulk repeatedly, until I disabled one of the swap partitions.
Can you comment on any ideosyncracies here, no matter how hidden ?
Cheers
I'm having much the same problems with a new install. I have an all-SCSI unit with two drives. The install runs fine but on re-boot I get an 'fsck failed' message, and told to remount the root in RW mode and do the fsck manually. Ok, but doing that doesn't solve the problem. Another reboot and its right back to the same problem. I was trying to make the root EXT3 and finally gave up on that since I was getting the fsck problem. I'm about ready to send 8.0 back. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 04/30/02 05:46 + +----------------------------------------------------------------------------+ "Heard on Noahs' ark: Sailing is fun, but scrubbing the decks is aardvark."
On Tue, 2002-04-30 at 09:51, Bruce Marshall wrote:
On Tuesday 30 April 2002 6:22 am, Uzo Kemdi Anyamele wrote:
On Mon, 2002-04-29 at 22:47, W.D. McKinney wrote:
Man is this one nice version for SuSE! No problems at all to report. Thanks so much for a job well done .
/Dee
Running Linux since Red Hat 2.0 and SuSE since 5.0.
Hey Dee and others,
Cool Runnings, eh ? I second that.
Just as curious, if you have multi partitions already across different drives.
You see, I have 4 10k SCSI drives with ,I think, 7/8 partitions. All, bar /boot and /extra running REISERFS. And more importantly 2 swaps partitions also.
So, during the upgrade, the system would baulk repeatedly, until I disabled one of the swap partitions.
Can you comment on any ideosyncracies here, no matter how hidden ?
Cheers
I'm having much the same problems with a new install. I have an all-SCSI unit with two drives. The install runs fine but on re-boot I get an 'fsck failed' message, and told to remount the root in RW mode and do the fsck manually. Ok, but doing that doesn't solve the problem. Another reboot and its right back to the same problem.
I was trying to make the root EXT3 and finally gave up on that since I was getting the fsck problem.
I'm about ready to send 8.0 back.
Please, no.... not yet !! The senerio you described, I encountered also. During install, did you at least try and read your active /etc/fstab file ? i.e if you, like me use the expert partitioning options ? I think that the default, during update or clean install is for the installer to want to format any disk in its way, but I've always refused it that pleasure , as I have several partitions going back in time that I've always kept and their data and files too. Just make the /boot default to ext2 and format that. Then try to match the others to what your original layout used to be. And make sure , you've asked for no formating of your precious partitions. Better still, just post your /etc/fstab here, so we can take a look. Here's mine, /dev/sdb3 / reiserfs defaults 1 2 /dev/sda1 /boot ext2 defaults 1 2 /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 devpts /dev/pts devpts defaults 0 0 /dev/dvd /media/dvd auto ro,noauto,user,exec 0 0 /dev/sda2 /extra ext2 defaults 1 2 /dev/sda3 /home reiserfs defaults 1 2 /dev/sdc2 /local reiserfs defaults 1 2 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/pda /media/sparQ auto rw,auto,user,exec 0 0 /dev/sdd1 /multimedia reiserfs defaults 1 2 /dev/sda4 /opt reiserfs defaults 1 2 proc /proc proc defaults 0 0 usbdevfs /proc/bus/usb usbdevfs noauto 0 0 /dev/sdb2 /usr reiserfs defaults 1 2 /dev/sdb4 /var reiserfs defaults 1 2 /dev/hdd4 /media/zip auto noauto,user 0 0 /dev/sdb1 swap swap pri=42 0 0 /dev/sdc1 swap swap pri=42 0 0 CHEERS -- Kemdi IN_SuSE_d Since 5.2 123792 of counter.li.org ICQ:112290572
On Tuesday 30 April 2002 11:10 am, Uzo Kemdi Anyamele wrote:
Please, no.... not yet !!
The senerio you described, I encountered also. During install, did you at least try and read your active /etc/fstab file ? i.e if you, like me use the expert partitioning options ?
I think that the default, during update or clean install is for the installer to want to format any disk in its way, but I've always refused it that pleasure , as I have several partitions going back in time that I've always kept and their data and files too.
Just make the /boot default to ext2 and format that. Then try to match the others to what your original layout used to be. And make sure , you've asked for no formating of your precious partitions.
Better still, just post your /etc/fstab here, so we can take a look.
Well here's what I do for an install. 1) No, I don't let it partition on its own. I always make my partitions ahead of time for /boot and / and let it format those. 2) I originally told it to format /boot as EXT2 and / as EXT3 which is what I really want, and then I ran into the problem. But I also 'added in' some of my old partitions such as /home and /ftparea which were already in EXT3 and I didn't let it format those. 3) I finally got down to just using /swap, a new /boot, and a new / with the latter formatted in EXT2 and that got me into the system one time at which point I probably played with fstab and added in some other partitions. If I had to guess, I would say that the install DID NOT set up initrd to allow for EXT3 partitions, a severe error in my estimation and it must have something to do with a relationship with also having SCSI because I was able to install on a laptop (IDE) with / being formatted to EXT3 and it went just fine. I need to get back and play with it but if I can't even get it to run, then what other problems are lurking beyond that? -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 04/30/02 15:02 + +----------------------------------------------------------------------------+ "We're going to turn this team around 360 degrees." -Jason Kidd, upon his drafting to the Dallas Mavericks
On Tue, 2002-04-30 at 19:08, Bruce Marshall wrote:
1) No, I don't let it partition on its own. I always make my partitions ahead of time for /boot and / and let it format those.
2) I originally told it to format /boot as EXT2 and / as EXT3 which is what I really want, and then I ran into the problem. But I also 'added in' some of my old partitions such as /home and /ftparea which were already in EXT3 and I didn't let it format those.
3) I finally got down to just using /swap, a new /boot, and a new / with the latter formatted in EXT2 and that got me into the system one time at which point I probably played with fstab and added in some other partitions.
If I had to guess, I would say that the install DID NOT set up initrd to allow for EXT3 partitions, a severe error in my estimation and it must have something to do with a relationship with also having SCSI because I was able to install on a laptop (IDE) with / being formatted to EXT3 and it went just fine.
Yes, I noticed that during my install, initrd does not auto-select the needed modules, ala the SuSE version 7 series . What a palaver !! Just doing a manual install, allowed me to select the needed modules and then carry on. Occassional, I get prompted that no partitions can be mounted. One other thing, so far for me, is that I can't seem to add or remove packages as before, with the help of the update modules of YaST2. Tried every trip bar, dd'ing the various CDs or DVD onto DISK. Moght have to be the last option. I think, we have a problem with YaST2. Otherwise, the system remains smooth and satisfactory , so far. -- Kemdi IN_SuSE_d Since 5.2 123792 of counter.li.org ICQ:112290572
Bruce Marshall wrote:
something to do with a relationship with also having SCSI because I was able to install on a laptop (IDE) with / being formatted to EXT3 and it went just What kind of SCSI card do you have? What are the SCSI IDs of the drives and which ID is set for the boot?
Damon Register
On Wednesday 01 May 2002 6:53 am, Damon Register wrote:
Bruce Marshall wrote:
something to do with a relationship with also having SCSI because I was able to install on a laptop (IDE) with / being formatted to EXT3 and it went just
What kind of SCSI card do you have? What are the SCSI IDs of the drives and which ID is set for the boot?
Damon Register
Problem has been solved... but is still very strange. I have been running SuSE 7.3 since it came out. Had a /home paritition that was ext3. Every ran fine with 7.3. But there was something wrong with that ext3 /home partition that caused the fsck.ext3 in 8.0 to segfault. Went around in circles before I found the problem because at boot time, the only error message was 'fsck failed' without any information as to which partition had the failure. Even doing an fsck of the /home in 7.3 didn't solve the problem. I had to rsync the /home to my backup of /home2, do a mke2fs on /home and then rsync back. Once I had a 'clean' /home everything worked fine after that. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/01/02 10:15 + +----------------------------------------------------------------------------+ ".... File not found. Should I fake it? (Y/N)"
OK, here goes: Old Pentium 166 machine, not able to boot from CD. To make this worse, the machine is 100% SCSI. I found out that you could make boot disks from the CD, including module disks. I can get thru module disk 1, but module disk 2 just hangs the machine. I don't want to call SuSE because I want to also put the software on a different machine, one that I will use much more frequently, as soon as I put it on a LAN, ehich I haven't wired up yet. I will probably need more help with that, but I don't know. Does anyone have any suggestions? At 15:10 04/30/2002 +0000, Uzo Kemdi Anyamele wrote:
On Tue, 2002-04-30 at 09:51, Bruce Marshall wrote:
On Tuesday 30 April 2002 6:22 am, Uzo Kemdi Anyamele wrote:
On Mon, 2002-04-29 at 22:47, W.D. McKinney wrote:
Man is this one nice version for SuSE! No problems at all to report. Thanks so much for a job well done .
/Dee
Running Linux since Red Hat 2.0 and SuSE since 5.0.
Hey Dee and others,
Cool Runnings, eh ? I second that.
Just as curious, if you have multi partitions already across different drives.
You see, I have 4 10k SCSI drives with ,I think, 7/8 partitions. All, bar /boot and /extra running REISERFS. And more importantly 2 swaps partitions also.
So, during the upgrade, the system would baulk repeatedly, until I disabled one of the swap partitions.
Can you comment on any ideosyncracies here, no matter how hidden ?
Cheers
I'm having much the same problems with a new install. I have an all-SCSI unit with two drives. The install runs fine but on re-boot I get an 'fsck failed' message, and told to remount the root in RW mode and do the fsck manually. Ok, but doing that doesn't solve the problem. Another reboot and its right back to the same problem.
I was trying to make the root EXT3 and finally gave up on that since I was getting the fsck problem.
I'm about ready to send 8.0 back.
Please, no.... not yet !!
The senerio you described, I encountered also. During install, did you at least try and read your active /etc/fstab file ? i.e if you, like me use the expert partitioning options ?
I think that the default, during update or clean install is for the installer to want to format any disk in its way, but I've always refused it that pleasure , as I have several partitions going back in time that I've always kept and their data and files too.
Just make the /boot default to ext2 and format that. Then try to match the others to what your original layout used to be. And make sure , you've asked for no formating of your precious partitions.
Better still, just post your /etc/fstab here, so we can take a look.
Here's mine,
/dev/sdb3 / reiserfs defaults 1 2 /dev/sda1 /boot ext2 defaults 1 2 /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 devpts /dev/pts devpts defaults 0 0 /dev/dvd /media/dvd auto ro,noauto,user,exec 0 0 /dev/sda2 /extra ext2 defaults 1 2 /dev/sda3 /home reiserfs defaults 1 2 /dev/sdc2 /local reiserfs defaults 1 2 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/pda /media/sparQ auto rw,auto,user,exec 0 0 /dev/sdd1 /multimedia reiserfs defaults 1 2 /dev/sda4 /opt reiserfs defaults 1 2 proc /proc proc defaults 0 0 usbdevfs /proc/bus/usb usbdevfs noauto 0 0
/dev/sdb2 /usr reiserfs defaults 1 2 /dev/sdb4 /var reiserfs defaults 1 2 /dev/hdd4 /media/zip auto noauto,user 0 0 /dev/sdb1 swap swap pri=42 0 0 /dev/sdc1 swap swap pri=42 0 0
CHEERS
-- Kemdi IN_SuSE_d Since 5.2 123792 of counter.li.org ICQ:112290572
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
On Wednesday 01 May 2002 03:38, Doug McGarrett wrote:
I can get thru module disk 1, but module disk 2 just hangs the machine.
Are you saying it hangs when you load the disk or when you create it? If the latter, you may want to run a memcheck. I had that problem once, and it turned out to be because of faulty memory.
I don't want to call SuSE because I want to also put the software on a different machine, one that I will use much more frequently, as soon as I put it on a LAN, ehich I haven't wired up yet. I will probably need more help with that, but I don't know.
Installation support is a certain number of days, not a certain number of calls. regards Anders
On Wed, 2002-05-01 at 01:38, Doug McGarrett wrote:
OK, here goes: Old Pentium 166 machine, not able to boot from CD. To make this worse, the machine is 100% SCSI. I found out that you could make boot disks from the CD, including module disks. I can get thru module disk 1, but module disk 2 just hangs the machine. I don't want to call SuSE because I want to also put the software on a different machine, one that I will use much more frequently, as soon as I put it on a LAN, ehich I haven't wired up yet. I will probably need more help with that, but I don't know. Does anyone have any suggestions?
Hmmm.... And you can comfirm that the scsi-card is CD bootable ? And that you have choosen the right CD module, if any, from the Modules 2 disk ? If, however you still cant progress along these lines, and still have a running system somewhere in your vicinity, then I suggest using the /etc/exports and NFS utilities to make the CDs or DVD mountable across the LAN. You could start, by exporting the SuSE 7.3 cds or dvd, then upgrading to 8.0 the same way. Cheers. -- Kemdi IN_SuSE_d Since 5.2 123792 of counter.li.org ICQ:112290572
I have a 29160 with SCSI-3 disks and I must have made it fine with out your issues. Have you tried asking any of SuSE guys that lurk on the list ? -----Original Message----- From: Bruce Marshall [mailto:bmarsh@bmarsh.com] Sent: Tuesday, April 30, 2002 1:52 AM To: SLE Subject: Re: [SLE] 8.0 - Am I dreaming ...pinch me please ! On Tuesday 30 April 2002 6:22 am, Uzo Kemdi Anyamele wrote:
On Mon, 2002-04-29 at 22:47, W.D. McKinney wrote:
Man is this one nice version for SuSE! No problems at all to report. Thanks so much for a job well done .
/Dee
Running Linux since Red Hat 2.0 and SuSE since 5.0.
Hey Dee and others,
Cool Runnings, eh ? I second that.
Just as curious, if you have multi partitions already across different drives.
You see, I have 4 10k SCSI drives with ,I think, 7/8 partitions. All, bar /boot and /extra running REISERFS. And more importantly 2 swaps partitions also.
So, during the upgrade, the system would baulk repeatedly, until I disabled one of the swap partitions.
Can you comment on any ideosyncracies here, no matter how hidden ?
Cheers
I'm having much the same problems with a new install. I have an all-SCSI unit with two drives. The install runs fine but on re-boot I get an 'fsck failed' message, and told to remount the root in RW mode and do the fsck manually. Ok, but doing that doesn't solve the problem. Another reboot and its right back to the same problem. I was trying to make the root EXT3 and finally gave up on that since I was getting the fsck problem. I'm about ready to send 8.0 back. -- +--------------------------------------------------------------------------- -+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 04/30/02 05:46 + +--------------------------------------------------------------------------- -+ "Heard on Noahs' ark: Sailing is fun, but scrubbing the decks is aardvark." -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
On Tuesday 30 April 2002 13:53 pm, W.D.McKinney wrote:
I have a 29160 with SCSI-3 disks and I must have made it fine with out your issues. Have you tried asking any of SuSE guys that lurk on the list ?
Thanks for the info... I also use a 29160. Do you have any disks formatted as EXT3? I think that's the real problem but the problem didn't occur when I installed 8.0 on my IDE laptop with EXT3.
-----Original Message----- From: Bruce Marshall [mailto:bmarsh@bmarsh.com] Sent: Tuesday, April 30, 2002 1:52 AM To: SLE Subject: Re: [SLE] 8.0 - Am I dreaming ...pinch me please !
On Tuesday 30 April 2002 6:22 am, Uzo Kemdi Anyamele wrote:
On Mon, 2002-04-29 at 22:47, W.D. McKinney wrote:
Man is this one nice version for SuSE! No problems at all to report. Thanks so much for a job well done .
/Dee
Running Linux since Red Hat 2.0 and SuSE since 5.0.
Hey Dee and others,
Cool Runnings, eh ? I second that.
Just as curious, if you have multi partitions already across different drives.
You see, I have 4 10k SCSI drives with ,I think, 7/8 partitions. All, bar /boot and /extra running REISERFS. And more importantly 2 swaps partitions also.
So, during the upgrade, the system would baulk repeatedly, until I disabled one of the swap partitions.
Can you comment on any ideosyncracies here, no matter how hidden ?
Cheers
I'm having much the same problems with a new install. I have an all-SCSI unit with two drives. The install runs fine but on re-boot I get an 'fsck failed' message, and told to remount the root in RW mode and do the fsck manually. Ok, but doing that doesn't solve the problem. Another reboot and its right back to the same problem.
I was trying to make the root EXT3 and finally gave up on that since I was getting the fsck problem.
I'm about ready to send 8.0 back.
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 04/30/02 15:14 + +----------------------------------------------------------------------------+ "One cat just leads to another." - Ernest Hemmingway
participants (7)
-
Anders Johansson -
Bruce Marshall -
Damon Register -
Doug McGarrett -
Uzo Kemdi Anyamele -
W.D. McKinney -
W.D.McKinney