Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > Linux Forums > HOWTO-Related Questions

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #11  
Old 4th January 2006, 20:17
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,741 Times in 2,575 Posts
Default

Quote:
Originally Posted by Dieda2000
Moreover, while booting there is alway the message
" grep: command not found"
How did you use grep in this early stage of booting?
Is grep installed? Run
Code:
which grep
to find out.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
Sponsored Links
  #12  
Old 7th January 2006, 17:22
mshah mshah is offline
Junior Member
 
Join Date: Jan 2006
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by till
Yes, this thraed is how to make fake raids.

You see in windows one raid volume, because there exist drivers for windows.
On linux you see the single harddisks, thats because there are no linux RAID drivers for SATA available for your controller.

That explains why you see 4 vs. 2 volumes.

If you explain the errors you get a bit more detailed, we can try to fix them.
Till - thanks for the repsonse. As I explained, I don't see any error. Only thing I see is that one of the RAID0 volume is not visible while other RAID1 volumes are visible as unbound. So can't use them. Should I be attaching some file from the computer so that we can find out what's going on ? Let me know where to look for boot log file or any other file and I'll attach it here. Again, thanks for your help.
Reply With Quote
  #13  
Old 6th February 2006, 02:55
joek9k joek9k is offline
Junior Member
 
Join Date: Feb 2006
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default making software RAID work in Linux

I managed to trick Fedora Core 4 into using my Silicon Image (SIL) SATA controller for RAID 1 (mirroring) by first configuring the software RAID 1 in SuSE 10 on fresh install
md0 mounted /
md1 mounted /home
md2 mounted /swap

The funny part is the whole reason why I then took these partitions into Fedora Core 4 was because after doing the install with SuSE 10 and formatting the drives, installing everything, SuSE 10 kernel panicked upon first reboot.

So I put Fedora core 4 in there, DiskDruid picked up the partition info and then I installed it and it gave me a warning message that you'd have to see to believe but after Fedora installed I could definately hear the drives working as a Software RAID (the sound of the configuration is a dead give-away, it's like an echo, same as a recent XP pro install I did) . So it worked, but it didn't work in my O/S of choice (SuSE 10)

Another thing is I had to go and purchase the Silicon Image controller (PCI) for 40 bux (a software raid controller) which makes me want to take back my SATA drives and just get a couple IDE drives and do a software IDE raid and save all the effort.

Now that I see how much BS the software raid is I'm thinking that a 3ware hardware raid controller with true Linux support and a Server motherboard with PCI 64bit is probably worth the money because my time is worth a lot more than all this BS. Anyone selling a server motherboard for cheap?

It'd be nice if all this bios raid software raid worked right now and saw one drive instead of two. I've been searching for other distros but I think it'd be cheaper to just get a real server instead of trying to turn a $50 dollar motherboard into a real server. Maybe in Kernel 2.7.
Reply With Quote
  #14  
Old 14th March 2006, 19:27
markes markes is offline
Junior Member
 
Join Date: Mar 2006
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Nice Howto, it´s works fine, but some peculiar things i have noticed:

- after boot and login in KDE
in MyComputer/media floppy is mounted always althougt i unmounted it.
media:/ -Konqueror
/Diskette (fd0)
/DVD (dvdram)
/Festplatte (mapper/via_bdeaacdjjh1)
/Festplatte (mapper/via_bdeaacdjjh10)
/Festplatte (mapper/via_bdeaacdjjh4)
/Festplatte (mapper/via_bdeaacdjjh5)
/Festplatte (mapper/via_bdeaacdjjh6)
/Festplatte (mapper/via_bdeaacdjjh7)
/Festplatte (mapper/via_bdeaacdjjh8)
/Festplatte (mapper/via_bdeaacdjjh9)

- If i logout and then login as different or same user without reboot i will get:
MyComputer/media:/ -Konqueror
/8.4G Medium
/Diskettenlaufwerk
after clicking 8.4G Medium i get the message:
Could not mount device.
The reported error was:
mount: can't find /dev/sda1 in /etc/fstab or /etc/mtab

