Fedora Linux Support Community & Resources Center
  #1  
Old 4th February 2013, 03:11 PM
Fedor Offline
Registered User
 
Join Date: Apr 2005
Posts: 31
linuxubuntufirefox
F18 How to install on Bios Raid

I have a laptop with BiosRaid 1 and Windows 7 running. I do need this Windows, but most of my work I do on Ubuntu which is installed in dual boot.
Now I want to replace Ubunto by Fedora. So I run the installation and that worked fine but than it seems to destoy the Raid in some way. At least the Intel Storage Manager does repair it every time I boot Win7 after any Fedora session.. This does not happen with Ubuntu.
In the installation guide I found this:

>>Fedora 18 uses mdraid instead of dmraid for installation onto Intel BIOS RAID sets. These sets are detected automatically, and devices with Intel ISW metadata are recognized as mdraid instead of dmraid. Note that the device node names of any such devices under mdraid are different from their device node names under dmraid. Therefore, special precautions are necessary when you migrate systems with Intel BIOS RAID sets.
Local modifications to /etc/fstab, /etc/crypttab or other configuration files which refer to devices by their device node names will not work in Fedora 18. Before migrating these files, you must therefore edit them to replace device node paths with device UUIDs instead. You can find the UUIDs of devices with the blkid command. <<

Frankly, it doesn't really mean anything to me. But I guess here is the source of my trouble.
Can please someone tell me if my guess is right and than how to do the installation with mdraid?
Reply With Quote
  #2  
Old 5th February 2013, 08:09 AM
chrismurphy Offline
Registered User
 
Join Date: May 2010
Posts: 1,058
macoschrome
Re: F18 How to install on Bios Raid

Quote:
Originally Posted by Fedor View Post
Can please someone tell me if my guess is right and than how to do the installation with mdraid?
Safest options is to boot from a LiveCD to do the following; I think your Fedora installation is installed on one of the disks, rather than on the IMSM array. But at your risk you can boot again off the hard drive into Fedora.

1. Web browser, download bootinfo script.
2. You'll need to make it executable, and then run it.
Code:
chmod 755 bootinfoscript
./bootinfoscript
3. Post the results.txt file to the forum.
4. Grab lsdrv you want the 2nd to last file.
5. Make it executable, run it.
Code:
chmod 755 lsdrv
./lsdrv > lsdrv.txt
6. Post lsdrv.txt to the forum.
7. Post the Fedora installations logs found in /var/anaconda/. I'd like to see anaconda.log, storage.log, program.log. If you're booted off LiveCD you'll need to mount the root file system for your Fedora install.
Reply With Quote
  #3  
Old 5th February 2013, 09:44 AM
Fedor Offline
Registered User
 
Join Date: Apr 2005
Posts: 31
linuxchrome
Re: F18 How to install on Bios Raid

Thank you!

I'll be too busy next two days, so I can do it on thursday earliest.
Reply With Quote
  #4  
Old 7th February 2013, 01:11 PM
Fedor Offline
Registered User
 
Join Date: Apr 2005
Posts: 31
linuxfirefox
Re: F18 How to install on Bios Raid

Done with little success.

The result of bootinfoscript is attached.

lsdrv returned with error, no outpu. I attach the error messages

There was no /var/anaconda

How to proceed?

-----------------------------------------------------------------------------

Boot Info Script 0.61 [1 April 2012]


============================= Boot Info Summary: ===============================


md/imsm0: __________________________________________________ ____________________

File system:
Boot sector type: Unknown
Boot sector info:
Mounting failed: mount: unknown filesystem type ''

md/Volume_01: __________________________________________________ ________________

File system:
Boot sector type: Grub2 (v1.99)
Boot sector info: Grub2 (v1.99) is installed in the boot sector of
md/Volume_01 and looks at sector 1 of the same hard
drive for core.img, but core.img can not be found at
this location.
Mounting failed: mount: unknown filesystem type ''
mount: unknown filesystem type ''

============================ Drive/Partition Info: =============================

no valid partition table found
"blkid" output: __________________________________________________ ______________

Device UUID TYPE LABEL

