Re: Reiser FS
Condon Thomas A KPWA wrote: > > > Doug, does ext3 work on / partitions? > > This question spurs me to ask: > > Does Reiser FS work for / partitions? reiserfs will work on any partition -- caveat: your kernel must be compiled with reiserfs included (not a module). Then even /boot can be reiserfs. Ciao, David A. Bandel -- Focus on the dream, not the competition. -- Nemesis Racing Team motto ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
Yes... But I have yet to recover mine which recently came up with a "Inconsistent Filesystem Structure" message on boot... I may have missed a post regarding this, but I haven't seen anyones' response if it has been sent... :) Any help would be appreciated! THX! My question remains... how would I recover from this? What are the tools available for ReiserFS? Matt "Condon Thomas A KPWA"To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> <[EMAIL PROTECTED]cc: .navy.mil> Subject: Reiser FS Sent by: linux-users-admin @linux.nf 07/18/01 02:20 PM Please respond to linux-users > Doug, does ext3 work on / partitions? This question spurs me to ask: Does Reiser FS work for / partitions? In Harmony's Way, and In A Chord, Tom :-}) +--+ | Thomas A. Condonemail: [EMAIL PROTECTED] | | Computer Engineer phone: (360) 315-7609| | Barbershop Bass SingerSailor and Singer of Chanties | | Left Handed and In My Right Mind | | "If you want to know what God thinks about money, just | | look at the people He gives it to." -- Old Irish Saying | +--+ ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Wed, Jul 18, 2001 at 01:36:41PM -0500, David A. Bandel wrote: ... >reiserfs will work on any partition -- caveat: your kernel must be >compiled with reiserfs included (not a module). Then even /boot can be >reiserfs. It would probably be better to have a separate ext2 /boot partition if one wants to boot different versions of Linux off the same /boot partition. We do this to avoid any potential 1024 segment problems, sharing /boot amongst multiple Linux versions. Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC UUCP: camco!bill PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 URL: http://www.celestial.com/ When I hear a man applauded by the mob I always feel a pang of pity for him. All he has to do to be hissed is to live long enough. -- H.L. Mencken, ``Minority Report'' ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Wed, 18 Jul 2001 20:16:20 -0700, Bill Campbell wrote: >It would probably be better to have a separate ext2 /boot partition if one >wants to boot different versions of Linux off the same /boot partition. We >do this to avoid any potential 1024 segment problems, sharing /boot amongst >multiple Linux versions. This brings up a side point for me. I just spent several days trying to get Grub back working on my main Linux box. I had delete 2 unused partitions (extended logical drives) and this changed the /dev point for my root drive. I did have a primary partition, 30M, that was mounted as /boot (when the system worked, before my little escapade). My / part went from /dev/sda8 to sda6, this frelled up the whole thing big time. I was finally able to get Grub working again by copying all the info from my old /boot part to a new directory on / called /boot. the old part is no longer mounted. My question is, How would one go about making a new /boot part and get Grub to boot off it? I tried to put Grub on the old /boot ( root was (hd0,2) the kernel line was "kernel = /boot/vmlinuz-2.4.2-modular vga=274 quiet root=/dev/sda6" The Kernel would start but it would panic saying it couldn't mount the root file system. I ended up with /boot on the / part and Grub on the /dev/sda6 or /part. I'd like to get /boot back on /dev/sda3 but After all the trouble I am a bit hesitant. I have stage1 and 2 on /dev/sda6 for now, I am using power boot to get there, I have DOS and Wincrap also on the drive. What is the trick? stayler ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
Bill Campbell wrote: > > On Wed, Jul 18, 2001 at 01:36:41PM -0500, David A. Bandel wrote: > ... > >reiserfs will work on any partition -- caveat: your kernel must be > >compiled with reiserfs included (not a module). Then even /boot can be > >reiserfs. > > It would probably be better to have a separate ext2 /boot partition if one > wants to boot different versions of Linux off the same /boot partition. We > do this to avoid any potential 1024 segment problems, sharing /boot amongst > multiple Linux versions. > I run several different distros on one system (my test system). /boot often has two or three different kernels (just in case), but since the first thing I do is rebuild a kernel after install it's optimized for my system. I use the same kernel to boot 4 different linux distros (I just copy /lib/modules/2.4.x to the other distro). So lilo points to the same kernel for 4 different distros. The only difference is the root= line. Ext2 is safe, but since my kernel is built with reiserfs built in, it works OK for me. Ciao, David A. Bandel -- Focus on the dream, not the competition. -- Nemesis Racing Team motto ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Thursday 19 July 2001 09:02, Shawn Tayler wrote: > On Wed, 18 Jul 2001 20:16:20 -0700, Bill Campbell wrote: > >It would probably be better to have a separate ext2 /boot partition if one > >wants to boot different versions of Linux off the same /boot partition. > > We do this to avoid any potential 1024 segment problems, sharing /boot > > amongst multiple Linux versions. > > This brings up a side point for me. I just spent several days trying > to get Grub back working on my main Linux box. I had delete 2 unused > partitions (extended logical drives) and this changed the /dev point > for my root drive. I did have a primary partition, 30M, that was > mounted as /boot (when the system worked, before my little escapade). > My / part went from /dev/sda8 to sda6, this frelled up the whole thing > big time. I was finally able to get Grub working again by copying all > the info from my old /boot part to a new directory on / called /boot. > the old part is no longer mounted. > > My question is, How would one go about making a new /boot part and get > Grub to boot off it? I tried to put Grub on the old /boot ( root was > (hd0,2) the kernel line was "kernel = /boot/vmlinuz-2.4.2-modular > vga=274 quiet root=/dev/sda6" The Kernel would start but it would > panic saying it couldn't mount the root file system. I ended up with > /boot on the / part and Grub on the /dev/sda6 or /part. I'd like to > get /boot back on /dev/sda3 but After all the trouble I am a bit > hesitant. I have stage1 and 2 on /dev/sda6 for now, I am using power > boot to get there, I have DOS and Wincrap also on the drive. > > What is the trick? > > stayler Install grub on the MBR with it pointing to the /boot partition... and the grub stages and menu.lst would also be on that /boot partition. I think I sent you an install command to do this. The only thing 'hard coded' within the grub boot code is a pointer to where to find its menu.lst and other load parts. ++ + Bruce S. Marshall [EMAIL PROTECTED] Bellaire, MI 07/19/01 09:37 + ++ "You might be a high-tech Red-neck if: your checkbook always balances" ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Friday 20 July 2001 00:54, David A. Bandel wrote: > system. I use the same kernel to boot 4 different linux distros (I just > copy /lib/modules/2.4.x to the other distro). So lilo points to the > same kernel for 4 different distros. Yep. That's kleva. You could also ln -s /boot/modules /lib/modules and maintain a single set >The only difference is the root= line. I don't follow? root=/dev/hd? Do you mean you have multiple image= blocks in lilo.conf, and only the root= changes? -- http://linux.nf -- [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
Mike Andrew wrote: > > On Friday 20 July 2001 00:54, David A. Bandel wrote: > > > system. I use the same kernel to boot 4 different linux distros (I just > > copy /lib/modules/2.4.x to the other distro). So lilo points to the > > same kernel for 4 different distros. > > Yep. That's kleva. > > You could also ln -s /boot/modules /lib/modules and maintain a single set no, because /boot never gets mounted (so never gets corrupted, at least as long as the hard drive electronics are working). > > >The only difference is the root= line. > > I don't follow? root=/dev/hd? Do you mean you have multiple image= blocks in > lilo.conf, and only the root= changes? exactly. No need to change the kernel, I just pick the distro I want to boot to by name, and the root = /dev/hdXX line changes. I even use the same vga = 792 line in all of them. Skeleton looks like this: my lilo.conf (last image deleted, you get the idea, /boot is on /dev/hda1 which is marked active partition): # # /etc/lilo.conf - generated by Lizard # # target boot = /dev/hda install = /boot/boot.b # options prompt delay = 50 timeout=50 #message=/boot/message default=Caldera image = /boot/bzImage-2.4.5 label = Caldera root = /dev/hda2 vga = 792 read-only image = /boot/bzImage-2.4.5 label = LFS root = /dev/hdb2 vga = 792 read-only image = /boot/bzImage-2.4.5 label = SuSE root = /dev/hdb3 vga = 792 read-only One system, same hardware, same kernel, same modules, different distros. I share /boot and /home (and of course, swap) between all distros. /home also nfs exported. BTW, from other systems, I usually run xdm clients (all the distros are _slllooowww_ on a 233MHz PI w/ 32 Mb RAM, and I have a couple of those). If you do that and use Caldera as the X display manager, you'll need /etc/X?.hosts files or Caldera won't serve them a login screen. I have X0.hosts and X1.hosts (linked). On a 100Mb network, working on one of the 233 PIs is like working directly on the 700MHz Athlon w/ 256Mb (because you are), but several systems connected at the same time isn't at all noticeable. Now that's a license question if I ever had one. I have one W3.1 installation. The other systems have LFS on them getting their display from the Caldera system. Do I need a license for each XDM connection? If so, do I need a license for each FTP connection? How about each telnet/SSH connection. I was planning to install LTS (Linux Terminal Server program) to remote boot to an XDM login on the remote systems. Where does this fit in the licensing scheme? I have a headache. Excuse me while I go take 800mg Motrin and throw a few more lawyers into the Atlantic Ocean. Ciao, David A. Bandel -- Focus on the dream, not the competition. -- Nemesis Racing Team motto ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
RE: Reiser FS
> From: David A. Bandel [mailto:[EMAIL PROTECTED]] > > Does Reiser FS work for / partitions? > > reiserfs will work on any partition -- caveat: your kernel must be > compiled with reiserfs included (not a module). Then even /boot can be > reiserfs. I've run into a problem with a new hard drive and a ReiserFS installed on it. My current suspicion is that the BIOS must also accept/handle the ReiserFS for it to be able to boot from a drive formatted in that manner. My reason for assuming this is that I have installed SuSE 7.2 Pro on a new hard drive, and the Bios tells me there is an Hard Drive Failure if I try to boot from it. But if I boot from CD or floppy I can not only see that installation, but access it, as well. Does anyone know if this is the case? Or a way to circumvent this problem if so? I haven't found a BIOS update that mentions file system type. I am reluctant to re-install (for the third time) if this won't fix the problem. In Harmony's Way, and In A Chord, Tom :-}) +--+ | Thomas A. Condonemail: [EMAIL PROTECTED] | | Computer Engineer phone: (360) 315-7609| | Barbershop Bass SingerSailor and Singer of Chanties | | Left Handed and In My Right Mind | | "If you want to know what God thinks about money, just | | look at the people He gives it to." -- Old Irish Saying | +--+ ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
RE: Reiser FS
I think that your hypothesis is flawed. No BIOS has the ability to understand filesystems. It sees raw hardware. Its quite possible that the MBR of that drive is corrupted, which is making it appear as if there is no bootable OS on the drive. --- Condon Thomas A KPWA <[EMAIL PROTECTED]> wrote: > > > From: David A. Bandel [mailto:[EMAIL PROTECTED]] > > > Does Reiser FS work for / partitions? > > > > reiserfs will work on any partition -- caveat: your kernel must be > > compiled with reiserfs included (not a module). Then even /boot can > be > > reiserfs. > > I've run into a problem with a new hard drive and a ReiserFS installed > on > it. My current suspicion is that the BIOS must also accept/handle the > ReiserFS for it to be able to boot from a drive formatted in that > manner. > > My reason for assuming this is that I have installed SuSE 7.2 Pro on a > new > hard drive, and the Bios tells me there is an Hard Drive Failure if I > try to > boot from it. But if I boot from CD or floppy I can not only see that > installation, but access it, as well. > > Does anyone know if this is the case? Or a way to circumvent this > problem > if so? > > I haven't found a BIOS update that mentions file system type. I am > reluctant to re-install (for the third time) if this won't fix the > problem. = Lonni J. Friedman [EMAIL PROTECTED] Linux FAQ & Step-by-step help:http://netllama.ipfox.com . __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
Condon Thomas A KPWA wrote: > > > From: David A. Bandel [mailto:[EMAIL PROTECTED]] > > > Does Reiser FS work for / partitions? > > > > reiserfs will work on any partition -- caveat: your kernel must be > > compiled with reiserfs included (not a module). Then even /boot can be > > reiserfs. > > I've run into a problem with a new hard drive and a ReiserFS installed on > it. My current suspicion is that the BIOS must also accept/handle the > ReiserFS for it to be able to boot from a drive formatted in that manner. > > My reason for assuming this is that I have installed SuSE 7.2 Pro on a new > hard drive, and the Bios tells me there is an Hard Drive Failure if I try to > boot from it. But if I boot from CD or floppy I can not only see that > installation, but access it, as well. No. But you might not have the correct partition marked active. The partition with the kernel images (/boot) gets marked active, not the / partition if /boot is separate. Also, I've seen this on Compaqs if the Compaq doesn't see a DOS partition with Compaq utilities. > > Does anyone know if this is the case? Or a way to circumvent this problem > if so? > > I haven't found a BIOS update that mentions file system type. I am > reluctant to re-install (for the third time) if this won't fix the problem. not the fix. > Ciao, David A. Bandel -- Focus on the dream, not the competition. -- Nemesis Racing Team motto ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Thursday 19 July 2001 14:49, Condon Thomas A KPWA wrote: > > From: David A. Bandel [mailto:[EMAIL PROTECTED]] > > > > > Does Reiser FS work for / partitions? > > > > reiserfs will work on any partition -- caveat: your kernel must be > > compiled with reiserfs included (not a module). Then even /boot can be > > reiserfs. > > I've run into a problem with a new hard drive and a ReiserFS installed on > it. My current suspicion is that the BIOS must also accept/handle the > ReiserFS for it to be able to boot from a drive formatted in that manner. > > My reason for assuming this is that I have installed SuSE 7.2 Pro on a new > hard drive, and the Bios tells me there is an Hard Drive Failure if I try > to boot from it. But if I boot from CD or floppy I can not only see that > installation, but access it, as well. > > Does anyone know if this is the case? Or a way to circumvent this problem > if so? > > I haven't found a BIOS update that mentions file system type. I am > reluctant to re-install (for the third time) if this won't fix the problem. > > >In Harmony's Way, and In A Chord, You're barking up the wrong tree. No BIOS would know anything about a linux file system. Did you make your /boot filesystem reiserfs? or is /boot on the reiserfs of '/'? My suspicion is that whatever you are using for boot (grub or lilo) can't read your kernel from a reiserfs partition, but I might be wrong on that. ++ + Bruce S. Marshall [EMAIL PROTECTED] Bellaire, MI 07/19/01 15:30 + ++ "I disagree with what you say, but will defend to the death your right to tell such LIES!" ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
RE: Reiser FS
> > My reason for assuming this is that I have installed SuSE > 7.2 Pro on a new > > hard drive, and the Bios tells me there is an Hard Drive > Failure if I try > > to boot from it. But if I boot from CD or floppy I can not > only see that > > installation, but access it, as well. > Did you make your /boot filesystem reiserfs? or is /boot on > the reiserfs of > '/'? /boot is reiserfs (.5 GB) / is reiserfs (7.5 GB) /home is reiserfs (2 GB) It is a new SuSE 7.2 installation with YaST on a new EIDE hard drive (Western Digital 10GB). My assumption is that YaST, in performing the installation and partitioning of the disk, would have taken care of LILO and the MBR. Perhaps that is not a correct assumption. > My suspicion is that whatever you are using for boot (grub > or lilo) can't > read your kernel from a reiserfs partition, but I might be > wrong on that. LILO. (I guess). Since it doesn't get that far (the boot loader prompt) before the "Hard Drive Error" message, I thought it would be BIOS, not boot loader. So, if I must do an FDISK, is that a Linux utility, or just DOS? I don't happen to have a submarine disk (DOS BOOT). Is there a SxS that I haven't found yet on a Linux version? In Harmony's Way, and In A Chord, Tom :-}) +--+ | Thomas A. Condonemail: [EMAIL PROTECTED] | | Computer Engineer phone: (360) 315-7609| | Barbershop Bass SingerSailor and Singer of Chanties | | Left Handed and In My Right Mind | | "If you want to know what God thinks about money, just | | look at the people He gives it to." -- Old Irish Saying | +--+ ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Thursday 19 July 2001 16:49, Condon Thomas A KPWA wrote: > > > My reason for assuming this is that I have installed SuSE > > > > 7.2 Pro on a new > > > > > hard drive, and the Bios tells me there is an Hard Drive > > > > Failure if I try > > > > > to boot from it. But if I boot from CD or floppy I can not > > > > only see that > > > > > installation, but access it, as well. > > > > Did you make your /boot filesystem reiserfs? or is /boot on > > the reiserfs of > > '/'? Are you able to boot into the system with the 7.2 boot floppy? If I had this problem, I would create another partition (ext2 and a LOT smaller than .5 GB) and I would copy all the /boot files over to it. But since you seem to be without the tools to play with partitions, I'm not sure what you do other than a new install. Many systems have an fdisk, including DOS and Linux. -- ++ + Bruce S. Marshall [EMAIL PROTECTED] Bellaire, MI 07/19/01 18:13 + ++ "He who steps on others to reach the top has good balance." ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Thursday 19 July 2001 02:10 pm, you wrote: > I think that your hypothesis is flawed. No BIOS has the ability to > understand filesystems. It sees raw hardware. Its quite possible that > the MBR of that drive is corrupted, which is making it appear as if > there is no bootable OS on the drive. > > --- Condon Thomas A KPWA <[EMAIL PROTECTED]> wrote: > > > From: David A. Bandel [mailto:[EMAIL PROTECTED]] > > > > > > > Does Reiser FS work for / partitions? > > > > > > reiserfs will work on any partition -- caveat: your kernel must be > > > compiled with reiserfs included (not a module). Then even /boot can > > > > be > > > > > reiserfs. > > > > I've run into a problem with a new hard drive and a ReiserFS installed > > on > > it. My current suspicion is that the BIOS must also accept/handle the > > ReiserFS for it to be able to boot from a drive formatted in that > > manner. > > > > My reason for assuming this is that I have installed SuSE 7.2 Pro on a > > new > > hard drive, and the Bios tells me there is an Hard Drive Failure if I > > try to > > boot from it. But if I boot from CD or floppy I can not only see that > > installation, but access it, as well. > > > > Does anyone know if this is the case? Or a way to circumvent this > > problem > > if so? > > > > I haven't found a BIOS update that mentions file system type. I am > > reluctant to re-install (for the third time) if this won't fix the > > problem. > > = > > Lonni J. Friedman [EMAIL PROTECTED] > > Linux FAQ & Step-by-step help:http://netllama.ipfox.com > Lonnie is correct here. Try fdisk /mbr, then you make have to reinstall. But try it with out reinstall or with recue disk first. I have had to on a used disk & new disk just completely clean the whole thing and start fresh. No partitions & a fdisk /mbr. You can use a newer version of dos to do it if you like -- Rick Sivernell Dallas, Texas 75287 972 306-2296 [EMAIL PROTECTED] Caldera Open Linux eWorkStation 3.1 Registered Linux User .~. / v \ /( _ )\ ^ ^ In Linux we trust! ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Friday 20 July 2001 03:40, David A. Bandel wrote: > No need to change the kernel, I just pick the distro I want to boot to > by name, and the root = /dev/hdXX line changes. I even use the same vga > = 792 line in all of them. Skeleton looks like this: > > my lilo.conf (last image deleted, you get the idea, /boot is on > /dev/hda1 which is marked active partition): [snip] thought that's what you meant. I like it. I imagine the vga= lines (eg) _could_ be a single statement outside of the blocks. I'm gonna experiment. Presumubaly you also have a single 'test' image for the times when you upgrade the kernel, and you pick a single distro to do that. >boot partition is read only belaboring the pont somewhat, I'd either create yet-another-partition for the modules, or, I would symlink to a chosen, automounted, distro. The idea of copying modules/blob/* to each distro isn't elegant and layered with errors. Then again, because of the way you've setup, i'd be inclined to create a single /usr/src/ partition _specifically_ because everything in that tree would be distro agnostic (not just the linux kernel) Just sharing ideas here, not having an argument. > I share /boot and /home how 'sensitive' have you found the home directories to distro-specific issues? I know Caldera as a for instance (used to) rely heavily on the bashxxx scripts in the users home folder. I can see problems arising from say e2.4 kde kmail vs Rh or w3.1 kmail where the config files have the same name but structure has altered Do you strike these gotcha's often? One thing for sure, with the 'discipline' required to maintain a common home partition, it would make installing a new distro much cleaner with a lot less post install work. -- http://linux.nf -- [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Friday 20 July 2001 06:19, Condon Thomas A KPWA wrote: > My reason for assuming this is that I have installed SuSE 7.2 Pro on a new > hard drive, and the Bios tells me there is an Hard Drive Failure if I try > to boot from it. But if I boot from CD or floppy I can not only see that > installation, but access it, as well. this smacks of the 8gig limit. Is your motherboard cabable? What boot manager is causing bios to report an error? Is lilo the later version? A quick check incidentally of discovering bios incompatibilties is to install windoze. The cmos CAN dsicover the real size of the drive, but if the bios cannot use ead, then windoze will limit that drive to 8gig no matter what. -- http://linux.nf -- [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
RE: Reiser FS
I found when installing Suse 7.2 pro on my laptop and configured much the same way (reiser for /, /boot, /home, everything) that it worked fine for IDE disks, but if /boot was Reiser on a SCSI you had to load teh ReiserFS as a module and boot using initrd. Unless I'm TOTALLY confused, and have probably totally confused you all! Mike > > My reason for assuming this is that I have installed SuSE > 7.2 Pro on a new > > hard drive, and the Bios tells me there is an Hard Drive > Failure if I try > > to boot from it. But if I boot from CD or floppy I can not > only see that > > installation, but access it, as well. > Did you make your /boot filesystem reiserfs? or is /boot on > the reiserfs of > '/'? >/boot is reiserfs (.5 GB) >/ is reiserfs (7.5 GB) >/home is reiserfs (2 GB) >It is a new SuSE 7.2 installation with YaST on a new EIDE hard drive >(Western Digital 10GB). My assumption is that YaST, in performing the >installation and partitioning of the disk, would have taken care of LILO and >the MBR. Perhaps that is not a correct assumption. > My suspicion is that whatever you are using for boot (grub > or lilo) can't > read your kernel from a reiserfs partition, but I might be > wrong on that. >LILO. (I guess). Since it doesn't get that far (the boot loader prompt) >before the "Hard Drive Error" message, I thought it would be BIOS, not boot >loader. >So, if I must do an FDISK, is that a Linux utility, or just DOS? I don't >happen to have a submarine disk (DOS BOOT). Is there a SxS that I haven't >found yet on a Linux version? -- Michael W. Holdeman Linux User #191066 Powered by Caldera eDesktop 2.4 Linux Linux Kernel 2.4.5 Windows apps. thanks to Win4Lin3.0 ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Fri, Jul 20, 2001 at 10:59:56AM -0400, Michael W. Holdeman wrote: > >I found when installing Suse 7.2 pro on my laptop and configured much the >same way (reiser for /, /boot, /home, everything) that it worked fine for IDE >disks, but if /boot was Reiser on a SCSI you had to load teh ReiserFS as a >module and boot using initrd. It's been my experience that any modular SCSI kernel requires initrd. Requiring the reiserfs module makes sense, but may not have been the killer. Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC UUCP: camco!bill PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 URL: http://www.celestial.com/ ``A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects.'' Robert Heinlein ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
RE: Reiser FS
Mike, > this smacks of the 8gig limit. Is your motherboard cabable? > What boot manager > is causing bios to report an error? Is lilo the later version? I never get to the LILO loader -- the "Primary Master Hard Disk Fail" message comes first. This is just after the "Bios Successfully Installed" message. It occurs even when I'm booting from a floppy (which is the first boot device). > A quick check incidentally of discovering bios > incompatibilties is to install > windoze. The cmos CAN dsicover the real size of the drive, > but if the bios > cannot use ead, then windoze will limit that drive to 8gig no > matter what. Installing Windoz is the "quick" test? I've never found that to be less than a 4 hour job. Of course, the only M$ OS I have available is NT 4.0 (workstation or server), and I scraped that off to run a decent OS some time ago. I'd prefer a simpler way to test it. Incidentally, it strikes me as counter-productive for Linux users to decry the nasty folks at M$ while expecting to find and use M$ and DOS tools to fix/run our systems. Hmm. Maybe we need more tools of our own. Last night's results: Linux fdisk does not have a /mbr option. I suspect that is dos. I couldn't find anything in man of fdisk on how to write the mbr, so in ran YaST2 (since I'd booted SuSE with the floppy). In Yast I found where to write LILO to the MBR, and did so. Rebooting showed no change to the situation. I suspect you are right about the 8GB limit, so I'll look into that in toady's reading. Debugging the home system from tips I pick up in spare time at work is difficult. Thanks to all for suggestions so far. Tom ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
RE: Reiser FS
Do you have a 2nd box to throw this harddrive into? That would make this process infinitely easier to troubleshoot. --- Condon Thomas A KPWA <[EMAIL PROTECTED]> wrote: > > this smacks of the 8gig limit. Is your motherboard cabable? > > What boot manager > > is causing bios to report an error? Is lilo the later version? > > I never get to the LILO loader -- the "Primary Master Hard Disk Fail" > message comes first. This is just after the "Bios Successfully > Installed" > message. It occurs even when I'm booting from a floppy (which is the > first > boot device). > > > A quick check incidentally of discovering bios > > incompatibilties is to install > > windoze. The cmos CAN dsicover the real size of the drive, > > but if the bios > > cannot use ead, then windoze will limit that drive to 8gig no > > matter what. > > Installing Windoz is the "quick" test? I've never found that to be > less > than a 4 hour job. Of course, the only M$ OS I have available is NT > 4.0 > (workstation or server), and I scraped that off to run a decent OS > some time > ago. I'd prefer a simpler way to test it. > > Incidentally, it strikes me as counter-productive for Linux users to > decry > the nasty folks at M$ while expecting to find and use M$ and DOS tools > to > fix/run our systems. Hmm. Maybe we need more tools of our own. > > Last night's results: > Linux fdisk does not have a /mbr option. I suspect that is dos. I > couldn't > find anything in man of fdisk on how to write the mbr, so in ran YaST2 > (since I'd booted SuSE with the floppy). In Yast I found where to > write > LILO to the MBR, and did so. Rebooting showed no change to the > situation. > > I suspect you are right about the 8GB limit, so I'll look into that in > toady's reading. Debugging the home system from tips I pick up in > spare > time at work is difficult. = Lonni J. Friedman [EMAIL PROTECTED] Linux FAQ & Step-by-step help:http://netllama.ipfox.com . __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
RE: Reiser FS
> Do you have a 2nd box to throw this hard drive into? That would make > this process infinitely easier to troubleshoot. Not working at home. That was the eventual destination of this hard drive. I suppose I could bring it to work and plug it into my W2K machine and do a low level format with MBR. I have the parts for a second box at home, and I have another hard drive (arrived yesterday) that I could try instead. The new hard drive will also suffer from the 8GB limit (it is 20) and the older box would have an older BIOS, so I'd have to work around that. Tom ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
Mike Andrew wrote: > > On Friday 20 July 2001 03:40, David A. Bandel wrote: > > No need to change the kernel, I just pick the distro I want to boot to > > by name, and the root = /dev/hdXX line changes. I even use the same vga > > = 792 line in all of them. Skeleton looks like this: > > > > my lilo.conf (last image deleted, you get the idea, /boot is on > > /dev/hda1 which is marked active partition): > > [snip] > > thought that's what you meant. I like it. I imagine the vga= lines (eg) > _could_ be a single statement outside of the blocks. I'm gonna experiment. yes, it can be in the global section. And of course you can change it on the command line. > > Presumubaly you also have a single 'test' image for the times when you > upgrade the kernel, and you pick a single distro to do that. well of course. I always have a way to get back to where I was. Needed to with 2.4.6, which won't boot on any of my systems. Fails spectacularly (kernel panics) at different places. > > >boot partition is read only > > belaboring the pont somewhat, I'd either create yet-another-partition for the > modules, or, I would symlink to a chosen, automounted, distro. The idea of > copying modules/blob/* to each distro isn't elegant and layered with errors. > Then again, because of the way you've setup, i'd be inclined to create a > single /usr/src/ partition _specifically_ because everything in that tree > would be distro agnostic (not just the linux kernel) I could, I just don't want to. And a quick mount and cp -a takes care of it. Not like there's a lot there. True about /usr/src, again, just not something I've thought too hard about (so haven't done). Then I could build a kernel and just run make modules_install in each distro. > > Just sharing ideas here, not having an argument. I'm sure there's a better way, I just haven't bothered to think about it further. > > > I share /boot and /home > > how 'sensitive' have you found the home directories to distro-specific > issues? I know Caldera as a for instance (used to) rely heavily on the > bashxxx scripts in the users home folder. I can see problems arising from say > e2.4 kde kmail vs Rh or w3.1 kmail where the config files have the same name > but structure has altered Do you strike these gotcha's often? Haven't run into any problem yet. > > One thing for sure, with the 'discipline' required to maintain a common home > partition, it would make installing a new distro much cleaner with a lot less > post install work. > Yep. I just copy /etc/passwd, shadow, and group to each /etc and all's well. Ciao, David A. Bandel -- Focus on the dream, not the competition. -- Nemesis Racing Team motto ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
RE: Reiser FS
--- Condon Thomas A KPWA <[EMAIL PROTECTED]> wrote: > > > Do you have a 2nd box to throw this hard drive into? That would > make > > this process infinitely easier to troubleshoot. > > Not working at home. That was the eventual destination of this hard > drive. > I suppose I could bring it to work and plug it into my W2K machine and > do a > low level format with MBR. Errr...that's not my definition of troubleshooting. Have you tried resetting the BIOS to defaults? Is the drive even getting recognized in the BIOS? = Lonni J. Friedman [EMAIL PROTECTED] Linux FAQ & Step-by-step help:http://netllama.ipfox.com . __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Saturday 21 July 2001 04:01, Condon Thomas A KPWA wrote: > I never get to the LILO loader -- the "Primary Master Hard Disk Fail" > message comes first. This is just after the "Bios Successfully Installed" > message. It occurs even when I'm booting from a floppy (which is the first > boot device). I don't follow why you get a 'successfully installed bios'? Who or what is *installing* a bios? Have you a scsi card playing in here? "primary master hard disk fail" is strictly a hardware / motherboard issue, It is NOT bootware related. You have some sort of hardware conflict with this 'new' drive. Eg two drives are masters, or some such. Check your drive selections CS / MA / SL on each drive that's on the same cable. You have an old sblaster card with it's ide set to the wrong address, you have a udma66 controller in addition to motherboard, etc etc. This is hardware conflict. -- http://linux.nf -- [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
Condon Thomas A KPWA wrote: > > Mike, > > > this smacks of the 8gig limit. Is your motherboard cabable? > > What boot manager > > is causing bios to report an error? Is lilo the later version? > > I never get to the LILO loader -- the "Primary Master Hard Disk Fail" > message comes first. This is just after the "Bios Successfully Installed" > message. It occurs even when I'm booting from a floppy (which is the first > boot device). > Sorry I missed the earlier part of the thread. If these are SCSI disks (you ARE using a SCSI card to get the bios message?) have you tried Ctrl-A to check your SCSI setup for misconfiguration, e.g. not set to be bootable, etc? -- Andrew Mathews 5:55pm up 15 days, 21:18, 5 users, load average: 1.00, 1.02, 1.01 Do you guys know what you're doing, or are you just hacking? ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Fri, 20 Jul 2001 09:28:33 -0700, Bill Campbell wrote: >It's been my experience that any modular SCSI kernel requires >initrd. Requiring the reiserfs module makes sense, but may not >have been the killer. So if this is the case, then I would need to create a new initrd for 2.4.6 if I were to compile one? If so, how do you go about creating the new initrd from the 2.4.6 source? I guess a trip to the Steps is in order stayler ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
There is a tool that will blow away your mbr, dd dd if=/dev/zero of=/dev/[device-node] bs=512k count=1 Im not sure what fdisk /mbr does, but you can take a look using hexdump -c on the drive before and after so you can get a feel for what it does.. HTH- Jim > Incidentally, it strikes me as counter-productive for Linux users to decry > the nasty folks at M$ while expecting to find and use M$ and DOS tools to > fix/run our systems. Hmm. Maybe we need more tools of our own. > > Last night's results: > Linux fdisk does not have a /mbr option. I suspect that is dos. I > couldn't find anything in man of fdisk on how to write the mbr, so in ran > YaST2 (since I'd booted SuSE with the floppy). In Yast I found where to > write LILO to the MBR, and did so. Rebooting showed no change to the > situation. -- 1:05pm up 10 days, 22:52, 6 users, load average: 1.20, 1.12, 1.12 UNIX...because life is too short for reboots... ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
--- Shawn Tayler <[EMAIL PROTECTED]> wrote: > On Fri, 20 Jul 2001 09:28:33 -0700, Bill Campbell wrote: > > >It's been my experience that any modular SCSI kernel requires > >initrd. Requiring the reiserfs module makes sense, but may not > >have been the killer. > > So if this is the case, then I would need to create a new initrd for > 2.4.6 if I were to compile one? If so, how do you go about creating > the new initrd from the 2.4.6 source? I guess a trip to the Steps is > in order NOt true. THe option is either to create an initrd *OR* to compile the support into the kernel. __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Fri, Jul 20, 2001 at 01:20:09PM -0700, Jim Bonnet wrote: > There is a tool that will blow away your mbr, dd > > dd if=/dev/zero of=/dev/[device-node] bs=512k count=1 > > Im not sure what fdisk /mbr does, but you can take a look using hexdump -c on > the drive before and after so you can get a feel for what it does.. fdisk /mbr replaces the active boot sector with a backup copy. ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
uh, a backup copy of what? If you are running linux/unix how is fdisk /mbr going to provide a backup copy? It must copy those bytes from somewhere that windows likes.. Does grub/lilo install a backup copy of the mbr in the same place as windoze? Jim On Saturday 21 July 2001 10:58, you wrote: > On Fri, Jul 20, 2001 at 01:20:09PM -0700, Jim Bonnet wrote: > > There is a tool that will blow away your mbr, dd > > > > dd if=/dev/zero of=/dev/[device-node] bs=512k count=1 > > > > Im not sure what fdisk /mbr does, but you can take a look using hexdump > > -c on the drive before and after so you can get a feel for what it does.. > > fdisk /mbr replaces the active boot sector with a backup copy. > > ___ > http://linux.nf -- [EMAIL PROTECTED] > Archives, Subscribe, Unsubscribe, Digest, Etc > ->http://linux.nf/mailman/listinfo/linux-users -- 6:35am up 13 days, 16:21, 4 users, load average: 1.01, 1.05, 1.02 UNIX...because life is too short for reboots... ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Mon, Jul 23, 2001 at 06:41:37AM -0700, Jim Bonnet wrote: > uh, a backup copy of what? If you are running linux/unix how is fdisk /mbr > going to provide a backup copy? It must copy those bytes from somewhere that > windows likes.. Sorry. A backup copy of the boot sector. fdisk /mbr is DOS/Windows only. > Does grub/lilo install a backup copy of the mbr in the same place as windoze? Not in the same place. LILO does provide a restore option, but the command line option for restoring the original boot sector using LILO escapes me just now. K ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Reiser FS
On Mon, 23 Jul 2001 06:41:37 -0700 Lourens said the following to Jim Bonnet: lilo -u /dev/hda [snip] " uh, a backup copy of what? If you are running linux/unix how is fdisk /mbr " going to provide a backup copy? It must copy those bytes from somewhere that " windows likes.. " " Does grub/lilo install a backup copy of the mbr in the same place as windoze? [end snip] *** Powered by SuSE Linux 7.2 Professional Registered Linux User Lourens Steenkamp Republic of South Africa _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Fwd: Re: Reiser FS
On Fri, 20 Jul 2001 09:28:33 -0700, Bill Campbell wrote: >It's been my experience that any modular SCSI kernel requires >initrd. Requiring the reiserfs module makes sense, but may not >have been the killer. So if this is the case, then I would need to create a new initrd for 2.4.6 if I were to compile one? If so, how do you go about creating the new initrd from the 2.4.6 source? I guess a trip to the Steps is in order stayler ===END FORWARDED MESSAGE=== ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: Fwd: Re: Reiser FS
On Fri, Jul 20, 2001 at 09:08:23PM -0700, Shawn Tayler wrote: >On Fri, 20 Jul 2001 09:28:33 -0700, Bill Campbell wrote: > >>It's been my experience that any modular SCSI kernel requires >>initrd. Requiring the reiserfs module makes sense, but may not >>have been the killer. > >So if this is the case, then I would need to create a new initrd for >2.4.6 if I were to compile one? If so, how do you go about creating >the new initrd from the 2.4.6 source? I guess a trip to the Steps is >in order On caldera systems, use /usr/libexec/modules/mkinitrd.sh which is part of the modutils RPM. It should determine which modules are necessary to boot, and build the appropriate initrd files in your current directory. >stayler > > > >===END FORWARDED MESSAGE=== > > >___ >http://linux.nf -- [EMAIL PROTECTED] >Archives, Subscribe, Unsubscribe, Digest, Etc >->http://linux.nf/mailman/listinfo/linux-users > -- Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC UUCP: camco!bill PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 URL: http://www.celestial.com/ ``Most people, sometime in their lives, stumble across truth. Most jump up, brush themselves off, and hurry on about their business as if nothing had happened.'' - Sir Winston Churchill ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
