Announcement

Collapse
No announcement yet.

problem with ntfs&fat32 partitions

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 5
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 5 template Next
    #46
    Re: problem with ntfs&fat32 partitions

    Your SATA hard drive has an interface chip on it, and your SATA DVD drive also has an interface chip, and they are not necessarily the same. So the driver in Linux may be happy to run the hard drive, but maybe does not recognize the interface on the DVD drive.

    If you can set your BIOS SATA mode to "legacy", it might be OK -- you have to do the experiment to find out.

    EDIT: If it is possible to get a DVD drive with IDE ("PATA") interface, that is more likely to just plug in and work.
    • Top
    • Bottom

    Comment

      #47
      Re: problem with ntfs&fat32 partitions

      Originally posted by dibl
      Your SATA hard drive has an interface chip on it, and your SATA DVD drive also has an interface chip, and they are not necessarily the same. So the driver in Linux may be happy to run the hard drive, but maybe does not recognize the interface on the DVD drive.

      If you can set your BIOS SATA mode to "legacy", it might be OK -- you have to do the experiment to find out.

      EDIT: If it is possible to get a DVD drive with IDE ("PATA") interface, that is more likely to just plug in and work.
      I will se what to do.There is no legacy option in my BIOS settings.
      • Top
      • Bottom

      Comment

        #48
        Re: problem with ntfs&fat32 partitions

        With the SATA drive plugged in, do you see it with
        Code:
        fdisk -l
        ? If you do
        Code:
        kcontrol
        and open the "Drives" item, do you see it? If it doesn't show up in either of those lists, I'm afraid Linux does not recognize that drive, so it's not going to work on your computer.

        EDIT: Is there an "IDE" mode available in your BIOS for the SATA device?
        • Top
        • Bottom

        Comment

          #49
          Re: problem with ntfs&fat32 partitions

          Nothing

          dusan@kubuntu:~$ fdisk -l
          dusan@kubuntu:~$



          I set at BIOS P-ATA + S-ATA but nothing changes.I knew that I should buy with IDE.Can I expect that this problem will be soon fixed.Or what distribution to take where SATA will be fuctioning?
          • Top
          • Bottom

          Comment

            #50
            Re: problem with ntfs&fat32 partitions

            Before you give up, do
            Code:
            sudo apt-get install hwinfo
            then (after it is installed) run
            Code:
            hwinfo
            and see if that drive shows up. Probably it will not.

            The drivers for hard drives and SATA devices are in the Linux kernel, so you would have to find a Linux distro with a kernel that has a driver for whatever controller chip is on that drive. I can't really say whether one exists or which one it would be. :P
            • Top
            • Bottom

            Comment

              #51
              Re: problem with ntfs&fat32 partitions

              Code:
              43: IDE 00.0: 10600 Disk
 [Created at block.222]
 UDI: /org/freedesktop/Hal/devices/storage_serial_1ATA_MAXTOR_4K020H1_571130218
162
 Unique ID: mE25.ajSHNw1M79B
 Parent ID: w7Y8.xJeQ4DgzxT6
 SysFS ID: /block/sda
 SysFS BusID: 0:0:0:0
 SysFS Device Link: /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0
 Hardware Class: disk
 Model: "MAXTOR 4K020H1"
 Vendor: "MAXTOR"
 Device: "4K020H1"
 Revision: "A08."
 Driver: "ata_piix", "sd"
 Driver Modules: "ata_piix"
 Device File: /dev/sda
 Device Files: /dev/sda, /dev/disk/by-id/scsi-1ATA_MAXTOR_4K020H1_571130218162,
 /dev/disk/by-id/ata-MAXTOR_4K020H1_571130218162, /dev/disk/by-path/pci-0000:00:
1f.2-scsi-0:0:0:0
 Device Number: block 8:0-8:15
 BIOS id: 0x80
 Drive status: no medium
 Config Status: cfg=new, avail=yes, need=no, active=unknown
 Attached to: #22 (IDE interface)