/dev/md126
/dev/md126p1 0EA4B6AFA4B69923 ntfs System-reserviert
/dev/md126p2 E6B6B9DEB6B9AF83 ntfs
/dev/md126p3 f9f914c5-df91-4e64-bef7-4718966ad6da ext4
/dev/md126p5 96f91f63-3fc3-4a26-a52c-c89e98ecf0ac swap
/dev/md126p6 662df3ae-2954-4c45-886c-1b381c257cdc ext4
/dev/md126p7 d0961415-1f9e-45a1-be3c-e1834195579c ext4
/dev/sda isw_raid_member
/dev/sdb isw_raid_member

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/md126p2 /run/media/fw/E6B6B9DEB6B9AF83 fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,def ault_permissions,allow_other,blksize=4096)
/dev/md126p3 /boot ext4 (rw,relatime,seclabel,data=ordered)
/dev/md126p6 / ext4 (rw,relatime,seclabel,data=ordered)
/dev/md126p7 /home ext4 (rw,relatime,seclabel,data=ordered)


======================== Unknown MBRs/Boot Sectors/etc: ========================

Unknown BootLoader on md/imsm0



========= Devices which don't seem to have a corresponding hard drive: =========

sdc

=============================== StdErr Messages: ===============================

No volume groups found
hexdump: /dev/md/imsm0: Das Argument ist ungültig


----------------------------------------------------------------------------------------------------------------------


----------------

lsdrv returned with error:

Traceback (most recent call last):
File "./lsdrv", line 409, in <module>
probe_block('/sys/block/'+x)
File "./lsdrv", line 368, in probe_block
blk.preFS += ", %s (%s) %s/sec" % (blk.md.sync_action, blk.md.SYNC, k2size(blk.md.sync_speed))
File "./lsdrv", line 174, in k2size
return (fmt+"k") % k
TypeError: float argument required, not NoneType

----------------
Reply With Quote
  #5  
Old 8th February 2013, 01:37 AM
chrismurphy Offline
Registered User
 
Join Date: May 2010
Posts: 1,058
macoschrome
Re: F18 How to install on Bios Raid

From the live CD:

Code:
cat /proc/mdstat
fdisk -l
You will probably need to mount the root fs somewhere to get the logs:

Code:
sudo mount /dev/md126p6 /mnt
ls -l /mnt/var/log/anaconda
Yes I got it wrong originally when I said /var/anaconda; it's /var/log/anaconda, but the livecd's /var/log won't have this, you have to mount the root of the Fedora system.

Also, did you choose to not install a boot loader? Because bootinfoscript reports the wrong boot loader version. What's installed on the disk is a version from Ubuntu, not the current version Fedora 18 installs.
Reply With Quote
  #6  
Old 8th February 2013, 02:56 AM
Fedor Offline
Registered User
 
Join Date: Apr 2005
Posts: 31
linuxfirefox
Re: F18 How to install on Bios Raid

Here we go.

Do you really want me to post the logs? They are about half a MB size.

Bootloader is very strange. What I did was, I made a fresh install of Win7, deleted the Ubuntu partitions to get clean space for Fedora an installed Fedora from a live disk. I used all defaults settings exceptI deselected LVM.

It is now about 2 am here and I have to get up at 5, so if zou could answer the above question right now I will post the stuff before I hit the sack. Otherwise tomorrow.

--------------------------------

mdstat

Personalities : [raid1] [raid0] [raid6] [raid5] [raid4] [raid10]
md126 : active raid1 sda[1] sdb[0]
488384323 blocks super external:/md127/0 [2/2] [UU]

md127 : inactive sdb[1](S) sda[0](S)
4256 blocks super external:imsm

unused devices: <none>

--------------------------------------

fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0defbebc

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sda2 206848 488384511 244088832 7 HPFS/NTFS/exFAT
/dev/sda3 488384512 489408511 512000 83 Linux
/dev/sda4 489408512 976768645 243680067 5 Extended
/dev/sda5 489410560 497438719 4014080 82 Linux swap / Solaris
/dev/sda6 497440768 602298367 52428800 83 Linux
/dev/sda7 602300416 976766975 187233280 83 Linux

