Re: After upgrading to CORE3, my raid drives no longer seem valid
From: Acer0001 (nospam_at_nospam.nospam)
Date: 12/05/04
- Next message: Stephane: "Apache into User directory"
- Previous message: staple: "multi booting with windows"
- In reply to: Tim Mavers: "After upgrading to CORE3, my raid drives no longer seem valid"
- Next in thread: Tim Mavers: "Re: After upgrading to CORE3, my raid drives no longer seem valid"
- Reply: Tim Mavers: "Re: After upgrading to CORE3, my raid drives no longer seem valid"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 04 Dec 2004 20:49:03 -0600
What does partprobe -s /dev/hde show? Anything different?
Acer0001
On Sat, 04 Dec 2004 08:07:53 -0600, Tim Mavers wrote:
> I just upgraded to Fedora Core 3. Actually I had to do a fresh install as
> Fedora never seems to want to upgrade correctly. I even have problems
> installing Fedora (any CORE) with my Promise ATA raid control installed.
>
> That said, I simply removed the raid controller from the PCI slot and
> unplugged all the power and IDE cables so during install Fedora wouldn't
> die. Everything worked smoothly (as it did when I did the same exact thing
> from Core 1 to Core 2).
>
> THis time however after reconnecting my raid-drives, both drives seem to be
> empty. In that I mean whenI I run fdisk on/dev/hde and /dev/hdg (my two
> drives in question) they show up without and partitions. I haven't changed
> any hardware and simpy just unplugged the drives during installation. It is
> worth noting that when I installed Core 3 (the same as Core 2), to avoid RPM
> hell, I always choose 'everything', so I don't think I am missing anything?
> Any ideas? RIght now I have missing about 300GB of data! Help!
>
> Here's the output of fdisk looking at /dev/hde (the first of two drives in
> my array):
>
> [root@tsunami ~]# fdisk /dev/hde
> Device contains neither a valid DOS partition table, nor Sun, SGI or OSF
> disklabel
> Building a new DOS disklabel. Changes will remain in memory only,
> until you decide to write them. After that, of course, the previous
> content won't be recoverable.
>
> The number of cylinders for this disk is set to 36473.
> There is nothing wrong with that, but this is larger than 1024,
> and could in certain setups cause problems with:
> 1) software that runs at boot time (e.g., old versions of LILO)
> 2) booting and partitioning software from other OSs
> (e.g., DOS FDISK, OS/2 FDISK)
> Warning: invalid flag 0x0000 of partition table 4 will be corrected by
> w(rite)
>
> Command (m for help): p
>
> Disk /dev/hde: 300.0 GB, 300001443840 bytes
> 255 heads, 63 sectors/track, 36473 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
>
> Command (m for help): q
- Next message: Stephane: "Apache into User directory"
- Previous message: staple: "multi booting with windows"
- In reply to: Tim Mavers: "After upgrading to CORE3, my raid drives no longer seem valid"
- Next in thread: Tim Mavers: "Re: After upgrading to CORE3, my raid drives no longer seem valid"
- Reply: Tim Mavers: "Re: After upgrading to CORE3, my raid drives no longer seem valid"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