44: None 00.0: 11300 Partition
 [Created at block.391]
 UDI: /org/freedesktop/Hal/devices/volume_uuid_BC20449720445B12
 Unique ID: 1tKY.SE1wIdpsiiC
 Parent ID: mE25.ajSHNw1M79B
 SysFS ID: /block/sda/sda1
 Hardware Class: partition
 Model: "Partition"
 Device File: /dev/sda1
 Device Files: /dev/sda1, /dev/disk/by-id/scsi-1ATA_MAXTOR_4K020H1_571130218162
-part1, /dev/disk/by-id/ata-MAXTOR_4K020H1_571130218162-part1, /dev/disk/by-path
/pci-0000:00:1f.2-scsi-0:0:0:0-part1, /dev/disk/by-uuid/BC20449720445B12
 Config Status: cfg=new, avail=yes, need=no, active=unknown
 Attached to: #43 (Disk)

45: IDE 01.0: 10600 Disk
 [Created at block.222]
 UDI: /org/freedesktop/Hal/devices/storage_serial_1ATA_QUANTUM_FIREBALLlct20_20
_752035087817
 Unique ID: DQI9.Zjm32PQro4E
 Parent ID: w7Y8.xJeQ4DgzxT6
 SysFS ID: /block/sdb
 SysFS BusID: 0:0:1:0
 SysFS Device Link: /devices/pci0000:00/0000:00:1f.2/host0/target0:0:1/0:0:1:0
 Hardware Class: disk
 Model: "QUANTUM FIREBALL"
 Vendor: "QUANTUM"
 Device: "FIREBALL"
 Revision: "APL."
 Driver: "ata_piix", "sd"
 Driver Modules: "ata_piix"
 Device File: /dev/sdb
 Device Files: /dev/sdb, /dev/disk/by-id/scsi-1ATA_QUANTUM_FIREBALLlct20_20_752
035087817, /dev/disk/by-id/ata-QUANTUM_FIREBALLlct20_20_752035087817, /dev/disk/
by-path/pci-0000:00:1f.2-scsi-0:0:1:0
 Device Number: block 8:16-8:31
 BIOS id: 0x81
 Drive status: no medium
 Config Status: cfg=new, avail=yes, need=no, active=unknown
 Attached to: #22 (IDE interface)

46: None 00.0: 11300 Partition
 [Created at block.391]
 UDI: /org/freedesktop/Hal/devices/volume_uuid_db16e84e_6401_4f07_815c_9e555189
a78e
 Unique ID: 6Kfz.SE1wIdpsiiC
 Parent ID: DQI9.Zjm32PQro4E
 SysFS ID: /block/sdb/sdb1
 Hardware Class: partition
 Model: "Partition"
 Device File: /dev/sdb1
 Device Files: /dev/sdb1, /dev/disk/by-id/scsi-1ATA_QUANTUM_FIREBALLlct20_20_75
2035087817-part1, /dev/disk/by-id/ata-QUANTUM_FIREBALLlct20_20_752035087817-part
1, /dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:1:0-part1, /dev/disk/by-uuid/db16
e84e-6401-4f07-815c-9e555189a78e
 Config Status: cfg=new, avail=yes, need=no, active=unknown
 Attached to: #45 (Disk)

47: None 00.0: 11300 Partition
 [Created at block.391]
 UDI: /org/freedesktop/Hal/devices/volume_part2_size_1024
 Unique ID: ZVv1.SE1wIdpsiiC
 Parent ID: DQI9.Zjm32PQro4E
 SysFS ID: /block/sdb/sdb2
 Hardware Class: partition
 Model: "Partition"
 Device File: /dev/sdb2
 Device Files: /dev/sdb2, /dev/disk/by-id/scsi-1ATA_QUANTUM_FIREBALLlct20_20_75
2035087817-part2, /dev/disk/by-id/ata-QUANTUM_FIREBALLlct20_20_752035087817-part
2, /dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:1:0-part2
 Config Status: cfg=new, avail=yes, need=no, active=unknown
 Attached to: #45 (Disk)