- some warnings and errors in /var/log/messages and /var/log/boot.msg
my /var/log/messages, the warning: grep not found too
...
Mar 14 10:31:41 linux kernel: attempt to access beyond end of device
Mar 14 10:31:41 linux kernel: sda: rw=0, want=312581850, limit=312581808
Mar 14 10:31:41 linux kernel: printk: 807 messages suppressed.
Mar 14 10:31:41 linux kernel: Buffer I/O error on device dm-0, logical block 312581804
...
Mar 14 10:32:01 linux kernel: bootsplash: status on console 0 changed to on
Mar 14 10:32:01 linux hal-subfs-mount[6327]: By hald-subfs-mount created dir /media/floppy got removed.
Mar 14 10:32:01 linux kernel: printk: 90 messages suppressed.
Mar 14 10:32:01 linux kernel: Buffer I/O error on device sda4, logical block 8241312
...
Mar 14 10:32:02 linux hal-subfs-mount[6338]: MOUNTPOINT:: /media/floppy
Mar 14 10:32:02 linux kernel: subfs 0.9
Mar 14 10:32:02 linux hal-subfs-mount[6338]: Collected mount options and Called(0) /bin/mount -t subfs -o fs=floppyfss,sync,procuid,nosuid,nodev,exec /dev/fd0 "/media/floppy"
Mar 14 10:32:02 linux kernel: end_request: I/O error, dev fd0, sector 0
Mar 14 10:32:02 linux submountd: mount failure, No such device or address
Mar 14 10:32:02 linux kernel: end_request: I/O error, dev fd0, sector 0
Mar 14 10:32:02 linux kernel: subfs: unsuccessful attempt to mount media (256)

/var/log/boot.msg
...
<6>scsi0 : sata_via
<7>ata2: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 88:80ff
<6>ata2: dev 0 ATA, max UDMA7, 312581808 sectors: lba48
<6>ata2: dev 0 configured for UDMA/133
<6>scsi1 : sata_via
<5> Vendor: ATA Model: SAMSUNG HD160JJ Rev: ZM10
<5> Type: Direct-Access ANSI SCSI revision: 05
<5>SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
<5>SCSI device sda: drive cache: write back
<5>SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
<5>SCSI device sda: drive cache: write back
<6> sda: sda1 sda2 < > sda3 sda4
<5>Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
<5> Vendor: ATA Model: SAMSUNG HD160JJ Rev: ZM10
<5> Type: Direct-Access ANSI SCSI revision: 05
<5>SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
<5>SCSI device sdb: drive cache: write back
<5>SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
<5>SCSI device sdb: drive cache: write back
<6> sdb:<3>Buffer I/O error on device sda3, logical block 2361344
<3>Buffer I/O error on device sda3, logical block 2361345
<3>Buffer I/O error on device sda3, logical block 2361346
<3>Buffer I/O error on device sda3, logical block 2361347
<3>Buffer I/O error on device sda3, logical block 2361348
<3>Buffer I/O error on device sda3, logical block 2361349
<3>Buffer I/O error on device sda3, logical block 2361350
<3>Buffer I/O error on device sda3, logical block 2361351
<3>Buffer I/O error on device sda4, logical block 8241312
<3>Buffer I/O error on device sda4, logical block 8241313
<5>Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
...
<3>Buffer I/O error on device sda3, logical block 2361344
..
Loading required kernel modules
doneRestore device permissionsdone
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: invalid flag 0xffffbf76 of partition table 5 will be corrected by w(rite)
Disk /dev/sdb doesn't contain a valid partition table
Activating remaining swap-devices in /etc/fstab...

I have installed it like you described, without any errors:
-the line in /etc/sysconfig/kernel i have changed to
INITRD_MODULES="sata_via via82cxxx processor thermal fan reiserfs dm-mod"

-my /boot/grub/device.map
(fd0) /dev/fd0
(hd0) /dev/mapper/via_bdeaacdjjh

-my /boot/grub/menu.lst
color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,3)/boot/message

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
chainloader (hd0,0)+1

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 10.0
root (hd0,3)
kernel /boot/vmlinuz root=/dev/mapper/via_bdeaacdjjh4 vga=0x317 selinux=0 resume=/dev/mapper/via_bdeaacdjjh3 splash=silent showopts
initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Diskette
chainloader (fd0)+1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 10.0
root (hd0,3)
kernel /boot/vmlinuz root=/dev/mapper/via_bdeaacdjjh4 vga=normal showopts ide=nodma apm=off acpi=off noresume selinux=0 nosmp noapic maxcpus=0 edd=off 3
initrd /boot/initrd

linux:/home/mk # fdisk -l
Warnung: ignoriere weitere Daten in Partitionstabelle 5
Warnung: ignoriere weitere Daten in Partitionstabelle 5
Warnung: ignoriere weitere Daten in Partitionstabelle 5
Warnung: Schreiben wird ungültiges Flag 0xffffbf76 in Part.-tabelle 5 korrigiere n

Platte /dev/sda: 160.0 GByte, 160041885696 Byte
255 Köpfe, 63 Sektoren/Spuren, 19457 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes

Gerät boot. Anfang Ende Blöcke Id System
/dev/sda1 * 1 1020 8193118+ 7 HPFS/NTFS
/dev/sda2 1021 36715 286720087+ f W95 Erw. (LBA)
/dev/sda3 36716 36862 1180777+ 82 Linux Swap / Solaris
/dev/sda4 36863 38914 16482690 83 Linux
/dev/sda5 ? 44606 181585 1100285363 3c PartitionMagic recovery