Disk /dev/sdb: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0defbebc

Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sdb2 206848 488384511 244088832 7 HPFS/NTFS/exFAT
/dev/sdb3 488384512 489408511 512000 83 Linux
/dev/sdb4 489408512 976768645 243680067 5 Extended
/dev/sdb5 489410560 497438719 4014080 82 Linux swap / Solaris
/dev/sdb6 497440768 602298367 52428800 83 Linux
/dev/sdb7 602300416 976766975 187233280 83 Linux

Disk /dev/mapper/live-rw: 4294 MB, 4294967296 bytes, 8388608 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/live-osimg-min: 4294 MB, 4294967296 bytes, 8388608 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/md126: 500.1 GB, 500105546752 bytes, 976768646 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0defbebc

Device Boot Start End Blocks Id System
/dev/md126p1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/md126p2 206848 488384511 244088832 7 HPFS/NTFS/exFAT
/dev/md126p3 488384512 489408511 512000 83 Linux
/dev/md126p4 489408512 976768645 243680067 5 Extended
/dev/md126p5 489410560 497438719 4014080 82 Linux swap / Solaris
/dev/md126p6 497440768 602298367 52428800 83 Linux
/dev/md126p7 602300416 976766975 187233280 83 Linux


-------------------------------------------------------
Reply With Quote
  #7  
Old 8th February 2013, 06:56 AM
chrismurphy Offline
Registered User
 
Join Date: May 2010
Posts: 1,058
macoschrome
Re: F18 How to install on Bios Raid

Yes post the logs.

---------- Post added at 10:56 PM ---------- Previous post was at 10:51 PM ----------

While booted from the LiveCD:
Code:
mount /dev/md126p6 /mnt
mount /dev/md126p3 /mnt/boot
mount -o bind /proc /mnt/proc
mount -o bind /dev /mnt/dev
mount -o bind /sys /mnt/sys
chroot /mnt
grub2-install /dev/md126
grub2-mkconfig -o /boot/grub2/grub.cfg
exit
reboot
This should mount the array partitions, special file systems, chroot all of it, install the boot loader to the proper location, and create a new grub.cfg

Yes this will replace the Windows boot manager with GRUB (it is reversible from the LiveCD should it be necessary by using syslinux mbr.bin written over the first sector of /dev/md126), your grub menu upon reboot should have entries for Fedora and Windows.
Reply With Quote
  #8  
Old 8th February 2013, 02:23 PM
Fedor Offline
Registered User
 
Join Date: Apr 2005
Posts: 31
windows_7firefox
Re: F18 How to install on Bios Raid

Two Points:
1st I apologize. I should have given more details about the new installation. As said, I did a new installation of Win7. When it was up and running, I deleted the partitions used by Ubuntu (Mint 14) before. Then I used a Fedora Live DVD to install Fedora 18-64.
When the installation finished, I made a reboot. And there came up Grub with the Fedora boot menu (and still does) with blue and white text. I can boot Fedora and Win7. The first step I took was to boot Fedora and to run yum update. Now I did the first two requested answers from the fresh installed Fedora, not from the LiveCD. After another reboot I selected Win7 and let it repair the Raid. So far I already did come before I opened this thread. Before I install the bootloader I want to make sure, you understand there is a boot menu and I can choose between initial Fedora, upgraded Version and Win7. Shall I still install the bootloader?
(By the way, there came up another issue with Fedora, it does not rebboot or shutdown, I have to use sysrq.)

2nd, I did try to post the logs but for some reason it dit not work. Anything different when there are huge posts?
Reply With Quote
  #9  
Old 9th February 2013, 08:10 AM
chrismurphy Offline
Registered User
 
Join Date: May 2010
Posts: 1,058
macoschrome
Re: F18 How to install on Bios Raid

[QUOTE=Fedor;1632902]Two Points:
Quote:
Before I install the bootloader I want to make sure, you understand there is a boot menu and I can choose between initial Fedora, upgraded Version and Win7.
For now, skip reinstalling GRUB.
Attach the current /boot/grub2/grub.cfg file.
Attach or post contents of the current /etc/mdadm.conf file.
Post the results of this command, while booted from Fedora install (not LiveCD):
Code:
df -h
Quote:
2nd, I did try to post the logs but for some reason it dit not work. Anything different when there are huge posts?
Don't paste it in the forum. Attach as a file. If it's too big, compress it then attach. Or you can post them on pastebin and post the URL.

