OS: SuSE 9.1 I am currently installing from a combo DVD-DOM/CD-ROM drive (/dev/hdb) as that is the only one I can get to boot from CD. The secondary CD-ROM (/dev/hdd) is recognized by the BIOS but for whatever reason will not boot from either CD. (I switched the IDE cables when attempting to boot from the CD-ROM, making it primary slave for a while to no avail.) Problem: The DVD drive apparently needs cleaning and I do not have a drive cleaning kit here. It has popped up the dialog stating it cannot find some packages. Occasionally a retry works but I usually have to Ignore the package to continue. Question: Once the install completes, assuming it is even useable, is there some yay to make YaST install the missing stuff from the secondary CD-ROM? Alternatively, it there any way I can boot from diskette and thence from the secondary CD-ROM drive? (I tried booting from CD2 in the primary (DVD/CD) drive but it failed trying to read the floppy drive for some reason.) (I'll fetch the drive cleaner tomorrow but, hopefully, will already be done.) Thank you, Lucky Leavell
On Saturday 29 May 2004 11:50 am, Lucky Leavell wrote:
OS: SuSE 9.1
I am currently installing from a combo DVD-DOM/CD-ROM drive (/dev/hdb) as that is the only one I can get to boot from CD. The secondary CD-ROM (/dev/hdd) is recognized by the BIOS but for whatever reason will not boot from either CD. (I switched the IDE cables when attempting to boot from the CD-ROM, making it primary slave for a while to no avail.)
Problem: The DVD drive apparently needs cleaning and I do not have a drive cleaning kit here. It has popped up the dialog stating it cannot find some packages. Occasionally a retry works but I usually have to Ignore the package to continue.
Question: Once the install completes, assuming it is even useable, is there some yay to make YaST install the missing stuff from the secondary CD-ROM?
Alternatively, it there any way I can boot from diskette and thence from the secondary CD-ROM drive? (I tried booting from CD2 in the primary (DVD/CD) drive but it failed trying to read the floppy drive for some reason.)
(I'll fetch the drive cleaner tomorrow but, hopefully, will already be done.)
Thank you, Lucky Leavell
Perform the install as normal, ignoring (for now) any missing packages. After the install in complete, start the install again, but chose "repair" as the install mode. Repair will test everything, including missing packages, and fix as required. I have had to use it many times before. Part of the problem with the media not found/package not found on medium errors is due to faulty hardware and/or faulty burned cds/dvds. You can boot from floppies, but it takes 2-6 floppies to do so, and I'm not sure it's worth the hassle. I did it once, and will bend over backwards to not have to do it again. :-) Regards, Mark
On Sat, 29 May 2004, Mark A. Taff wrote:
On Saturday 29 May 2004 11:50 am, Lucky Leavell wrote:
OS: SuSE 9.1
Question: Once the install completes, assuming it is even useable, is there some yay to make YaST install the missing stuff from the secondary CD-ROM?
Alternatively, it there any way I can boot from diskette and thence from the secondary CD-ROM drive? (I tried booting from CD2 in the primary (DVD/CD) drive but it failed trying to read the floppy drive for some reason.)
Perform the install as normal, ignoring (for now) any missing packages. After the install in complete, start the install again, but chose "repair" as the install mode. Repair will test everything, including missing packages, and fix as required. I have had to use it many times before.
That did appear to work and even accessed the CDs on the secondary drive but the root filesystem is still mounted read only which makes for a very limited system.
Part of the problem with the media not found/package not found on medium errors is due to faulty hardware and/or faulty burned cds/dvds.
I think the media is OK as I have used it before OK. I thinks it may be the drives, hopefully just needing cleaning.
You can boot from floppies, but it takes 2-6 floppies to do so, and I'm not sure it's worth the hassle. I did it once, and will bend over backwards to not have to do it again. :-)
Done that too. 9.0 typically requires 2-3 depending on how many drivers are needed.
Regards,
Thank you, Lucky
On Saturday 29 May 2004 04:38 pm, Lucky Leavell wrote:
On Sat, 29 May 2004, Mark A. Taff wrote:
On Saturday 29 May 2004 11:50 am, Lucky Leavell wrote:
OS: SuSE 9.1
Question: Once the install completes, assuming it is even useable, is there some yay to make YaST install the missing stuff from the secondary CD-ROM?
Alternatively, it there any way I can boot from diskette and thence from the secondary CD-ROM drive? (I tried booting from CD2 in the primary (DVD/CD) drive but it failed trying to read the floppy drive for some reason.)
Perform the install as normal, ignoring (for now) any missing packages. After the install in complete, start the install again, but chose "repair" as the install mode. Repair will test everything, including missing packages, and fix as required. I have had to use it many times before.
That did appear to work and even accessed the CDs on the secondary drive but the root filesystem is still mounted read only which makes for a very limited system.
Part of the problem with the media not found/package not found on medium errors is due to faulty hardware and/or faulty burned cds/dvds.
I think the media is OK as I have used it before OK. I thinks it may be the drives, hopefully just needing cleaning.
You can boot from floppies, but it takes 2-6 floppies to do so, and I'm not sure it's worth the hassle. I did it once, and will bend over backwards to not have to do it again. :-)
Done that too. 9.0 typically requires 2-3 depending on how many drivers are needed.
Regards,
Thank you, Lucky
Why exactly is / mounted read-only? I have had that happen when a partition (with ReiserFS on it) is corrupted. Try this: While the box is booting, press the scroll lock (ScrLk) key periodically -- this will pause the boot long enough to read the screen -- and pay attention to the lines related to the filesystem checks and mounting. If it reports errors (i.e. filesystem is NOT clean), then run fsck after the boot to the limited system is done. You will need to run fsck for all the partitions that reported errors, probably with some flags you wouldn't normally use, such as --rebuild tree. Do --help first, and read the warnings, docs first. --rebuild-tree is not to be taken lightly, but it will fix a corrupt filesystem, and I've never lost any data when I've had to use it, with the exception of webpage history in Konqi. I think that may be a bug in Konqi? My bet is that after you do this, you will be able to boot into a functional and stable system. Regards, Mark
On Sat, 29 May 2004, Mark A. Taff wrote:
On Saturday 29 May 2004 04:38 pm, Lucky Leavell wrote:
On Sat, 29 May 2004, Mark A. Taff wrote:
On Saturday 29 May 2004 11:50 am, Lucky Leavell wrote:
OS: SuSE 9.1
Perform the install as normal, ignoring (for now) any missing packages. After the install in complete, start the install again, but chose "repair" as the install mode. Repair will test everything, including missing packages, and fix as required. I have had to use it many times before.
That did appear to work and even accessed the CDs on the secondary drive but the root filesystem is still mounted read only which makes for a very limited system.
Part of the problem with the media not found/package not found on medium errors is due to faulty hardware and/or faulty burned cds/dvds.
I think the media is OK as I have used it before OK. I thinks it may be the drives, hopefully just needing cleaning.
You can boot from floppies, but it takes 2-6 floppies to do so, and I'm not sure it's worth the hassle. I did it once, and will bend over backwards to not have to do it again. :-)
Done that too. 9.0 typically requires 2-3 depending on how many drivers are needed.
Why exactly is / mounted read-only? I have had that happen when a partition (with ReiserFS on it) is corrupted. Try this:
I wish I knew...
While the box is booting, press the scroll lock (ScrLk) key periodically -- this will pause the boot long enough to read the screen -- and pay attention to the lines related to the filesystem checks and mounting.
Didn't try that before reinstalling - see below
If it reports errors (i.e. filesystem is NOT clean), then run fsck after the boot to the limited system is done. You will need to run fsck for all the partitions that reported errors, probably with some flags you wouldn't normally use, such as --rebuild tree. Do --help first, and read the warnings, docs first.
Booted from CD and ran reiserfsck --check --fix-fixable but it reported no corruption at all.
--rebuild-tree is not to be taken lightly, but it will fix a corrupt filesystem, and I've never lost any data when I've had to use it, with the exception of webpage history in Konqi. I think that may be a bug in Konqi?
My bet is that after you do this, you will be able to boot into a functional and stable system.
So did starting the install over and changing the default reiserfs to ext3. I still had some problems reading the CDs and had to repair this system as well but it now functions as expected. (I have experienced problems with reiserfs on IDE drives with 9.0 as well and am about to quit using it altogether. My initial 9.0 install uses reiser but on SCSI drive with no problems so far. We had to blow away a 9.0 installed using reiser on an IDE drive. I have found nothing in sdb to back this up. It is a gut feeling borne from 15+ years experience mainly with Unix.) Thank you, Lucky Leavell
On Monday 31 May 2004 02:36, Lucky Leavell wrote:
On Sat, 29 May 2004, Mark A. Taff wrote:
On Saturday 29 May 2004 04:38 pm, Lucky Leavell wrote:
On Sat, 29 May 2004, Mark A. Taff wrote:
On Saturday 29 May 2004 11:50 am, Lucky Leavell wrote:
OS: SuSE 9.1
Perform the install as normal, ignoring (for now) any missing packages. After the install in complete, start the install again, but chose "repair" as the install mode. Repair will test everything, including missing packages, and fix as required. I have had to use it many times before.
That did appear to work and even accessed the CDs on the secondary drive but the root filesystem is still mounted read only which makes for a very limited system.
Part of the problem with the media not found/package not found on medium errors is due to faulty hardware and/or faulty burned cds/dvds.
I think the media is OK as I have used it before OK. I thinks it may be the drives, hopefully just needing cleaning.
You can boot from floppies, but it takes 2-6 floppies to do so, and I'm not sure it's worth the hassle. I did it once, and will bend over backwards to not have to do it again. :-)
Done that too. 9.0 typically requires 2-3 depending on how many drivers are needed.
Why exactly is / mounted read-only? I have had that happen when a partition (with ReiserFS on it) is corrupted. Try this:
I wish I knew...
While the box is booting, press the scroll lock (ScrLk) key periodically -- this will pause the boot long enough to read the screen -- and pay attention to the lines related to the filesystem checks and mounting.
Didn't try that before reinstalling - see below
If it reports errors (i.e. filesystem is NOT clean), then run fsck after the boot to the limited system is done. You will need to run fsck for all the partitions that reported errors, probably with some flags you wouldn't normally use, such as --rebuild tree. Do --help first, and read the warnings, docs first.
Booted from CD and ran reiserfsck --check --fix-fixable but it reported no corruption at all.
--rebuild-tree is not to be taken lightly, but it will fix a corrupt filesystem, and I've never lost any data when I've had to use it, with the exception of webpage history in Konqi. I think that may be a bug in Konqi?
My bet is that after you do this, you will be able to boot into a functional and stable system.
So did starting the install over and changing the default reiserfs to ext3.
I still had some problems reading the CDs and had to repair this system as well but it now functions as expected.
(I have experienced problems with reiserfs on IDE drives with 9.0 as well and am about to quit using it altogether. My initial 9.0 install uses reiser but on SCSI drive with no problems so far. We had to blow away a 9.0 installed using reiser on an IDE drive. I have found nothing in sdb to back this up. It is a gut feeling borne from 15+ years experience mainly with Unix.)
Thank you, Lucky Leavell Hi All .
It seems you are suffering from suspect drive syndrome more that an error with Reiserfs I have been running Reiser since the very early days and had just two 2 problems one was due to an early version of Reiser (well what do you expect it was about alpha quality) and the second was not long ago but that was down to collapsed bearings in the Hdd motor Check them drives modern IDE stuff is basically CRAP ! .. -- G6NJR Pete otherwise known as "Quinton 11" A Linux Only area Happy bug hunting M$ clan Pete,,,,, :-)
participants (3)
-
Lucky Leavell -
Mark A. Taff -
peter Nikolic