Platte /dev/sdb: 160.0 GByte, 160041885696 Byte
255 Köpfe, 63 Sektoren/Spuren, 19457 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes

Festplatte /dev/sdb enthält keine gültige Partitionstabelle


linux:/home/mk # fdisk /dev/mapper/via_bdeaacdjjh

Die Anzahl der Zylinder für diese Platte ist auf 38914 gesetzt.
Daran ist nichts verkehrt, aber das ist größer als 1024 und kann
in bestimmten Konfigurationen Probleme hervorrufen mit:
1) Software, die zum Bootzeitpunkt läuft (z. B. ältere LILO-Versionen)
2) Boot- und Partitionierungssoftware anderer Betriebssysteme
(z. B. DOS FDISK, OS/2 FDISK)

Befehl (m für Hilfe): p

Platte /dev/mapper/via_bdeaacdjjh: 320.0 GByte, 320083770368 Byte
255 Köpfe, 63 Sektoren/Spuren, 38914 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes

Gerät boot. Anfang Ende Blöcke Id System
/dev/mapper/via_bdeaacdjjh1 * 1 1020 8193118+ 7 HPFS/NTFS
/dev/mapper/via_bdeaacdjjh2 1021 36715 286720087+ f W95 Erw. (LBA)
/dev/mapper/via_bdeaacdjjh3 36716 36862 1180777+ 82 Linux Swap / Solaris
/dev/mapper/via_bdeaacdjjh4 36863 38914 16482690 83 Linux
/dev/mapper/via_bdeaacdjjh5 1021 3570 20482843+ 7 HPFS/NTFS
/dev/mapper/via_bdeaacdjjh6 3571 6120 20482843+ 7 HPFS/NTFS
/dev/mapper/via_bdeaacdjjh7 6121 18868 102398278+ 7 HPFS/NTFS
/dev/mapper/via_bdeaacdjjh8 18869 31616 102398278+ 7 HPFS/NTFS
/dev/mapper/via_bdeaacdjjh9 31617 36575 39833136 7 HPFS/NTFS
/dev/mapper/via_bdeaacdjjh10 36576 36715 1124518+ b W95 FAT32


my /etc/fstab
/dev/mapper/via_bdeaacdjjh4 / reiserfs acl,user_xattr 1 1
/dev/mapper/via_bdeaacdjjh1 /windows/C ntfs noauto,ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/mapper/via_bdeaacdjjh5 /windows/D ntfs noauto,ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/mapper/via_bdeaacdjjh6 /windows/E ntfs noauto,ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/mapper/via_bdeaacdjjh7 /windows/F ntfs noauto,ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/mapper/via_bdeaacdjjh8 /windows/G ntfs noauto,ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/mapper/via_bdeaacdjjh9 /windows/H ntfs noauto,ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/mapper/via_bdeaacdjjh10 /windows/I vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/mapper/via_bdeaacdjjh3 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/dvdram /media/dvdram subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocha rset=utf8 0 0
/dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0

greets
markes
Reply With Quote
  #15  
Old 19th March 2006, 01:10
HBauer HBauer is offline
Junior Member
 
Join Date: Mar 2006
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I installed everything following the Howto on my system using a via SATA-controller. But booting the installed system results in a lot of timeouts for the underlying SATA (/dev/sda, /dev/sdb) disks. Also the "missing grep" appears. Any recommendations?

Greetings, HB

BTW: Isn't it possible to transfer the part you did using the Gentoo Live-CD to the installed SuSE using chroot?
Reply With Quote
  #16  
Old 19th March 2006, 09:55
markes markes is offline
Junior Member
 
Join Date: Mar 2006
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Default

The warnings: "grep: command not found" is produced by this Code in line 1971 from mkinitrd:
cat_linuxrc <<-EOF
|# Workaround: dmraid should not probe cdroms, but it does.
|# We'll remove all cdrom device nodes till dmraid does this check by itself.
|for y in hda hdb hdc hdd hde hdf hdg hdh sr0 sr1 sr2 sr3;
|do
| if (grep -q "$y" /proc/sys/dev/cdrom/info)
| then
| rm -f /dev/"$y"
| fi
|done
|# Now we can load dmraid
|dmraid -ay -i
EOF