Last edited by chrismurphy; 9th February 2013 at 08:12 AM.
Reply With Quote
  #10  
Old 9th February 2013, 06:47 PM
Fedor Offline
Registered User
 
Join Date: Apr 2005
Posts: 31
linuxfirefox
Re: F18 How to install on Bios Raid

Done!

I did put in one file separated by a line of ########

Each section got atitle:

anaconda.log
program.log
storage.log
fdisk.out
mdstat.out
grub.cfg
df -h

Good luck!
I will now start up Win7 to let it repair the raid ---

---------- Post added at 05:51 PM ---------- Previous post was at 05:30 PM ----------

Hold on, please. Fedora did reboot (without sysrq) and the raid was still ok. Let me try out a few things, e.g. install some software and see.
Maybe something has changed with the update.

---------- Post added at 06:47 PM ---------- Previous post was at 05:51 PM ----------

Strange, seems to be ok now. I would guess due to a kernel change. In earlier tries it was even enough to start Fedora and only shutdown again and the raid had to be repaired.
And so it was after the first shutdown after the update.
Anyway, the problem disappeared now. I will close this thread.
And yes, I forgot the link:

http://pastebin.com/8HhWiSJx

I will leave it for some time just in case you are curious. If you see something, please let me know.

For now all I can do is to thank you for your help and time.
Reply With Quote
  #11  
Old 9th February 2013, 08:30 PM
chrismurphy Offline
Registered User
 
Join Date: May 2010
Posts: 1,058
macoschrome
Re: F18 How to install on Bios Raid

Quote:
Originally Posted by Fedor View Post
Anyway, the problem disappeared now. I will close this thread.
Well it's difficult to say what fixed it exactly without regression and some more testing. The logs indicate it was installed to the IMSM RAID, not to devices. When there's a kernel change, there's also an updating of the initramfs. So it could have been a systemd update, or a dracut update, or a kernel update that fixed it. Or even simply rerunning dracut might have fixed it.

But the install logs indicate it was installing to the array. Not to a disk.

BTW, realize that with swap on this array, using a check scrub will indicate mismatch errors on the array. Next, the array can't self-repair during normal operation in the event of a read error from either disk, because linux's SCSI layer time out will be set shorter than the error time out of these consumer drives. So what happens is a timeout error gets recorded in dmesg, and the offending bad block is never fixed. Later, if a drive dies, you'll have problems rebuilding the array if the surviving drive had bad sectors.

So you need to run:
smarctl -l scterc /dev/sd[ab]

If the reply back is "SCT Commands not supported" then you will need to adjust the SCSI layout timeout so it's longer than the drives, so that read errors are properly transfered to the md layer where it can be fixed.

