[ale] Major Hdwe upgrade foils LVM

hscast at charter.net hscast at charter.net
Sun Aug 17 15:24:50 EDT 2008


---- hscast at charter.net wrote: 
> 
> ---- Jim Kinney <jim.kinney at gmail.com> wrote: 
> > Sounds like a "fun" challenge :-)
> > 
> > First off, grub is grousing because it can't find the original / partition.
> > The LVM isn't loading because of the miss-ordering of the drives. It
> > _should_ be using labels on the drives themselves but it seems like
> > something is wrong. Which Fedora version is loaded on the drives?
> Fedora 9 (32 bit)
> > 
> > BIOS ordering is ignored on the /boot is found. What does matter is pci
> > device numbering.  So try plugging in the 500G into the SATA port the first
> > 37G is plugged into the 37G into the 500G port.  I suspect the SATA ports
> > are using the primary/secondary scheme and that is fouling up the PCI device
> > numbering.
> > 
> I was thinking of doing that but wound up just disconnecting the 2 37GBs and of course the 500GB came up as sdd. I'll go back and give it a try again to see and get back to you.
> > 
> > 
> > On Sun, Aug 17, 2008 at 12:28 PM, <hscast at charter.net> wrote:
> > 
> > > Took the plunge after my AMD Socket A processor burned up and also took
> > > down the PSU. Bought new 520 W Corsair PSU along with a Gigabyte AM2+ MoBo
> > > but only with an AMD 64 X2 processor and 4GB RAM (800MHz). I still have the
> > > original HDDs (80GB, 250GB, 160GB, 500GB, 37GB, 37GB). The first 2 are PATA
> > > and the other 4 are SATA which I had originally had connected to a PCI-SATA
> > > 4 port card. The original; drive assignments or designators were as in order
> > > by size; sda, sdb, sdc, sdd, sde, sdf. The new Mobo has one PATA port
> > > (master/Slave), and 6 SATA ports (0-5) of which the last 2 are inactive in
> > > non-raid configs. The BIOS has them set as IDE the only non-raid config. The
> > > BIOS also "sees" the drives in the correct order, however Fedora rescue boot
> > > swaps the 500GB with the 1st 37GB making the order as 80GB = sda, 250GB =
> > > sdb, 160GB = sdc, 1st 37GB = sdd, 500GB = sde, & 2nd 37GB sdf. I went to
> > > Fedora rescue as the system originally wouldn't boot, GRUB comes up but it
> > > seems to have a !
> > >  problem with the LVM. Everything except of course is in a LVM partition
> > > except of course /boot. Under system rescue, the volumes get mounted, but
> > > with errors, but I'm not sure what the errors are, or at least I don't
> > > understand it any way.
> > >
> > > I hope that this is somewhat clear and someone may be able to point me in
> > > the right direction.
> > >
> > > TIA
> > > Scott
> > >
> > > _______________________________________________
> > > Ale mailing list
> > > Ale at ale.org
> > > http://mail.ale.org/mailman/listinfo/ale
> > >
> > 
> > 
> > 
> > -- 
> > -- 
> > James P. Kinney III
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
Ok, swapping physical port connections with the 500GB and the 1st 37GB fixed that problem. I noticed that when I boot from DVD system-rescue, if I check the mounted FSs I noticed in the options rw, relatime, errors=continue, data=ordered. It's the 3rd and possibly the 4th that I'm questioning. Also, everything seems to be there ok. 

Now when I boot from the hard drive it goes through GRUB ok and starts initializing the kernel, but then it'll suddenly spit out the following:

"Unable to access resume device (/dev/sda2)"
"mount: could not find filesystem '/dev/root'"
"setuproot: moving /dev failed: No such file or directory"
"setuproot: error mounting /proc: No such file or directory"
"setuproot: error mounting /sys: No such file or directory"
"Mount failed for selinuxfs on /selinux: No such file or directory"
"Switch root: mount failed: No such file or directory"

I do have SELinux enabled, do you think that it may have something to do with that? I don't remember how to boot w/o selinux enabled to see. Also, is it possible that selinux just needs to rescan the drives? I seem to remember coming up with a similar problem back in Fedora 7 or 8, and I just booted disabling selinux and then doing a scan then rbooting and everything was fine after that. Any idea what the commands are/were?


More information about the Ale mailing list