1 |
On Sunday 06 Nov 2011 12:43:06 Dale wrote: |
2 |
> Hi, |
3 |
> |
4 |
> This is weird and I'm not sure what info to give yet. This is the |
5 |
> events tho. First, a raccoon got on the power substation transformer |
6 |
> that supplies power for the whole county, excluding my local city which |
7 |
> has its own transformer. So, we lost power. It was sudden just like a |
8 |
> power switch. Yea, this happens regular here and it ticks me to no |
9 |
> end. It also ticks off the power company because it is always about 2 |
10 |
> or 3 in the morning when the little farts do this. Second, my system |
11 |
> switched to the UPS battery which was beeping and woke me up. I did a |
12 |
> normal shutdown and cut everything off. No problems so far. Patience. |
13 |
> o_O |
14 |
> |
15 |
> When the power came back on, I turned on the UPS which turns on the |
16 |
> modem, router, monitor and everything computer related back on. I |
17 |
> waited a few seconds and turned on my rig. BIOS comes up which I wasn't |
18 |
> really looking at, then Grub prompt. I hit enter and got the "file not |
19 |
> found" thing. Well, this is weird. So, I hit a key to try a older |
20 |
> kernel, I keep several older versions around just in case. Same error. |
21 |
> Hmmm. I did a reset and noticed the BIOS is NOT seeing a single drive |
22 |
> connected, NOT ONE. What !! I enter the BIOS and go to the drive |
23 |
> section and try to get it to detect them, nothing. Surely three hard |
24 |
> drives and a DVD burner can't all go out at exactly the same time. |
25 |
> Well, after scratching my head a bit, I reset the BIOS to defaults, |
26 |
> which should be about what it is anyway since I don't overclock. Still |
27 |
> same grub error. |
28 |
> |
29 |
> After a bit, I loaded sysrescue from the USB stick. I thought maybe |
30 |
> grub updated and it was having issues so was planning to chroot in and |
31 |
> fix it. Here comes a funny part. When I did a cat /proc/partitions |
32 |
> from sysrescue, all my drives and partitions were there even tho the |
33 |
> BIOS didn't see them. However, cfdisk gave me a error when I tried to |
34 |
> look at the drives. Same error on ALL drives. Now I'm freaking out a |
35 |
> bit. :/ Oh, for you folks who use LABELS like me, write down which |
36 |
> partition is what. If cfdisk doesn't work, you can't tell what |
37 |
> partition is what. ;-) Anyway, while in there I finally started |
38 |
> mounting partitions and seeing what files were there until I figured out |
39 |
> what was what, at least for root and boot. When I did my ls on /boot, |
40 |
> the kernels were symlinks to the kernel sources on /usr which is not |
41 |
> mounted yet. OK. Whew!! That's why grub can't find the kernel since |
42 |
> it is a symlink to a partition that is not mounted yet. I did find two |
43 |
> that were actual files and not links. Thanks goodness for being a |
44 |
> packrat. lol |
45 |
> |
46 |
> I reboot and the BIOS shows my drives not as SATA but as IDE. However, |
47 |
> I edit the grub kernel line to point to a good kernel and it boots. I'm |
48 |
> actually typing in it now. |
49 |
> |
50 |
> My questions you ask? Why is the BIOS not seeing the drives correctly? |
51 |
> The main BIOS screen sees nothing and it used to print them on the |
52 |
> screen, including the DVD burner. They do show up on the second screen |
53 |
> where AHCI detects drives. Next question, why could cfdisk not see the |
54 |
> drives? Note, I tried all three drives on my system, same error. I may |
55 |
> reboot into the sysrescue thing and try it again and write down the error. |
56 |
> |
57 |
> I'm going to test on this some more. I want to figure this out in case |
58 |
> there is something wrong or I run into this again and can't get cfdisk |
59 |
> to work. I'm also going to print my partition layout too. lol |
60 |
> |
61 |
> Oh, from the Gentoo install, cfdisk sees the drives and works |
62 |
> perfectly. The only thing I notice is a "*" way out to the right on the |
63 |
> last partition. Like this: |
64 |
> |
65 |
> sda9 Logical ext4 [chroot] 61832.05 * |
66 |
> |
67 |
> I'm not sure what the "*" means tho. Any ideas? That is where I do my |
68 |
> builds for a 32 bit install hence the label. It is not even mounted all |
69 |
> the time. |
70 |
> |
71 |
> Dale |
72 |
> |
73 |
> :-) :-) |
74 |
> |
75 |
> P. S. I'll post back as I test things. This is weird. Like me. ROFL |
76 |
|
77 |
Can you set in your BIOS which controller IDE or SATA manages the drives? |
78 |
|
79 |
I'm not sure why you have a symlink to your /usr/src/linux files from /boot (I |
80 |
don't understand it). In /boot you should have the image files themselves of |
81 |
your desired kernels (plus corresponding System and .config files). |
82 |
-- |
83 |
Regards, |
84 |
Mick |