anaconda doesn't appear to be running dmraid during install - cannot see bios raid...
FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
anaconda doesn't appear to be running dmraid during install - cannot see bios raid...
Help!
I am trying to install FC6 from a DVD image to my AMD 64 bit system with SATA drives. This system also has a NVIDIA bios raid that I configured for RAID Mirror and Stripe with 4k block size. When I boot up the system, the first available time I can hit control-alt-F2 (for a shell) is right when anaconda loads. At this point, I then do an ls -l on /dev/mapper and see nothing but a control file.
I then proceed to type in:
# dmraid -a y
and when I do, I can then see three files in the /dev/mapper directory that were created. They are in the form nvidia_bbdeeff, nvidia_bbdeeff-0 and nvidia_bbdeeff-1. (the bbdeeff is arbitrary - this changes every time I reboot). When I do an fdisk on the first block device "nvidia_bbdeeff", I am able to see the correct LUN size that it is supposed to be (after it has been RAID'ed).
Next, I've performed a control-alt-f6 to go back into anaconda and finish the installation. I then click next on the following windows until I get into the hard drive selection. At this point, all I can see are the actual hard drives, not the raid device.
I've even tried booting off the cdrom using "linux dodmraid", but the only two drivers I see loaded are ohci and sata_nv. There was nothing about dmraid.
Anyone have any suggestions on how I can get anaconda to re-scan the drives or re-load to see the new raid in /dev/mapper? It appears that every time I try to get to a shell prompt, anaconda has already looked at the hardware and will not re-scan.
32bit or 64bit on dual DVD? Do a clean install, let FC6 do stuff & custom size parts
I installed FC5 OK on a HW RAID 3 and also to a BIOS nVidia Raid 0, but not on 0+1 (aka 10). Not sure now if I used both 32 & 64 bit options from a dual architecture DVD, but I think I did (~90%). Some installs took a couple of reboots before Desktop displayed OK. Think I installed GRUB to a boot partition (Custom adjustment I made), swap, root & home used the defaults!
I would just let install run, the `nvidia_bbdeeff' is normal as I recall, but not sure why it would change arbitrarily.
What HW are you using? Do you have a HD as IDE primary master (even though not used for the RAID install?? {Need depends on which nVidia nForce 4 board is being used!}
[7033 edit: May not be an issue on your system!
* What are you trying to accomplish with a 1 TB mirrored/striped RAID? *
Were you having problems completing the install, or just curious in use of dmraid??
{7033 EDTD Just let Fedora Core # do a default install, allow to run through on its own. See if it will reboot and let you log on as User)
* By LUN, did you mean LVM??*
HW I raided successfully AMD FX-55@~2.9GHz (& 60x2), 2gbOCZddr400, OCd ~512.
Mainboards; Tyan S2865 [rev 1.0 (??)] G2NR (& +ANRF). nForce 4 chipsets
Raid 3 WD2500KS 3x; on PNY S-Cure Data card {5103}, like to try 5x RAID 3- Digital Video Editing Capture=nVid RAID0 2xWD740GD, maybe 4x Raptor Raid 10.
- - -
7033@1451EST. Do not know the HW you are using, but will try to find what I can.
1. * New to LQ, or totally new to GNU/Linux?* Seems you have some programming background.
2. Can you get the nVidia fx3500 support from the FC6 DVD and load it when FC5 installs?
2nd; Are you loading 32 or 64 bit?? I think 32 may work better for RAID (Ed Guess only, no real exp)
Last edited by digital8doug; 02-07-2007 at 12:17 AM.
Reason: I would TRY 2 HD RAID0 w/FC5, MAKE SURE YOU UNDERSTAND DEFAULT INSTALL; then upgrade to 8 HD on a 2ND INSTALL or update? Maybe that would work?
Thanks for the quick reply! The hardware I'm using is a Sun Ultra 40. I've not been able to dig up what motherboard they're using but it's a dual-core AMD_64 system with an NVIDIA FX3500 graphics and on-board raid (I am fairly certain it's the nvidia bios raid though...) It has 8 250G SATA drives. I was hoping to have all 8 in a 0+1 RAID so that performance would be maxed and protection existed. I was hesitant to use LVM b/c I would end up wasting an entire disk to the boot partition and not enable it in a 4 disk stripe. I'm not sure how I can accomplish RAID 0+1 without the bios raid and use a 4 disk stripe - if you know of a way, I'm open as I feel the cpu's will be ok handling the RAID.
Someone had recommended to me to load FC5 (as they had a better experience with it recognizing bios raid) and then upgrade to FC6, but the only problem is FC5 won't recognize my nvidia fx3500 card and when it tries to load X, it just hangs with a black screen and the white X for the mouse. I've tried disabling acpi but that didn't work either. I tried also using the text installer but the screen just stayed a solid blue.
I'm wondering if there's a way to force anaconda to reload the drive configuration. I just don't know why dmraid has to be run by hand and that anaconda isn't starting it up to see all available devices (including RAID)? It's only after I type in dmraid -a y in another terminal window that I see the nvidia devices in /dev/mapper - but by this time anaconda has already appeared to have scanned the hardware and won't re-read what's changed. It just doesn't seem to see the raid...
I just noticed your edited questions. I'm fairly new to LQ, but I've been working lightly with FC4 for a while now. I do have some programming experience, but won't call myself an expert by any means! The machine will be used for recording and streaming video.
I'm curious - how can I do what you are asking? That is, get the nvidia support from the FC6 DVD and load it when FC5 installs?
I had an NVIDIA FeForce 7600 GS (PCI-E) lying around, so I removed the fx3500 thinking it would at least recognize that in FC5, however it still would not recognize the nvidia card. It just says:
NVIDIA Corporation unknown device 0392
right when X tries to load. It then turns the screen black and all you see is the white X, which you can move it with the mouse, but that is all you can do. I again tried "linux text" at the boot prompt, but that just ends up giving me a blue screen (literally a blue screen) right after it says "Running anoaconda, the Fedora Core System Installer". It again gives me the same NVIDIA error and that is all I can do.
I'm looking for suggestions from anyone out there!! Help!!
Think EDIT is better than new post! Similar desires, I just got Macbook Pro; n-l DVE
Quote:
Originally Posted by avoidspam
SNPD/EDTD; fairly new to LQ, but I've been working lightly with FC4 for a while now., do have some programming experience, but not an expert by any means! This machine will be used for (recording) CAPTURING and streaming video.
How can I get the nvidia support from the 64bit install of FC6 DVD and load it when FC5 installs?
Until you get FC6 running, logging in as user. Try simple default install (but ADD multimedia selections for DVE) to a single hard drive, or maybe RAID 0 on only 2. Need MORE LQ help!
Last edited by digital8doug; 02-03-2007 at 03:16 PM.
Reason: AvoidSpam; Please enable LQ email so I can send you other guidance, no need for it in this help thread. LQ user help stuff. Or email me. Left click d.8d,, follow the links for mail, not PM. TY d8d
could anyone out there in the LQ community shed some light on how I can boot up FC5 without having it probe the video card? If I try:
linux noprobe
at the boot prompt, it disables my usb keyboard and mouse also and I can't get past the screen asking to test my CD. (My system won't take a PS2 keyboard and mouse)
X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.9-22.18.bz155725.ELsmp x86_64Red Hat, Inc.
Current Operating System: Linux localhost.localdomain 2.6.15-1.2054_FC5 #1 SMP Tue Mar 14 15:48:20 EST 2006 x86_64
Build Date: 06 March 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/ramfs/X.log", Time: Sat Feb 3 19:19:29 2007
(++) Using config file: "/tmp/XConfig.test"
Could not init font path element unix/:7100, removing from list!
# XFree86 4 configuration created by pyxf86config
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, a font server independent of the X server is
# used to render fonts.
FontPath "/usr/share/X11/fonts/misc:unscaled"
FontPath "/usr/share/X11/fonts/Type1/"
FontPath "/usr/share/X11/fonts/Speedo/"
FontPath "/usr/share/X11/fonts/75dpi:unscaled"
FontPath "/usr/share/X11/fonts/100dpi:unscaled"
FontPath "/usr/share/X11/fonts/korean:unscaled"
FontPath "/usr/share/X11/fonts/cyrillic:unscaled"
FontPath "/usr/share/fonts/ISO8859-2/misc:unscaled"
FontPath "/usr/share/fonts/ISO8859-2/75dpi:unscaled"
FontPath "/usr/share/fonts/ISO8859-2/100dpi:unscaled"
FontPath "/usr/share/fonts/ISO8859-9/misc:unscaled"
FontPath "/usr/share/fonts/ISO8859-9/75dpi:unscaled"
FontPath "/usr/share/fonts/ISO8859-9/100dpi:unscaled"
FontPath "/usr/share/fonts/KOI8-R/misc:unscaled"
FontPath "/usr/share/fonts/KOI8-R/75dpi:unscaled"
FontPath "unix/:7100"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
Load "dri"
EndSection
Section "InputDevice"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "X7202A"
DisplaySize 380 300
### Comment all HorizSync and VertSync values to use DDC:
HorizSync 31.0 - 81.0
VertRefresh 56.0 - 75.0
Option "dpms"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "vesa"
VendorName "Videocard vendor"
BoardName "nVidia Corporation Unknown device 029d"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Viewport 0 0
Depth 16
Modes "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
These are all generated from FC5 during the install. Again, this is what is in the /tmp directory after anaconda tries to load and all I see is a black screen and white X.
I did a "linux rescue" and skipped everything so I could get a command prompt. I then typed in dmraid -a y and saw the devices in /dev/mapper. I noticed that anaconda was still running in the background. When I tried to kill it, it just forced a reboot. So I tried it again, but this time I didn't kill the existing anaconda, I just ran another anaconda install by typing in:
It then started the installer, but would still not display the nvidia RAID devices. I just don't get it...
Is there any way to boot the system without anaconda running?
What if I had installed FC6 on an external USB device and then booted off that? If the full OS install could see the /dev/mapper directory - would I then be able to install FC6 at that point? Would anyone have any other suggestions?
ok, so I tried another option. I figured, since I used the default anaconda startup (listed in previous post), I may as well modify it to mount on the raid device. This way, maybe, anaconda would see the raid. So, to do this, I created new sdi devices in /dev using mknod and using the same major/minor numbers as the RAID device, like this:
Code:
mknod /dev/sdi b 253 2
mknod /dev/sdi1 b 253 3
...
mknod /dev/sd14 b 253 16
then, I started another anaconda using reference to the new device:
but that still didn't work... I could not see sdi in the list of disks via the anaconda GUI, however, I did notice something else... Here is the output from anaconda.log in the /tmp directory when I did that...
Code:
18:07:19 INFO : 8147812 kB are available
18:07:19 INFO : modules to insert cramfs fat vfat sunrpc lockd fscache nfs_acl nfs loop isofs floppy edd pcspkr squashfs
18:07:19 INFO : loaded cramfs from /modules/modules.cgz
18:07:19 INFO : loaded fat from /modules/modules.cgz
18:07:19 INFO : loaded vfat from /modules/modules.cgz
18:07:19 INFO : loaded sunrpc from /modules/modules.cgz
18:07:19 INFO : loaded lockd from /modules/modules.cgz
18:07:19 INFO : loaded fscache from /modules/modules.cgz
18:07:19 INFO : loaded nfs_acl from /modules/modules.cgz
18:07:19 INFO : loaded nfs from /modules/modules.cgz
18:07:19 INFO : loaded loop from /modules/modules.cgz
18:07:19 INFO : loaded floppy from /modules/modules.cgz
18:07:19 INFO : loaded edd from /modules/modules.cgz
18:07:19 INFO : loaded pcspkr from /modules/modules.cgz
18:07:19 INFO : loaded squashfs from /modules/modules.cgz
18:07:19 DEBUG : module(s) isofs not found
18:07:19 INFO : inserted /tmp/cramfs.ko
18:07:19 INFO : inserted /tmp/fat.ko
18:07:19 INFO : inserted /tmp/vfat.ko
18:07:19 INFO : inserted /tmp/sunrpc.ko
18:07:19 INFO : inserted /tmp/lockd.ko
18:07:19 INFO : inserted /tmp/fscache.ko
18:07:19 INFO : inserted /tmp/nfs_acl.ko
18:07:19 INFO : inserted /tmp/nfs.ko
18:07:19 INFO : inserted /tmp/loop.ko
18:07:22 WARNING : failed to insert module (19)
18:07:22 ERROR : failed to insert /tmp/floppy.ko
18:07:22 INFO : inserted /tmp/edd.ko
18:07:22 INFO : inserted /tmp/pcspkr.ko
18:07:22 INFO : inserted /tmp/squashfs.ko
18:07:22 INFO : load module set done
18:07:22 INFO : modules to insert ipv6
18:07:23 INFO : loaded ipv6 from /modules/modules.cgz
18:07:23 INFO : inserted /tmp/ipv6.ko
18:07:23 INFO : load module set done
18:07:23 INFO : modules to insert cdrom ide-cd
18:07:23 INFO : loaded cdrom from /modules/modules.cgz
18:07:23 INFO : loaded ide-cd from /modules/modules.cgz
18:07:23 INFO : inserted /tmp/cdrom.ko
18:07:23 INFO : inserted /tmp/ide-cd.ko
18:07:23 INFO : load module set done
18:07:23 INFO : modules to insert scsi_mod sd_mod sr_mod
18:07:23 INFO : loaded scsi_mod from /modules/modules.cgz
18:07:23 INFO : loaded sd_mod from /modules/modules.cgz
18:07:23 INFO : loaded sr_mod from /modules/modules.cgz
18:07:23 INFO : inserted /tmp/scsi_mod.ko
18:07:23 INFO : inserted /tmp/sd_mod.ko
18:07:23 INFO : inserted /tmp/sr_mod.ko
18:07:23 INFO : load module set done
18:07:23 INFO : modules to insert scsi_transport_iscsi libiscsi iscsi_tcp
18:07:23 INFO : loaded scsi_transport_iscsi from /modules/modules.cgz
18:07:23 INFO : loaded libiscsi from /modules/modules.cgz
18:07:23 INFO : loaded iscsi_tcp from /modules/modules.cgz
18:07:23 INFO : inserted /tmp/scsi_transport_iscsi.ko
18:07:23 INFO : inserted /tmp/libiscsi.ko
18:07:23 INFO : inserted /tmp/iscsi_tcp.ko
18:07:23 INFO : load module set done
18:07:23 INFO : looking for usb controllers
18:07:23 INFO : found USB controller ehci-hcd
18:07:23 INFO : modules to insert ehci-hcd
18:07:23 INFO : loaded ehci-hcd from /modules/modules.cgz
18:07:23 INFO : inserted /tmp/ehci-hcd.ko
18:07:23 INFO : load module set done
18:07:23 INFO : found USB controller ohci-hcd
18:07:23 INFO : modules to insert ohci-hcd
18:07:23 INFO : loaded ohci-hcd from /modules/modules.cgz
18:07:23 INFO : inserted /tmp/ohci-hcd.ko
18:07:23 INFO : load module set done
18:07:23 DEBUG : waiting for usb to become stable...
18:07:27 DEBUG : 4 seconds.
18:07:27 INFO : modules to insert hid keybdev
18:07:28 DEBUG : module(s) hid keybdev not found
18:07:28 INFO : load module set done
18:07:29 INFO : found firewire controller ohci1394
18:07:29 INFO : modules to insert ieee1394 ohci1394
18:07:29 INFO : loaded ieee1394 from /modules/modules.cgz
18:07:29 INFO : loaded ohci1394 from /modules/modules.cgz
18:07:29 INFO : inserted /tmp/ieee1394.ko
18:07:29 INFO : inserted /tmp/ohci1394.ko
18:07:29 INFO : load module set done
18:07:32 INFO : probing for firewire scsi devices
18:07:32 DEBUG : no firewire scsi devices found
18:07:32 DEBUG : no pcic controller found
18:07:32 DEBUG : probing buses
18:07:32 DEBUG : finished bus probing
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0377
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0375
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0378
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0374
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0374
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0376
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 036a
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0368
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0361
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0369
18:07:32 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] Unknown device 1103
18:07:32 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] Unknown device 1102
18:07:32 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] Unknown device 1101
18:07:32 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] Unknown device 1100
18:07:32 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] Unknown device 1103
18:07:32 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] Unknown device 1102
18:07:32 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] Unknown device 1101
18:07:32 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] Unknown device 1100
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0377
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0375
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0378
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0374
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0374
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0376
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0370
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0368
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0364
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0369
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Unknown device 0371
18:07:32 DEBUG : ignoring driverless device nVidia Corporation Quadro FX 3500
18:07:32 INFO : modules to insert forcedeth libata sata_nv
18:07:32 INFO : loaded forcedeth from /modules/modules.cgz
18:07:32 INFO : loaded libata from /modules/modules.cgz
18:07:32 INFO : loaded sata_nv from /modules/modules.cgz
18:07:33 INFO : inserted /tmp/forcedeth.ko
18:07:33 INFO : inserted /tmp/libata.ko
18:07:38 INFO : inserted /tmp/sata_nv.ko
18:07:38 INFO : load module set done
18:07:38 INFO : trying to mount CD device hda
18:07:39 INFO : 8147812 kB are available
18:07:47 INFO : mntloop loop0 on /mnt/runtime as /tmp/ramfs/stage2.img fd is 40
18:07:47 DEBUG : MD5SUM -> c28ef7bfe1e9ba56b07c733925e876fd
18:07:47 DEBUG : skipsectors = 15
18:07:47 INFO : supported = 0
18:07:55 DEBUG : going to set language to en_US.UTF-8
18:07:55 INFO : setting language to en_US.UTF-8
18:07:55 INFO : 53 keymaps are available
18:07:56 INFO : Loading SELinux policy
18:07:56 INFO : getting ready to spawn shell now
18:07:56 INFO : modules to insert
18:07:56 INFO : load module set done
18:07:56 INFO : modules to insert
18:07:56 INFO : load module set done
18:07:56 INFO : modules to insert
18:07:56 INFO : load module set done
18:07:56 DEBUG : probing buses
18:07:56 DEBUG : finished bus probing
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI Express bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI Express bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI Express bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI Express bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI Express bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI Express bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 Memory Controller
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 SMBus
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 LPC Bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 Memory Controller
18:07:56 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
18:07:56 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
18:07:56 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
18:07:56 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
18:07:56 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
18:07:56 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
18:07:56 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
18:07:56 DEBUG : ignoring driverless device Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI Express bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI Express bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI Express bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI Express bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI Express bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI Express bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 PCI bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 SMBus
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 LPC Bridge
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 Memory Controller
18:07:56 DEBUG : ignoring driverless device nVidia Corporation MCP55 High Definition Audio
18:07:56 DEBUG : ignoring driverless device nVidia Corporation Quadro FX 3500
18:07:56 INFO : modules to insert
18:07:56 INFO : load module set done
18:07:56 INFO : modules to insert md raid0 raid1 raid5 raid6 xor raid456 msdos jbd ext3 gfs2 lock_nolock reiserfs jfs xfs dm-mod dm-zero dm-mirror dm-snapshot dm-multipath dm-round-robin dm-emc
18:07:56 INFO : loaded raid0 from /modules/modules.cgz
18:07:56 INFO : loaded raid1 from /modules/modules.cgz
18:07:56 INFO : loaded xor from /modules/modules.cgz
18:07:56 INFO : loaded raid456 from /modules/modules.cgz
18:07:56 INFO : loaded msdos from /modules/modules.cgz
18:07:56 INFO : loaded jbd from /modules/modules.cgz
18:07:56 INFO : loaded ext3 from /modules/modules.cgz
18:07:56 INFO : loaded gfs2 from /modules/modules.cgz
18:07:56 INFO : loaded lock_nolock from /modules/modules.cgz
18:07:56 INFO : loaded reiserfs from /modules/modules.cgz
18:07:56 INFO : loaded jfs from /modules/modules.cgz
18:07:56 INFO : loaded xfs from /modules/modules.cgz
18:07:56 INFO : loaded dm-mod from /modules/modules.cgz
18:07:56 INFO : loaded dm-zero from /modules/modules.cgz
18:07:56 INFO : loaded dm-mirror from /modules/modules.cgz
18:07:56 INFO : loaded dm-snapshot from /modules/modules.cgz
18:07:56 INFO : loaded dm-multipath from /modules/modules.cgz
18:07:56 INFO : loaded dm-round-robin from /modules/modules.cgz
18:07:56 INFO : loaded dm-emc from /modules/modules.cgz
18:07:56 DEBUG : module(s) md raid5 raid6 not found
18:07:56 INFO : inserted /tmp/raid0.ko
18:07:56 INFO : inserted /tmp/raid1.ko
18:07:56 INFO : inserted /tmp/xor.ko
18:07:57 INFO : inserted /tmp/raid456.ko
18:07:57 INFO : inserted /tmp/msdos.ko
18:07:57 INFO : inserted /tmp/jbd.ko
18:07:57 INFO : inserted /tmp/ext3.ko
18:07:57 INFO : inserted /tmp/gfs2.ko
18:07:57 INFO : inserted /tmp/lock_nolock.ko
18:07:57 INFO : inserted /tmp/reiserfs.ko
18:07:57 INFO : inserted /tmp/jfs.ko
18:07:57 INFO : inserted /tmp/xfs.ko
18:07:57 INFO : inserted /tmp/dm-mod.ko
18:07:57 INFO : inserted /tmp/dm-zero.ko
18:07:57 INFO : inserted /tmp/dm-mirror.ko
18:07:57 INFO : inserted /tmp/dm-snapshot.ko
18:07:57 INFO : inserted /tmp/dm-multipath.ko
18:07:57 INFO : inserted /tmp/dm-round-robin.ko
18:07:57 INFO : inserted /tmp/dm-emc.ko
18:07:57 INFO : load module set done
18:07:57 INFO : looking for USB mouse...
18:07:57 INFO : USB mouse found, loading mousedev module
18:07:57 INFO : modules to insert mousedev
18:07:57 DEBUG : module(s) mousedev not found
18:07:57 INFO : load module set done
18:07:57 DEBUG : failed to loading mousedev module
18:07:57 INFO : looking for scsi tape devices
18:07:57 INFO : no scsi tape devices found
18:07:57 INFO : Running anaconda script /usr/bin/anaconda
18:07:58 INFO : using only installclass _Fedora
18:07:58 INFO : _Fedora is only installclass, using it
18:07:58 INFO : no /tmp/fcpconfig; not configuring zfcp
18:11:41 INFO : using only installclass _Fedora
18:11:41 INFO : _Fedora is only installclass, using it
18:11:41 INFO : Display mode = g
18:11:41 INFO : Method = cdrom://hdi:/mnt/source
18:11:41 WARNING : no floppy devices found but we'll try fd0 anyway
18:11:49 INFO : Started mini-wm
18:11:49 INFO : Starting graphical installation...
18:11:50 ERROR : could not create directory //dev/mapper: File exists
18:11:50 INFO : no /tmp/fcpconfig; not configuring zfcp
18:11:50 INFO : no /tmp/fcpconfig; not configuring zfcp
18:11:50 INFO : Detected 7968M of memory
18:11:50 INFO : Swap attempt of 1000M to 2000M
18:11:50 WARNING : step installtype does not exist
18:11:50 WARNING : step complete does not exist
18:11:51 INFO : moving (1) to step welcome
18:11:54 INFO : moving (1) to step findrootparts
18:11:54 DEBUG : starting mpaths
18:11:54 DEBUG : self.driveList(): ['sda', 'sdb', 'sdc', 'sdd', 'sde', 'sdf', 'sdg', 'sdh']
18:11:54 DEBUG : DiskSet.skippedDisks: []
18:11:54 DEBUG : DiskSet.skippedDisks: []
18:11:54 DEBUG : starting all mpaths on drives ['sda', 'sdb', 'sdc', 'sdd', 'sde', 'sdf', 'sdg', 'sdh']
18:11:54 DEBUG : scanning for multipath on drives ['sda', 'sdb', 'sdc', 'sdd', 'sde', 'sdf', 'sdg', 'sdh']
18:11:54 DEBUG : mpaths: []
18:11:54 DEBUG : done starting mpaths. Drivelist: ['sda', 'sdb', 'sdc', 'sdd', 'sde', 'sdf', 'sdg', 'sdh']
18:11:54 DEBUG : starting dmraids
18:11:54 DEBUG : self.driveList(): ['sda', 'sdb', 'sdc', 'sdd', 'sde', 'sdf', 'sdg', 'sdh']
18:11:54 DEBUG : DiskSet.skippedDisks: []
18:11:54 DEBUG : DiskSet.skippedDisks: []
18:11:54 DEBUG : starting all dmraids on drives ['sda', 'sdb', 'sdc', 'sdd', 'sde', 'sdf', 'sdg', 'sdh']
18:11:54 DEBUG : scanning for dmraid on drives ['sda', 'sdb', 'sdc', 'sdd', 'sde', 'sdf', 'sdg', 'sdh']
18:11:54 DEBUG : done starting dmraids. Drivelist: ['sda', 'sdb', 'sdc', 'sdd', 'sde', 'sdf', 'sdg', 'sdh']
18:12:02 WARNING : step complete does not exist
18:12:02 INFO : moving (1) to step partitionobjinit
18:12:02 INFO : no initiator set
18:12:11 ERROR : could not create directory //dev/mapper: File exists
18:12:11 INFO : moving (1) to step parttype
18:13:25 INFO : moving (1) to step partition
18:13:59 INFO : moving (-1) to step parttype
now, it seems that dmraid is starting (because I ran it before anaconda) as well as recognizes all drives (sda - sdh) but anaconda is STILL not recognizing or looking in the /dev/mapper directory or seeing the devices I built (sdi)... what gives???
Hi,
I just posted myself, saying how pleased I am with the FC6 Anaconda. I am also using a bios raid setup. Mine is a more standard Sil 3112 though on a more standard 32 bit PC. Anaconda found it by itself without me having to running anything manually. I presume it must be running dmraid within lvm or something..
So I take it you have 2 problems, one to do with the graphics card and one with the hard drives (?)
If that is correct, I would concentrate on the harddrive first. I wonder if it is easier for Anaconda to find an existing partitioned setup instead of creating a new one. So maybe you could try with a different tool or boot CD to partition and format the setup you want (I used Partition Magic in the past when I initially struggled to install Ubuntu, I guess you'll need something else with that Sun machine though...).
If Linux drivers exist for your graphics card, you can always install that after your main installation of Linux itself.
...I might be missing something in your above posts though...
Unable complete FC6 install, X hangs @ Black screen, no nVid drivers 7600GS or fx3500
avoidspam e-mail me. I would not use Part magic if I were you. I always have problems w/ PM8.05. Linux partitioner is much better & NEWER.
Quote:
Originally Posted by monsm
SNPD/EDTD pleased with 32bit FC6 Anaconda, using a bios raid setup, on a more standard Sil 3112. Anaconda found it by itself without me having to running anything manually. I presume it must be running dmraid within lvm or something..
So I take it you have 2 problems, one to do with the graphics card and one with the hard drives (?) If that is correct, I would concentrate on the harddrive first. I wonder if it is easier for Anaconda to find an existing partitioned setup instead of creating a new one.
(I used Partition Magic in past when struggled to install Ubuntu, I guess you'll need something else with that Sun machine though...).
If Linux drivers exist for your graphics card, you can always install that after your main installation of Linux itself.
well, thanks to all those who have helped me along the way. I've had to give up due to time constraints and was forced to go the way of software RAID10. Further investigation revealed that anaconda FC6 no longer loads the raid10 module. If you look above, it would only load the modules for raid0 raid1 raid5 raid6 and raid456 (whatever this is). After the OS is loaded it would then give you the option of creating raid10, but not during.
As an attempted workaround, I created 4 raid devices (mirrors on 8 drives), then I was going to load the OS and stripe across the disks (with the exception of the / and /boot parititons) but once anaconda recognized the raid 1, it caused my screen to go black - exactly the same way FC5 displayed it(given above). Which leads me to believe that FC5 did recognize raid10 and that's why it was a black screen. It didn't know what to do with it.
Oh well, it's not the ideal solution I was out for, but it is giving me a 4 disk stripe mirrored to 4 disks. Perhaps if anyone is interested I could post how I did this. It's not the best but it works... I'm currently testing chunk sizes and testing read/write speeds now to see what will be best suited for this environment...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
32bit or 64bit on dual DVD? Do a clean install, let FC6 do stuff & custom size parts
The machine will be used for recording and streaming video.
(My system won't take a PS2 keyboard and mouse)