48: None 00.0: 11300 Partition
 [Created at block.391]
 UDI: /org/freedesktop/Hal/devices/volume_uuid_36cf2f85_c8b5_4050_b8ea_a9ca2479
5a23
 Unique ID: w1gE.SE1wIdpsiiC
 Parent ID: DQI9.Zjm32PQro4E
 SysFS ID: /block/sdb/sdb5
 Hardware Class: partition
 Model: "Partition"
 Device File: /dev/sdb5
 Device Files: /dev/sdb5, /dev/disk/by-id/scsi-1ATA_QUANTUM_FIREBALLlct20_20_75
2035087817-part5, /dev/disk/by-id/ata-QUANTUM_FIREBALLlct20_20_752035087817-part
5, /dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:1:0-part5, /dev/disk/by-uuid/36cf
2f85-c8b5-4050-b8ea-a9ca24795a23
 Config Status: cfg=new, avail=yes, need=no, active=unknown
 Attached to: #45 (Disk)

49: IDE 100.0: 10600 Disk
 [Created at block.222]
 UDI: /org/freedesktop/Hal/devices/storage_serial_1ATA_WDC_WD2500KS_00MJB0_WD_W
CANKH320479
 Unique ID: gbYD.tOkFeeFfgL4
 Parent ID: w7Y8.xJeQ4DgzxT6
 SysFS ID: /block/sdc
 SysFS BusID: 1:0:0:0
 SysFS Device Link: /devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0
 Hardware Class: disk
 Model: "WDC WD2500KS-00M"
 Vendor: "WDC"
 Device: "WD2500KS-00M"
 Revision: "02.0"
 Driver: "ata_piix", "sd"
 Driver Modules: "ata_piix"
 Device File: /dev/sdc
 Device Files: /dev/sdc, /dev/disk/by-id/scsi-1ATA_WDC_WD2500KS-00MJB0_WD-WCANK
H320479, /dev/disk/by-id/ata-WDC_WD2500KS-00MJB0_WD-WCANKH320479, /dev/disk/by-p
ath/pci-0000:00:1f.2-scsi-1:0:0:0
 Device Number: block 8:32-8:47
 BIOS id: 0x82
 Drive status: no medium
 Config Status: cfg=new, avail=yes, need=no, active=unknown
 Attached to: #22 (IDE interface)

50: None 00.0: 11300 Partition
 [Created at block.391]
 UDI: /org/freedesktop/Hal/devices/volume_uuid_FE3C6A553C6A08CB
 Unique ID: BnzO.SE1wIdpsiiC
 Parent ID: gbYD.tOkFeeFfgL4
 SysFS ID: /block/sdc/sdc1
 Hardware Class: partition
 Model: "Partition"
 Device File: /dev/sdc1
 Device Files: /dev/sdc1, /dev/disk/by-id/scsi-1ATA_WDC_WD2500KS-00MJB0_WD-WCAN
KH320479-part1, /dev/disk/by-id/ata-WDC_WD2500KS-00MJB0_WD-WCANKH320479-part1, /
dev/disk/by-path/pci-0000:00:1f.2-scsi-1:0:0:0-part1, /dev/disk/by-uuid/FE3C6A55
3C6A08CB, /dev/disk/by-label/Big\x20Brother
 Config Status: cfg=new, avail=yes, need=no, active=unknown
 Attached to: #49 (Disk)

51: None 00.0: 11300 Partition
 [Created at block.391]
 UDI: /org/freedesktop/Hal/devices/volume_part2_size_20342013952
 Unique ID: eyDT.SE1wIdpsiiC
 Parent ID: gbYD.tOkFeeFfgL4
 SysFS ID: /block/sdc/sdc2
 Hardware Class: partition
 Model: "Partition"
 Device File: /dev/sdc2
 Device Files: /dev/sdc2, /dev/disk/by-id/scsi-1ATA_WDC_WD2500KS-00MJB0_WD-WCAN
KH320479-part2, /dev/disk/by-id/ata-WDC_WD2500KS-00MJB0_WD-WCANKH320479-part2, /
dev/disk/by-path/pci-0000:00:1f.2-scsi-1:0:0:0-part2
 Config Status: cfg=new, avail=yes, need=no, active=unknown
 Attached to: #49 (Disk)

52: None 00.0: 11300 Partition
 [Created at block.391]
 UDI: /org/freedesktop/Hal/devices/volume_uuid_0dd683f8_8055_4e05_a926_8bac2c33
90bb
 Unique ID: 58UX.SE1wIdpsiiC
 Parent ID: gbYD.tOkFeeFfgL4
 SysFS ID: /block/sdc/sdc3
 Hardware Class: partition
 Model: "Partition"
 Device File: /dev/sdc3
 Device Files: /dev/sdc3, /dev/disk/by-id/scsi-1ATA_WDC_WD2500KS-00MJB0_WD-WCAN
KH320479-part3, /dev/disk/by-id/ata-WDC_WD2500KS-00MJB0_WD-WCANKH320479-part3, /
dev/disk/by-path/pci-0000:00:1f.2-scsi-1:0:0:0-part3, /dev/disk/by-uuid/0dd683f8
-8055-4e05-a926-8bac2c3390bb
 Config Status: cfg=new, avail=yes, need=no, active=unknown
 Attached to: #49 (Disk)

53: SCSI 101.0: 10602 CD-ROM
 [Created at block.226]
 UDI: /org/freedesktop/Hal/devices/storage_model_DRW_1814BLT
 Unique ID: twPO.N68sMv18YR2
 Parent ID: w7Y8.xJeQ4DgzxT6
 SysFS ID: /block/sr0
 SysFS BusID: 1:0:1:0
 SysFS Device Link: /devices/pci0000:00/0000:00:1f.2/host1/target1:0:1/1:0:1:0
 Hardware Class: cdrom
 Model: "ASUS DRW-1814BLT"
 Vendor: "ASUS"
 Device: "DRW-1814BLT"
 Revision: "1.13"
 Driver: "ata_piix", "sr"
 Driver Modules: "ata_piix"
 Device File: /dev/sr0 (/dev/sg3)
 Device Files: /dev/sr0, /dev/scd0, /dev/disk/by-path/pci-0000:00:1f.2-scsi-1:0
:1:0, /dev/cdrom2, /dev/cdrw2, /dev/dvd2, /dev/dvdrw2
 Device Number: block 11:0 (char 21:3)
 Features: CD-R, CD-RW, DVD-R, DVD-RW, DVD+R, DVD+RW, DVD+DL, DVDRAM
 Drive status: no medium
 Config Status: cfg=new, avail=yes, need=no, active=unknown
 Attached to: #22 (IDE interface)
 Drive Speed: 48
              This is a part where are some drives.
              • Top
              • Bottom

              Comment

                #52
                Re: problem with ntfs&fat32 partitions

                Code:
                3: SCSI 101.0: 10602 CD-ROM
 [Created at block.226]
 UDI: /org/freedesktop/Hal/devices/storage_model_DRW_1814BLT
 Unique ID: twPO.N68sMv18YR2
 Parent ID: w7Y8.xJeQ4DgzxT6
 SysFS ID: /block/sr0
 SysFS BusID: 1:0:1:0
 SysFS Device Link: /devices/pci0000:00/0000:00:1f.2/host1/target1:0:1/1:0:1:0
 Hardware Class: cdrom
 Model: "ASUS DRW-1814BLT"
 Vendor: "ASUS"
 Device: "DRW-1814BLT"
 Revision: "1.13"
 Driver: "ata_piix", "sr"
 Driver Modules: "ata_piix"
 Device File: /dev/sr0 (/dev/sg3)
 Device Files: /dev/sr0, /dev/scd0, /dev/disk/by-path/pci-0000:00:1f.2-scsi-1:0