Solution:
Find out on wich port your cdrom drive hangs and delete all the other registers. In my case my cdrom hangs on Secondary Port as Master and so "hdc". So i deletetd all except hdc (|for y in hdc and save the file. After that you have to type mkinitrd in console as root.

The warnings
...
Mar 19 08:58:44 linux kernel: attempt to access beyond end of device
Mar 19 08:58:44 linux kernel: sda: rw=0, want=312581850, limit=312581808
Mar 19 08:58:44 linux kernel: Buffer I/O error on device dm-0, logical block 312581804
Mar 19 08:58:44 linux kernel: attempt to access beyond end of device
Mar 19 08:58:44 linux kernel: sda: rw=0, want=312581852, limit=312581808
Mar 19 08:58:44 linux kernel: Buffer I/O error on device dm-0, logical block 312581805
Mar 19 08:58:44 linux kernel: attempt to access beyond end of device
Mar 19 08:58:44 linux kernel: sda: rw=0, want=312581854, limit=312581808
Mar 19 08:58:44 linux kernel: Buffer I/O error on device dm-0, logical block 312581806
etc

are produced from your linux kernel. You have to fix your kernel if these warnings will be awkward for you:

Code:
diff -Nur linux-2.6.15/fs/partitions/check.c linux-2.6.15-check/fs/partitions/check.c
--- linux-2.6.15/fs/partitions/check.c	2006-01-03 04:21:10.000000000 +0100
+++ linux-2.6.15-check/fs/partitions/check.c	2006-02-08 21:20:03.000000000 +0100
@@ -175,8 +175,19 @@
 		memset(&state->parts, 0, sizeof(state->parts));
 		res = check_part[i++](state, bdev);
 	}
-	if (res > 0)
+	if (res > 0) {
+		sector_t from, cap;
+		for(i = 1; i < state->limit; i++) {
+			from = state->parts[i].from;
+			cap = get_capacity(hd);
+			if(state->parts[i].size + from > cap) {
+				printk(KERN_WARNING " %s: partition %s%d beyond device capacity\n",
+						hd->disk_name, hd->disk_name, i);
+				state->parts[i].size = cap - (from < cap ? from : cap);
+			}
+		}
 		return state;
+	}
 	if (!res)
 		printk(" unknown partition table\n");
 	else if (warn_no_part)
Look at http://tienstra4.flatnet.tudelft.nl/~gerte/gen2dmraid/ and https://www.redhat.com/archives/atar.../msg00015.html for further information. On http://tienstra4.flatnet.tudelft.nl/...dmraid-2.0.iso you can also download the Gentoo based LiveCD with dmraid-1.0.0-rc9. So you can use Gentoo directly without installing dmraid.

greets
markes

Last edited by markes; 19th March 2006 at 10:08.
Reply With Quote
  #17  
Old 20th March 2006, 02:31
HBauer HBauer is offline
Junior Member
 
Join Date: Mar 2006
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks for your answer, but that's not exactly my problem.
Booting the original SuSE-kernel results in endless hanging periods (ata1/2 timeout command 0x?? stats 0x?? host_stats 0x??).
Booting a reduced kernel I compiled myself results in a kernel panic:
Code:
waiting for device /dev/mapper/via_ebdfgdfgeg2 to appear: ok
no record for 'mapper/via_ebdfgdfgeg2' in database
rootfs: major=254 minor=2 devn=65026
Mounting root /dev/mapper/via_ebdfgdfgeg2
mount: no such device
umount2: device or ressource busy
Kernel panic - not syncing: Attempted to kill init!
I suspect udev to be responsible for that. Does anybody know the exact reason?

Booting from a separate hd the same modified kernel (my own compilation) drastically reduces the timeout hanging time.

Any suggestions about that?

Greetings, HB

Last edited by HBauer; 20th March 2006 at 02:42.
Reply With Quote
  #18  
Old 21st March 2006, 16:22
markes markes is offline
Junior Member
 
Join Date: Mar 2006
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Default

hmmm, seems to be an fstab or mkinitrd problem. Have you tryed also mkintrd from crushton?

greets
markes
Reply With Quote
  #19  
Old 21st March 2006, 22:38
HBauer HBauer is offline
Junior Member
 
Join Date: Mar 2006
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Yes, it's exactly the one I tried. I tried Fedora 5 and Gentoo, both of them work with the same hardware, but I don't know where to start with the analysis of mkinitrd...

Greetings, HB
Reply With Quote
  #20  
Old 22nd March 2006, 06:53
mgosr mgosr is offline
Junior Member
 
Join Date: Mar 2006
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
 
Default For now...

If you aren't too crazy about which distro, RedHat Fedora Core 5 [Bordeaux] set up (AND BOOTED!!) with out a glitch on my via sata raid 0 and opteron 242*2. Could be best to get it and go on, at least for now.

Eventually maybe we'll have answers to why 64-bit technology and sata raid has been so lagging in support. Our hardware will be outdated before working solutions arrive. Anyone know if there is a 64-bit flash plug-in?
Reply With Quote
Reply

Bookmarks

Thread Tools
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


All times are GMT +2. The time now is 06:31.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.