Re: [SLE] 7.2 install woes...more errors than you can shake a stick at
Hi Thanks everyone, I am getting somewhere now. But I have still have not solved these two errors. The machine has been up six hours and I have 70,000 lines of this in /var/log/messages. Directory sread (sector 0x14eff37) failed attempt to access beyond end of device 03:01: rw=0, want=10977180, limit=7341673 Directory sread (sector 0x14eff37) failed attempt to access beyond end of device 03:01: rw=0, want=10977180, limit=7341673 Directory sread (sector 0x14eff37) failed The partitions used seem fine, lots of space left over. I thought at first it might be a problem accessing the DVD during install, but now the majority of these messages have been added after install without using the DVD, so I guess the device mentioned must be the hard disk? Also, when YaST2 runs SuSEconfig after installing packages it shows grep: writing output: Broken pipe many times when switching to a text console [ctrl]+[atl] then [atl] + F4 Is my hard disk the problem, or is it SuSE 7.2 DVD, anybody else have these messages? I do not want to re-install just yet, it took 6 hours to get this far. I assume if YaST2 is dodgy and I need to install with YaST1 that I have to use the CDroms? Oh, something completely different, I do not get any sound running Xawtv, picture is fine. I tried KwinTV too but that just crashes. Rich
-- Powered by SuSE Linux Richie Rich
Hi all I think I have discovered my problem. Can you have resierfs on all partitions? I have all, but the /boot (ext2) partition running resierfs. I think I heard somewhere / needs to be an ext2 partition. Is that correct? What partitions have others used resierfs on? Thanks Rich --- On Tuesday 28 August 2001 17:28, Richard Booth wrote:
-- Powered by SuSE Linux Richie Rich
At 05:47 PM 8/28/2001 +0000, Richard Booth wrote:
Onlhy the /boot partition needs to be ext2. I have all my other partitions as resierfs. If you have the / partition an boot from it then it has to be ext2, but only if your booting from the / partition. jack malone Network Administrator EAST TEXAS LIGHTHOUSE FOR THE BLIND dba HORIZON INDUSTRIES 903-595-3444 http://www.horizonind.com
I have discovered why the messages occur, it is a dodgy FAT partition that causes these errors. Not figured out the grep: writing output: Broken pipe when YaST runs SuSEconfig though. Rich
-- Powered by SuSE Linux Richie Rich
I recently installed SuSE 7.2 without creating a separate /boot filesystem. There was only root and this was configured to be a reiser fs. No problems have I encountered. Maybe this is because I boot Linux from the discs MBR? (ie. root is NOT above 1024 boundary?). Whatever, check out www.namesys.com. I noted in the FAQ that it is recommended that /boot be mounted with -notail option. What is this? Kind regards, Simon Richard Booth wrote:
At 17:28 28/08/2001 +0000, Richard Booth wrote:
I suspect the disk was 'fdisk'ed with DOS/Win9x fdisk, which incorrectly partitions beyond the end of the physical disk. With some drives, this can result in damage to the disk. This is often a problem which crops up with dual-boot machines, initially installed with Win9x. The only solution I know of is to clear all existing partitions and start again (complaints to Bill Gates please!) If anyone has a solution which allows the existing installation to be retained, please let us all know. Brgds, Tony
participants (4)
-
Jack Malone
-
Richard Booth
-
Simon Heaton
-
Tony White