:1:0, /dev/cdrom2, /dev/cdrw2, /dev/dvd2, /dev/dvdrw2
 Device Number: block 11:0 (char 21:3)
 Features: CD-R, CD-RW, DVD-R, DVD-RW, DVD+R, DVD+RW, DVD+DL, DVDRAM
 Drive status: no medium
 Config Status: cfg=new, avail=yes, need=no, active=unknown
 Attached to: #22 (IDE interface)
 Drive Speed: 48
                look this.What does this meanIs my asus recognised?
                • Top
                • Bottom

                Comment

                  #53
                  Re: problem with ntfs&fat32 partitions

                  Yes it's clearly being found. The question is, what about those drivers?

                  Put a CD or DVD in it, and then see if it tries to mount.

                  EDIT: I see several different device designations:

                  /dev/sr0
                  /dev/sg3
                  /dev/scd0

                  That last one is the "normal" Kubuntu device file for CD/DVD drives. It may be that if you (a) make a mount point in /media, and (b) add a mount line to your /etc/fstab file, that this drive will work. So in Konsole do sudo mkdir /media/ASUS_DRW (or whatever name you like). Then edit /etc/fstab, as root, and make a mount line for the drive. For example:

                  /dev/scd0 /media/ASUS_DRW iso9660 user,noauto,exec 0 0

                  When you reboot the computer, you might get lucky.
                  • Top
                  • Bottom

                  Comment

                    #54
                    Re: problem with ntfs&fat32 partitions

                    Originally posted by dibl
                    Yes it's clearly being found. The question is, what about those drivers?

                    Put a CD or DVD in it, and then see if it tries to mount.
                    I cant belive.I put cd and he asked what I wont to do.And I opened without problem.WOW.Thank you!!!!!!!!!!!!!!!

                    Why didnt I tryed this.Because I know in windows,you see it.In linux its different.You have to put cd and then to use dvd drive.
                    • Top
                    • Bottom

                    Comment

                      #55
                      Re: problem with ntfs&fat32 partitions

                      GREAT -- that's good to hear.

                      Note the edit in my post above, to set your /etc/fstab file up so the drive is automatically found when you boot. But it will only mount when there is a CD or DVD in it.
                      • Top
                      • Bottom

                      Comment

                        #56
                        Re: problem with ntfs&fat32 partitions

                        I hope I wont destroy my fstab file again?
                        • Top
                        • Bottom

                        Comment

                          #57
                          Re: problem with ntfs&fat32 partitions

                          Backup up the one you have now, like this:

                          Code:
                          sudo cp /etc/fstab /etc/fstab.bak21dec07

                          That way you can always restore it if your editing adventure goes badly.
                          • Top
                          • Bottom

                          Comment

                            #58
                            Re: problem with ntfs&fat32 partitions

                            Since I am new user I dont wont to experiment now.But I wont to ask you smt.When I decide to reinstall kubuntu will the procedure for my ntfs&fat partitions be the same.Creating some files and then write those codes in fstab...
                            • Top
                            • Bottom

                            Comment

                              #59
                              Re: problem with ntfs&fat32 partitions

                              Probably it will be easier, because if you have your drives all connected when you do the new installation, the ntfs partitions will be detected at that time, and the /etc/fstab file will be written to include them. Only USB drives don't get picked up automatically. At least that's the way I THINK it will work -- it's been a while since I had a NTFS partition.
                              • Top
                              • Bottom

                              Comment

                                #60
                                Re: problem with ntfs&fat32 partitions

                                Hm,when I instaled kubuntu,step after partitionig, kubuntu showed me all partitions,and I choose just ext3&swap.I didnt know what to do with those partitions so I chose just ext3&swap.Maybe I needed to mount all partitions then,but I did installation by the book.
                                • Top
                                • Bottom

                                Comment

                                Previous 1 2 3 4 5 template Next
                                Working...
                                X