If the reply back is timing information, chances are the times need to be changed to something like 7 seconds (that's a value of 70 since the times are in deciseconds) so that upon bad sector errors, the drive gives up in 7 seconds and reports a read error to the kernel (and hence md) so the error can be fixed.

It's better to do this change in the drive, if the drive supports SCT ERC. But it isn't a persistent setting. You'll need a startup script to tell the drive at each startup.

If SCT ERC isn't supported by the drives, the SCSI layer change is made with:

echo 120 >/sys/block/sdX/device/timeout

This is pointed at physical drives, not the array. So you need a line for each drive, and can also go in a startup script.
Reply With Quote
  #12  
Old 10th February 2013, 01:16 PM
Fedor Offline
Registered User
 
Join Date: Apr 2005
Posts: 31
linuxchrome
Re: F18 How to install on Bios Raid

Quote:
Well it's difficult to say what fixed it exactly without regression and some more testing.
If you want to do some more testing Iwould be glad to assist, even if you ask me to start over with a fresh installation of Fedora.

smartctl -i /dev/sd[ab]

returns:

....
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Sun Feb 10 12:58:02 2013 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

but smartctl -l scterc /dev/sd[ab] tells me:

SCT Error Recovery Control:
Read: Disabled
Write: Disabled

and this is not what you mean with
Quote:
SCT Commands not supported
, I guess.

I'd look through the manpages of smartctl but did not find how to enable it, if it can be done at all.

By the way, yesterday another new kernel was installed. The one at installation time was 3.6.10...
the first update gave 3.7.5... and now 3.7.6...

So, how will we proceed?
Reply With Quote
  #13  
Old 12th February 2013, 08:39 AM
chrismurphy Offline
Registered User
 
Join Date: May 2010
Posts: 1,058
macoschrome
Re: F18 How to install on Bios Raid

Try this:
Code:
smartctl -l scterc,70,70 /dev/sdX
See what gets returned back to you for that. And if it's not an error, repeat:

Code:
smartctl -l scterc /dev/sdX
And report back that result, which should look like you previous post, except no longer say disabled.

What model drive is reported by smartctl in the first few lines of
Code:
smartctl -i /dev/sdX
Reply With Quote
  #14  
Old 12th February 2013, 09:02 AM
Fedor Offline
Registered User
 
Join Date: Apr 2005
Posts: 31
linuxchrome
Re: F18 How to install on Bios Raid

smartctl -l scterc /dev/sdX returned:

SCT Error Recovery Control:
Read: 70 (7.0 seconds)
Write: 70 (7.0 seconds)

smartctl -i /dev/sda

Model Family: Western Digital Scorpio Blue Serial ATA
Device Model: WDC WD5000BEVT-22ZAT0
Serial Number: WD-WXNX08LKA308
LU WWN Device Id: 5 0014ee 2acd50eb3
Firmware Version: 01.01A01
User Capacity: 500.107.862.016 bytes [500 GB]
Sector Size: 512 bytes logical/physical


smartctl -i /dev/sdb

Model Family: Western Digital Scorpio Blue Serial ATA
Device Model: WDC WD5000BEVT-22ZAT0
Serial Number: WD-WXNX08SH0968
LU WWN Device Id: 5 0014ee 2022ad356
Firmware Version: 01.01A01
User Capacity: 500.107.862.016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Reply With Quote
  #15  
Old 13th February 2013, 01:14 AM
chrismurphy Offline
Registered User
 
Join Date: May 2010
Posts: 1,058
macoschrome
Re: F18 How to install on Bios Raid

Quote:
Originally Posted by Fedor View Post
smartctl -l scterc /dev/sdX returned:

SCT Error Recovery Control:
Read: 70 (7.0 seconds)
Write: 70 (7.0 seconds)
OK good. So in the event the firmware ECC can't recover sector data in 7 seconds, it will stop trying and report a read error and sector number, which will find its way to md. And then md will go get the data from the other drive and pass it up the chain to your app and also pass a write of that data to the drive and LBA for the bad sector. The drive firmware will determine if it's a transient or persistent failure and in case it's persistent, it'll make the sector bad, and reassign the LBA to a reserve sector. And all will be right as rain.

You have to put the command above in a startup script, for each drive in the array. The values clear when the drive is powered down.

Quote:
Model Family: Western Digital Scorpio Blue Serial ATA
Device Model: WDC WD5000BEVT-22ZAT0
Interesting. Are these relatively new drives? I have one of these that's probably 4-5 years old, same capacity, and it also supports SCT ERC (Western Digital calls this TLER). Yet a Scorpio Black I bought maybe 18 months ago, doesn't support SCT ERC. Annoying. When drives don't support this, their time out for such an error can be in the realm of 2 minutes, meanwhile your app is hanging waiting for data. Some apps get pretty pissed off when this happens.

Last edited by chrismurphy; 13th February 2013 at 01:17 AM.
Reply With Quote
Reply

Tags
bios, f18, install, raid, windows 7

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Intel ICH RAID in BIOS. Use or not? hceuterpe Installation, Upgrades and Live Media 1 5th January 2010 01:22 PM
onboard BIOS raid supported ? mrechte Hardware & Laptops 6 6th August 2008 02:08 PM
anaconda isn't running dmraid during install - cannot see bios raid... avoidspam Installation, Upgrades and Live Media 8 6th February 2007 10:27 PM
Raid in bios. Can I remove it? dpawson Installation, Upgrades and Live Media 0 6th December 2006 08:45 PM
How to access fat32 partitions on BIOS RAID 0? electron1948 Installation, Upgrades and Live Media 6 21st August 2006 10:41 AM


Current GMT-time: 22:32 (Monday, 25-09-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat