<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Steven N. Hirsch wrote: <blockquote cite="midPine.LNX.4.61.0505110854580.5930@monarch.fast.net" type="cite"> <pre wrap="">On Wed, 11 May 2005, Balint Cristian wrote: </pre> <blockquote type="cite"> <pre wrap="">On Wednesday 11 May 2005 15:07, Steven N. Hirsch wrote: </pre> <blockquote type="cite"> <pre wrap="">On Wed, 11 May 2005, Balint Cristian wrote: </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">I'm running into problems trying to install Alpha Core 1.0. The box is a UP2000+ with an Adaptec 39160 controller. There are (2) drives attached, one on each channel. The dka device is partitioned and formatted for Tru64 Unix. Dkb has (3) other Linux distributions installed and has been partitioned with a BSD disklabel scheme. I'm trying to install onto an unused partition on dkb. The installer trips over dka, telling me that the partition table is unreadable and asking if I want to reinitialize it. I answer "no". It then tells me that dkb is unreadable as well! When I tell it not to initialize that disk, it terminates with an error (thinking that no disks are available). The question is: why can't the installer read the partition information on either drive? Granted, it won't know about AdvFS on dka, but it still should have read the disklabel. And, since the Linux distros on dkb are functional there's no reason it should have problems of any sort. </pre> </blockquote> <pre wrap="">Hmm interesting. I notice the issue, keep that in mind. </pre> <blockquote type="cite"> <pre wrap="">Any advice as to how I proceed with installation and avoid repartitioning the second disk? </pre> </blockquote> <pre wrap="">As quick hack, try unplug physicaly dka down from SCSI bus ! </pre> </blockquote> <pre wrap="">Just tried that. It still claims it cannot "read" the disk. Sergey recommended that I boot in rescue mode and try to mount it manually. This works fine, as I expected. </pre> </blockquote> <pre wrap="">What does it say exactly, can do Alt-F4 or some sort of Alt-F2,3,4 to see more debugs ? </pre> </blockquote> <pre wrap=""> I am now successfully installing on a fresh disk, which I permitted AC to partition and format for me :-). I notice one major difference between what Anaconda did on that disk and the way the troublesome disk is setup. Anaconda does not follow the BSD convention of making the "C" slice cover the entire drive! It has /boot as A, swap as B and the root partition as C. My drive has /boot starting at cylinder 2 (to leave room for aboot), then swap as B, then C as the entire drive (starting at cylinder 1, not 2), followed by all the root partitions (D, E, F) from the various distros. Not being familiar with Anaconda, I wonder if it is getting confused by the situation - particularly the 'C' slice? </pre> </blockquote> I think your assumptions are correct. The used anaconda is mainline one with very few alpha specific patches. To fix and debug anaconda scripts is very time consuming. I didn't find a way (although I didn't look hard) to do it without having a second machine. It might not know about rules for "C slice" and simply decides that no free space available. :) I don't remember was RH7.2 able to install on such patition configuration. <blockquote cite="midPine.LNX.4.61.0505110854580.5930@monarch.fast.net" type="cite"> <pre wrap=""> The only messages which were not routine are a series of complaints about Anaconda using an obsolete ioctl call for scsi generic driver. This occurs at the time it's probing for the partition information. Please note that an actual booting kernel recognizes the partition map - AlphaCore 1.0 included. If I boot in rescue mode, fdisk shows me exactly what I expect to see. This is almost certainly an Anaconda problem rather than a kernel problem. Steve _______________________________________________ axp-list mailing list <a class="moz-txt-link-abbreviated" href="mailto:axp-list@redhat.com">axp-list@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/axp-list">https://www.redhat.com/mailman/listinfo/axp-list</a> </pre> </blockquote> Regards, <pre class="moz-signature" cols="72">-- --- Sergey Tikhonov Solvo Ltd. <a class="moz-txt-link-abbreviated" href="mailto:tsv@solvo.ru">tsv@solvo.ru</a> </pre> </body> </html>