Guest Owdy Posted September 1, 2004 Report Share Posted September 1, 2004 Starting mandrake10 takes 5-10 minutes. Boot hangs in this for minutes: Aug 29 10:17:11 localhost kernel: hdc: DMA timeout errorAug 29 10:17:11 localhost kernel: hdc: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest } Aug 29 10:17:11 localhost kernel: Aug 29 10:17:11 localhost kernel: NTFS volume version 3.1. Aug 29 10:17:11 localhost kernel: NTFS volume version 3.1. Aug 29 10:17:11 localhost kernel: NTFS-fs error: find_attr(): Inode is corrupt. Run chkdsk. Aug 29 10:17:11 localhost kernel: NTFS-fs error (device hdc5): ntfs_read_locked_inode(): $STANDARD_INFORMATION attribute is missing. Aug 29 10:17:11 localhost kernel: NTFS-fs error (device hdc5): ntfs_read_locked_inode(): Failed with error code 5. Marking inode 0xa as bad. Aug 29 10:17:11 localhost kernel: NTFS-fs error (device hdc5): load_and_init_upcase(): Failed to load $UpCase from the volu me. Using default. Aug 29 10:17:11 localhost kernel: NTFS volume version 3.1. Aug 29 10:17:11 localhost kernel: NTFS-fs error (device hdc5): ntfs_read_locked_inode(): Inode is not in use! You should ru n chkdsk. Aug 29 10:17:11 localhost kernel: NTFS-fs error (device hdc5): ntfs_read_locked_inode(): Failed with error code 5. Marking inode 0xb as bad. Aug 29 10:17:11 localhost kernel: NTFS-fs error (device hdc5): load_system_files(): Failed to load $Extend. Aug 29 10:17:11 localhost kernel: NTFS-fs error (device hdc5): ntfs_fill_super(): Failed to load system file And this: Aug 29 10:17:13 localhost kernel: NTFS-fs error: find_attr(): Inode iscorrupt. Run chkdsk. Aug 29 10:17:13 localhost kernel: NTFS-fs error (device hdc5): ntfs_read_locked_inode(): $STANDARD_INFORMATION attribute is missing. Aug 29 10:17:13 localhost kernel: NTFS-fs error (device hdc5): ntfs_read_locked_inode(): Failed with error code 5. Marking inode 0xa as bad. Aug 29 10:17:13 localhost kernel: NTFS-fs error (device hdc5): load_and_init_upcase(): Failed to load $UpCase from the volume. Using default. Aug 29 10:17:13 localhost kernel: NTFS volume version 3.1. Aug 29 10:17:13 localhost kernel: NTFS-fs error (device hdc5): ntfs_read_locked_inode(): Inode is not in use! You should run chkdsk. Aug 29 10:17:13 localhost kernel: NTFS-fs error (device hdc5): ntfs_read_locked_inode(): Failed with error code 5. Marking inode 0xb as bad. Aug 29 10:17:13 localhost kernel: NTFS-fs error (device hdc5): load_system_files(): Failed to load $Extend. Aug 29 10:17:13 localhost kernel: NTFS-fs error (device hdc5): ntfs_fill_super(): Failed to load system files. Aug 29 10:17:13 localhost mount: mount: wrong fs type, bad option, bad superblock on /dev/hdc5, Aug 29 10:17:13 localhost mount: or too many mounted file systems Aug 29 10:17:13 localhost xfs: ignoring font path element I have run chkdsk for all windows partions, no errors. Ideas? Quote Link to comment Share on other sites More sharing options...
devries Posted September 1, 2004 Report Share Posted September 1, 2004 (edited) Try booting with 'linux nodma' (what i found after some googling) Good luck Edited September 1, 2004 by devries Quote Link to comment Share on other sites More sharing options...
Cannonfodder Posted September 2, 2004 Report Share Posted September 2, 2004 You may also want to examine your /etc/fstab file. This file contains a list of all mounted partitions and their file system types. Maybe some partition got shifted and its now attempting to load a NTFS file system from a linux partitions or something like that.. Run diskdrake to get a visual display of your partition layout.. Quote Link to comment Share on other sites More sharing options...
Guest Owdy Posted September 2, 2004 Report Share Posted September 2, 2004 You may also want to examine your /etc/fstab file. This file contains a list of all mounted partitions and their file system types. Maybe some p /dev/hda5 / ext3 defaults 1 1none /dev/pts devpts mode=0620 0 0 /dev/hda8 /home ext3 defaults 1 2 /dev/hdb /mnt/cdrom auto umask=0,user,iocharset=iso8859-15,codepage=850,noauto,ro,exec 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-15,sync,codepage=850 0 0 /dev/hda1 /mnt/win_c ntfs umask=0,nls=iso8859-15,ro 0 0 /dev/hdc1 /mnt/win_c2 ntfs umask=0,nls=iso8859-15,ro 0 0 /dev/hda6 /mnt/win_d ntfs umask=0,nls=iso8859-15,ro 0 0 /dev/hdc5 /mnt/win_d2 ntfs umask=0,nls=iso8859-15,ro 0 0 none /proc proc defaults 0 0 /dev/hda7 swap swap defaults 0 0 That isnt telling anything. Im totally n00b with linux. :unsure: Quote Link to comment Share on other sites More sharing options...
Cannonfodder Posted September 3, 2004 Report Share Posted September 3, 2004 Well, each entry is used by linux to load a file system. It defines the partition location, the type of file system (ext3, ntfs, reiserfs, etc) and additional parameter information such as permissions. Remember, you can google this board and of course google.com for terms such as partitioning and fstab and learn rapidly. So look at win_d2. Located at hdc5 and mounted into the file system at location /mnt/win_d2 (this is a actually a folder) as an NTFS file system. The IDE controller board in your computer supports 2 IDE devices (hard drive, cd writer, whatever) each. So, the first board's devices are going to be HDA and HDB. If you have a second IDE board, those devices are going to be HDC and HDD (or some variant based on the device). The question is what would happen if fstab thinks hdc5 is NTFS, but in actuality it is ext3 (linux file system)? It's gonna have an issue because it tries to mount it with the NTFS keyword and logic. If you have linux up and running, you can open a command terminal and type diskdrake or, if you don't have it up and running, you can start up your PC with the Mandrake Install CD. Do an install and when you get to the partitioning screen, you can select CUSTOM install. Now you should be looking at a visual image of your hard drive(s). Compare the file system types to what your fstab file states and make sure they match. Quote Link to comment Share on other sites More sharing options...
Guest Owdy Posted September 3, 2004 Report Share Posted September 3, 2004 If you have linux up and running, you can open a command terminal and type diskdrake bash: diskdrake: command not found Quote Link to comment Share on other sites More sharing options...
Guest Owdy Posted September 3, 2004 Report Share Posted September 3, 2004 The question is what would happen if fstab thinks hdc5 is NTFS, but in actuality it is ext3 (linux file system)? It's gonna have an issue because it tries to mount it with the NTFS keyword and logic. Those seems to be in right order Quote Link to comment Share on other sites More sharing options...
spinynorman Posted September 3, 2004 Report Share Posted September 3, 2004 bash: diskdrake: command not found Owdy - just for future reference, you have to be root to run diskdrake. su [root password] diskdrake :) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.