Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
04-05-2006, 11:54 AM
|
#1
|
Member
Registered: Aug 2005
Distribution: Ubuntu 7.10, Slackware 12
Posts: 270
Rep:
|
One NTFS partition has errors, the other wont mount.
Hi all, i gave partition doctor a try on xp (dual booting) to try to get rid of some errors and to make the z:\ drive in windows (hdc i think in slackware) mount to /ntfs-z, but im not too sure what needs to be changed.
EDIT: i forgot the sata drive needs to be called sda so changed it in fstab to
Code:
/dev/sda /ntfs-z ntfs ro,users 1 0
these are the errors:
Code:
NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: ST340810A, ATA DISK drive
hdb: IC35L120AVV207-0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: DVD-RW IDE1108, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hda: cache flushes not supported
hda: hda1 hda2 hda3 < hda5 >
hdb: max request size: 512KiB
hdb: 241254720 sectors (123522 MB) w/1821KiB Cache, CHS=16383/255/63, UDMA(100)
hdb: cache flushes supported
hdb: hdb1 < hdb5 >
hdc: ATAPI 63X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
libata version 1.20 loaded.
sata_sil 0000:01:0b.0: version 0.9
ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:01:0b.0[A] -> Link [LNK3] -> GSI 11 (level, low) -> IRQ 11
ata1: SATA max UDMA/100 cmd 0xF8802080 ctl 0xF880208A bmdma 0xF8802000 irq 11
ata2: SATA max UDMA/100 cmd 0xF88020C0 ctl 0xF88020CA bmdma 0xF8802008 irq 11
ata1: SATA link up 1.5 Gbps (SStatus 113)
ata1: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3c69 86:3c01 87:4003 88:20ff
ata1: dev 0 ATA-7, max UDMA7, 312581808 sectors: LBA48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: SATA link down (SStatus 0)
scsi1 : sata_sil
Vendor: ATA Model: SAMSUNG SP1614C Rev: SW10
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 6, 262144 bytes)
TCP established hash table entries: 262144 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
Using IPI Shortcut mode
ACPI wakeup devices:
HUB0 HUB1 USB0 USB1 USB2 F139 MMAC MMCI UAR1
ACPI: (supports S0 S1 S4 S5)
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 152k freed
Adding 1301224k swap on /dev/hda5. Priority:-1 extents:1 across:1301224k
EXT3 FS on hda2, internal journal
Linux agpgart interface v0.101 (c) Dave Jones
kjournald starting. Commit interval 5 seconds
EXT3 FS on hdb5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NTFS driver 2.1.26 [Flags: R/W MODULE].
NTFS volume version 3.1.
NTFS-fs warning (device hda1): load_system_files(): Unsupported volume flags 0x4000 encountered.
NTFS-fs warning (device hda1): load_system_files(): Volume has unsupported flags set. Will not be able to remount read-write. Run chkdsk and mount in Windows.
NTFS-fs warning (device sda): is_boot_sector_ntfs(): Invalid boot sector checksum.
NTFS-fs error (device sda): read_ntfs_boot_sector(): Primary boot sector is invalid.
NTFS-fs error (device sda): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
NTFS-fs error (device sda): ntfs_fill_super(): Not an NTFS volume.
Anyone know what im doing wrong?
Last edited by dave`2005; 04-05-2006 at 12:04 PM.
|
|
|
04-05-2006, 01:17 PM
|
#2
|
Member
Registered: Aug 2004
Location: Aguascalientes, AGS. Mexico.
Distribution: Slackware 13.0 kernel 2.6.29.6
Posts: 816
Rep:
|
Quote:
NTFS-fs warning (device sda): is_boot_sector_ntfs(): Invalid boot sector checksum.
NTFS-fs error (device sda): read_ntfs_boot_sector(): Primary boot sector is invalid.
NTFS-fs error (device sda): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
NTFS-fs error (device sda): ntfs_fill_super(): Not an NTFS volume.
|
the entry on the /etc/fstab file is wrong, properly you do not mount the entire drive, only partitions of it. There you are telling it to mount the whole /dev/sda drive, whilst you should specify one partition to mount as like /dev/sda1, /dev/sda2, etc.
you can check how your drive if partitioned with
or more technically
there if you don't say which drive, fdisk shall display all your accessible partitions on all your accessible drives
|
|
|
04-06-2006, 02:52 AM
|
#3
|
Member
Registered: Mar 2006
Distribution: Slackware
Posts: 63
Rep:
|
Quote:
Originally Posted by raska
you can check how your drive if partitioned with
or more technically
there if you don't say which drive, fdisk shall display all your accessible partitions on all your accessible drives
|
Actually he doesn't need that.
This is a snippet from the output of dmesg above
Code:
SCSI device sda: drive cache: write back
sda: sda1
|
|
|
04-06-2006, 10:44 AM
|
#4
|
Member
Registered: Aug 2004
Location: Aguascalientes, AGS. Mexico.
Distribution: Slackware 13.0 kernel 2.6.29.6
Posts: 816
Rep:
|
Quote:
Originally Posted by wchild
Actually he doesn't need that.
This is a snippet from the output of dmesg above
Code:
SCSI device sda: drive cache: write back
sda: sda1
|
ouch that's true! I didn't noticed, my mistake
|
|
|
All times are GMT -5. The time now is 11:58 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|