New motherboard can't see old drives
in [Linux Hardware]
|
From: Charlie Gibbs on 23 Jan 2008 21:16 The motherboard on my big Linux box blew up last Friday. I've gotten a replacement motherboard (with a bit more CPU power and memory, natch), and now I'm trying to get things back to normal. The original box booted from a 4GB IDE drive, then mounted two SATA drives; the first one (200GB) held /usr/local and /home (both ReiserFS), while the second drive (320GB) held an XFS partition which I mounted as /bigspace. I removed the two SATA drives before taking my box into the shop; I didn't want someone to accidentally format them while testing the new hardware. But even the IDE boot drive, which I left in the machine, is intact; it booted the original kernel just fine. However, the two SATA drives aren't quite there. The BIOS sees and correctly identifies them, but the kernel can't mount them; cfdisk can't find them either. I'll worry about trivia like Ethernet and X configuration later; for now, how do I get the kernel to see those two SATA drives (and the 500GB of stuff on them, of course)? -- /~\ cgibbs(a)kltpzyxm.invalid (Charlie Gibbs) \ / I'm really at ac.dekanfrus if you read it the right way. X Top-posted messages will probably be ignored. See RFC1855. / \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!
From: jellybean stonerfish on 24 Jan 2008 01:24 On Wed, 23 Jan 2008 18:16:35 -0800, Charlie Gibbs wrote: > The motherboard on my big Linux box blew up last Friday. I've > gotten a replacement motherboard (with a bit more CPU power and > memory, natch), and now I'm trying to get things back to normal. <<SNIP>>> > However, the two SATA drives aren't quite there. The BIOS sees > and correctly identifies them, but the kernel can't mount them; > cfdisk can't find them either. > Perhaps your kernel needs the modules for the chipset of your new motherboard. What are the specs on your new motherboard?
From: Charlie Gibbs on 24 Jan 2008 11:15 In article <NaWlj.1077$hI1.454(a)nlpi061.nbdc.sbc.com>, stonerfish(a)geocities.com (jellybean stonerfish) writes: > On Wed, 23 Jan 2008 18:16:35 -0800, Charlie Gibbs wrote: > >> The motherboard on my big Linux box blew up last Friday. I've >> gotten a replacement motherboard (with a bit more CPU power and >> memory, natch), and now I'm trying to get things back to normal. ><<SNIP>>> >> However, the two SATA drives aren't quite there. The BIOS sees >> and correctly identifies them, but the kernel can't mount them; >> cfdisk can't find them either. > > Perhaps your kernel needs the modules for the chipset of your new > motherboard. > What are the specs on your new motherboard? It's an ASRock ALiveNF6G-VSTA. As you might have guessed from those last 4 characters, they make a big deal about it being up to the stresses and strains of running Windows Vista. However, I'm trying my usual tack of ignoring the Microsoft hype and just bringing up Linux on it, a practice which has worked well on several other boxes in the past. Information in the manual is pretty sketchy; for example, the section on SATA drive installation says nothing more than to mount the drive(s) in the case and plug in the cables - which, on my old motherboard, was all I had to do. As for specifications, the only specific mention of SATA is that there are four connectors, and that it supports RAID and hot-plugging. Under "Chipset" the manual says "NVIDIA GeForce 6100 / nForce 430 or GeForce 6150SE / nForce 430". This sounds like a description of the onboard video, which isn't an issue because I'm using a separate video card (eGeForce 8400 GS). Presumably the shop that replaced the motherboard got all the jumper settings right; the video card seems to be working OK (although I haven't tried to get X running yet). There's a CD provided with the motherboard - strictly Windows, of course - and one of the directories on it is \drivers\SATA2\nvidia. It seems to contain drivers for 32- and 64-bit versions of Vista. Most Linux installations I've done in the past have run right out of the box with no special drivers. But who knows, this might be the exception that proves the rule. I did try going through make menuconfig, reviewing all the specs and building a new kernel, in the hopes I'd see something in the software configuration that I had missed - but the results were the same. I'm _really_ hoping that this motherboard doesn't require some exotic driver that doesn't yet exist in Linux form. Any pointers on Linux SATA would be appreciated, although I'm starting to come up with things like http://linuxmafia.org/faq/Hardware/sata.html Thanks for the note. -- /~\ cgibbs(a)kltpzyxm.invalid (Charlie Gibbs) \ / I'm really at ac.dekanfrus if you read it the right way. X Top-posted messages will probably be ignored. See RFC1855. / \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!
From: Darren Salt on 24 Jan 2008 11:24 I demand that Charlie Gibbs may or may not have written... > In article <NaWlj.1077$hI1.454(a)nlpi061.nbdc.sbc.com>, > stonerfish(a)geocities.com (jellybean stonerfish) writes: >> On Wed, 23 Jan 2008 18:16:35 -0800, Charlie Gibbs wrote: [snip] >>> However, the two SATA drives aren't quite there. The BIOS sees >>> and correctly identifies them, but the kernel can't mount them; >>> cfdisk can't find them either. >> Perhaps your kernel needs the modules for the chipset of your new >> motherboard. What are the specs on your new motherboard? [snip] > Under "Chipset" the manual says "NVIDIA GeForce 6100 / nForce 430 or > GeForce 6150SE / nForce 430". This sounds like a description of the onboard > video, "GeForce" is. "nForce" is the board's chipset. > which isn't an issue because I'm using a separate video card (eGeForce 8400 > GS). Presumably the shop that replaced the motherboard got all the jumper > settings right; the video card seems to be working OK (although I haven't > tried to get X running yet). nv? nouveau? [snip] > I did try going through make menuconfig, reviewing all the specs and > building a new kernel, in the hopes I'd see something in the software > configuration that I had missed - but the results were the same. You've probably missed either sd_mod or sata_nv; however, if you're using a kernel >= 2.6.20 (IIRC) with a config from an older kernel, updated using "make oldconfig" or similar, you'll have lost the SATA configuration options from the older kernel. Device Drivers → SCSI device support → SCSI disk support Device Drivers → Serial ATA [...] drivers → NVIDIA SATA support [snip] -- | Darren Salt | linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Lobby friends, family, business, government. WE'RE KILLING THE PLANET. We came. We assimilated. We left.
From: Anton Ertl on 24 Jan 2008 13:37
"Charlie Gibbs" <cgibbs(a)kltpzyxm.invalid> writes: >Under "Chipset" the manual says "NVIDIA GeForce 6100 / >nForce 430 or GeForce 6150SE / nForce 430". AFAIK Nvidia chipsets support ahci as well as other modes, and you may have to set the mode correctly in the BIOS to be able to access the existing data on the drives (at least I have read that that's the case with Intel chipsets). - anton -- M. Anton Ertl Some things have to be seen to be believed anton(a)mips.complang.tuwien.ac.at Most things have to be believed to be seen http://www.complang.tuwien.ac.at/anton/home.html |