Hi,
This is a really strange problem. I think I know what is going on, but unsure how to remedy the situation.
When I did the install, I partitioned the main drive so that /usr and /web were on different partitions. FC3t2 created the other partitions and did the rest.
Gets to the end, reboot, I create user paul and login happily. I also create users bev and richard, so everything was the same as the old system.
I've next added more drives, as they're 120Gb jobs, these too have been partitioned. I have a new home directory on /dev/hdb1 and alter fstab to say that /home is now /dev/hdb1 and insert the other partitions on the other drives also info fstab (in total, there is hdb1 & 2, hdg1 & 2 and hdh1 on the drives - hdh1 is a massive backup drive).
When I reboot, I have all sorts of problems getting into my area (lots of problems with applets on the panel bar and my Liver bird backdrop). I can also not logout. When I do a ctrl backspace, I am returned to login screen and then can log in normally - everything reappears and works normally. Okay, the sound needs to be fiddled with, but other than that, it's all fine.
Is the problem that /home/paul still exists on /dev/hda2 and the system is getting confused or something else?
TTFN
Paul
Not kernel related this time!
Device inodes are not being created properly by anaconda, instead of:
/dev/i2o/hda 80, 0 /dev/i2o/hda1 80, 1 ... /dev/i2o/hda9 80, 9
I'm seeing:
/dev/i2o/hda 80, 0 /dev/i2o/hdap1 80, 0 ... /dev/i2o/hdap9 80, 0
causing the install to fail with no hard drives found. Creating the devices manually allows the install to proceed as normal:
mknod /dev/i2o/hda1 b 80 1 mknod /dev/i2o/hda2 b 80 2 ... mknod /dev/i2o/hda9 b 80 9
Technical discussion below - should I take this across to anaconda-devel and/or bugzilla, or is a relevant party listening in?
isys/devnodes.c, devMakeInode() cannot determine minor device number since devName[7] is always 'p' - Assuming fsset.py formatDevice() is correct, I believe (UNTESTED!) the bug is in loader2/getparts.c, isPartitionName():
(1) Either do this:
--- loader2/getparts.c 2004-09-23 01:48:30.000000000 +0100 +++ loader2/getparts.c 2004-09-23 01:48:53.000000000 +0100 @@ -32,7 +32,7 @@ return 0;
/* if it has a '/' in it then treat it specially */ - if (strchr(pname, '/') && !strstr(pname, "iseries")) { + if (strchr(pname, '/') && !strstr(pname, "iseries") && !strstr(pname, "i2o")) { /* assume its either a /dev/ida/ or /dev/cciss device */ /* these have form of c?d?p? if its a partition */ return strchr(pname, 'p') != NULL;
(2) Or instead of excluding devices that don't have the form c?d?p?, why not just include those that do?:
--- loader2/getparts.c 2004-09-23 01:48:30.000000000 +0100 +++ loader2/getparts.c 2004-09-23 01:53:40.000000000 +0100 @@ -32,7 +32,7 @@ return 0;
/* if it has a '/' in it then treat it specially */ - if (strchr(pname, '/') && !strstr(pname, "iseries")) { + if (strstr(pname, "ida/") || strstr(pname, "cciss/")) { /* assume its either a /dev/ida/ or /dev/cciss device */ /* these have form of c?d?p? if its a partition */ return strchr(pname, 'p') != NULL;
(1) is less likely to break existing behaviour, (2) seems more sensible (but still ugly in the long term) - take your pick. NB - I've not had a chance to rebuild anaconda to test this yet since I'm currently without a suitable build platform.
Hey, thanks for the bug report. One thing that needs to be emphasized is that unless this gets reported in bugzilla, it's very likely to be lost.
All bugs need to be reported in bugzilla so they can be tracked and
managed sanely, and so that you can always find out exactly what the status of a fix is. <<<
Cheers, -- Elliot We're so busy putting out fires that we don't take time to stop kids from playing with matches.
On Thu, 23 Sep 2004, Dave wrote:
Not kernel related this time!
Device inodes are not being created properly by anaconda, instead of:
/dev/i2o/hda 80, 0 /dev/i2o/hda1 80, 1 ... /dev/i2o/hda9 80, 9
I'm seeing:
/dev/i2o/hda 80, 0 /dev/i2o/hdap1 80, 0 ... /dev/i2o/hdap9 80, 0
causing the install to fail with no hard drives found. Creating the devices manually allows the install to proceed as normal:
mknod /dev/i2o/hda1 b 80 1 mknod /dev/i2o/hda2 b 80 2 ... mknod /dev/i2o/hda9 b 80 9
Technical discussion below - should I take this across to anaconda-devel and/or bugzilla, or is a relevant party listening in?
isys/devnodes.c, devMakeInode() cannot determine minor device number since devName[7] is always 'p' - Assuming fsset.py formatDevice() is correct, I believe (UNTESTED!) the bug is in loader2/getparts.c, isPartitionName():
(1) Either do this:
--- loader2/getparts.c 2004-09-23 01:48:30.000000000 +0100 +++ loader2/getparts.c 2004-09-23 01:48:53.000000000 +0100 @@ -32,7 +32,7 @@ return 0;
/* if it has a '/' in it then treat it specially */
- if (strchr(pname, '/') && !strstr(pname, "iseries")) {
- if (strchr(pname, '/') && !strstr(pname, "iseries") && !strstr(pname,
"i2o")) { /* assume its either a /dev/ida/ or /dev/cciss device */ /* these have form of c?d?p? if its a partition */ return strchr(pname, 'p') != NULL;
(2) Or instead of excluding devices that don't have the form c?d?p?, why not just include those that do?:
--- loader2/getparts.c 2004-09-23 01:48:30.000000000 +0100 +++ loader2/getparts.c 2004-09-23 01:53:40.000000000 +0100 @@ -32,7 +32,7 @@ return 0;
/* if it has a '/' in it then treat it specially */
- if (strchr(pname, '/') && !strstr(pname, "iseries")) {
- if (strstr(pname, "ida/") || strstr(pname, "cciss/")) { /* assume its either a /dev/ida/ or /dev/cciss device */ /* these have form of c?d?p? if its a partition */ return strchr(pname, 'p') != NULL;
(1) is less likely to break existing behaviour, (2) seems more sensible (but still ugly in the long term) - take your pick. NB - I've not had a chance to rebuild anaconda to test this yet since I'm currently without a suitable build platform.