| 1 |
On Sun, Apr 10, 2011 at 4:33 PM, Alan McKinnon <alan.mckinnon@×××××.com>wrote: |
| 2 |
|
| 3 |
> Apparently, though unproven, at 23:11 on Sunday 10 April 2011, Alan |
| 4 |
> Mackenzie |
| 5 |
> did opine thusly: |
| 6 |
> |
| 7 |
> > Hi, Gentoo. |
| 8 |
> > |
| 9 |
> > My new(ish) amd64 system has two 1TB HDDs in a (software) RAID1, and |
| 10 |
> > practically the entire system is under an LVM2. |
| 11 |
> > |
| 12 |
> > I rather unwisely made this addition to the startup stuff: |
| 13 |
> > |
| 14 |
> > ls -s /usr/bin/svscanboot /etc/init.d/ |
| 15 |
> > rc-update add svscanboot default |
| 16 |
> > |
| 17 |
> > , and now the box hangs during boot up. |
| 18 |
> > |
| 19 |
> > On the same box, I also have a "trial" installation which boots and I |
| 20 |
> > still have the installation CD from about a year ago. |
| 21 |
> > |
| 22 |
> > Would somebody please help me get into my system sufficiently to correct |
| 23 |
> > my mistake on the boot scripts. Pointing me in the direction of a fine |
| 24 |
> > manual section would be regarded as help. |
| 25 |
> |
| 26 |
> Boot the trial installation which does boot. |
| 27 |
> vgchange -ay |
| 28 |
> find and mount your lvm volumes somewhere |
| 29 |
> now you can access that dodgy symlink to delete it |
| 30 |
> |
| 31 |
> Maybe there's other steps (like loading kernel modules), but I'm assuming |
| 32 |
> you |
| 33 |
> know your way around to find and detect those. |
| 34 |
> |
| 35 |
> -- |
| 36 |
> alan dot mckinnon at gmail dot com |
| 37 |
> |
| 38 |
> |
| 39 |
He should be able to just do an interactive startup. Press "i" when |
| 40 |
prompted, and you should be able to bypass the bad startup item; |
| 41 |
alternatively, if you have access to grub boot, you can also try booting |
| 42 |
into single user mode. |
Archives