HDD errors & KDE not starting.

dave`2005 · 04-03-2006, 09:54 PM

Hi all, after trying to get slackware to see a drive being 115gb instead of it coming up as 22gb i took the advice of trying "fdisk /dev/hdb" to no avail. I thought ok, i'll try again later.

I got the kde 3.5.2 .tgz's and upgraded (not sure if this is what did it), logged out of kde then back in, things seemed fine. I then rebooted, and got:

Code:

    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:
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 979924k swap on /dev/hda5.  Priority:-1 extents:1 across:979924k
EXT3 FS on hda2, internal journal
Linux agpgart interface v0.101 (c) Dave Jones
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 error (device hda1): load_system_files(): Volume has unsupported flags set.  Mounting read-only.  Run chkdsk and mount in Windows.
NTFS volume version 3.1.
NTFS-fs error (device sda1): load_system_files(): Volume is dirty.  Mounting read-only.  Run chkdsk and mount in Windows.
nvidia: module license 'NVIDIA' taints kernel.

I booted XP and did a chkdsk, rebooted back into slackware and get the same thing.

After seeing that the chkdsk didnt help i went ahead and tried to boot kde anyway, and got:

Code:

There was an error setting up the inter-process communications for kde.  The message returned by the system was: Could not read network connection list.
dl//.DCOPServer_desktop-box__0
Please check that the "DCOPServer" is running!

It stays on the splash screen for a few minutes then the box with that error above is visible (it was behind the splash screen), i click ok and get the prompt back.
If i log in to kde on the root account things are ok :/

What have i done ?

Any help would be very very appreciated.

Alien_Hominid · 04-03-2006, 11:03 PM

Do you have two hard drives?

wchild · 04-04-2006, 01:39 AM

Quote:

Originally Posted by dave`2005

NTFS driver 2.1.26 [Flags: R/W MODULE].

BAD IDEA!
Mount NTFS partitions read-only.

dave`2005 · 04-04-2006, 11:33 AM

I reinstalled Slackware. I have 3 hdds in this desktop pc. About to compile the 2.6.16.1 kernel and will choose the read only ntfs option, and have "ro" in the fstab (not sure which one it is so i'll do both).

However the z drive on xp isnt showing up in Slackware now, i think it was hdc, will double check using the gparted live cd, all i need to do after confirming it as hdc is to add it to fstab right?

Alien_Hominid · 04-04-2006, 11:43 AM

Yes. You can fdisk -l /dev/hdc to check him and then use mount.

igu · 04-04-2006, 11:26 PM

Quote:

Originally Posted by wchild

BAD IDEA!Mount NTFS partitions read-only.

Why? The bad NTFS driver was replaced by a new one in 2002 which is safe to use since then. See more at http://www.linux-ntfs.org

Alien_Hominid · 04-05-2006, 12:09 AM

Thats why:
Still mostly read-only, but with safe file overwrite support on all Windows versions including changes to the file size (uncompressed, unencrypted, non-sparse files only).

wchild · 04-05-2006, 01:40 AM

Quote:

Originally Posted by igu

Why? The bad NTFS driver was replaced by a new one in 2002 which is safe to use since then. See more at http://www.linux-ntfs.org

I'm not going to start a flame war here but this is what I think: the NTFS support for non-Windows OSes is reverse engineering, the specification of the NTFS file system is not disclosed. Nobody expects Microsoft to disclose their code for NTFS. But keeping specification secret is just unfair. If you need write NTFS access, just use Windows.

igu · 04-09-2006, 12:11 PM

Quote:

Originally Posted by Alien_Hominid

Thats why:
Still mostly read-only, but with safe file overwrite support on all Windows versions including changes to the file size (uncompressed, unencrypted, non-sparse files only).

You found the wrong driver. This is how you can have safe read-write NTFS access from Linux: http://wiki.linux-ntfs.org/doku.php?id=ntfsmount

igu · 04-09-2006, 12:44 PM

Quote:

Originally Posted by wchild

the NTFS support for non-Windows OSes is reverse engineering, the specification of the NTFS file system is not disclosed. Nobody expects Microsoft to disclose their code for NTFS. But keeping specification secret is just unfair. If you need write NTFS access, just use Windows.

Thanks but it works fine from Linux too. Of course you can think whatever you want but facing the reality it turns out that your thoughts are nonsense excuses for something that's not a problem ;-)

If you disagree then please describe how you can corrupt an NTFS: use for instance ntfsclone to make an image file of an existing NTFS partition or just mkntfs a file then ntfsmount it (not by the kernel driver, not by Captive NTFS) and try to destroy, trash or corrupt it. I would be highly surprised if you were able to do so, since nobody else can.