Results 1 to 7 of 7

Thread: Not able to access DISK DRIVES...NEWLY INSTALLED OS.

  1. #1

    Unhappy Not able to access DISK DRIVES...NEWLY INSTALLED OS.

    Hi.
    I have installed SUSE yesterday.Everything has been fine except two.
    1. I can't access my hard disk drives. It says it need to install online some software for it but it can't.I am attaching a screen shot of the error I encounter.
    2. I have Ubuntu installed in another disk drive but in the Grub menu there in no option to boot to Ubuntu OS.How should I change the text in 'menu.lst' to solve the problem?

    I will post screenshots too I you please.
    Please reply soon.
    Thanks in advance.

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,130

    Default Re: Not able to access DISK DRIVES...NEWLY INSTALLED OS.

    On 1 (and it may be helpfull on 2 also) please the output (as root) of
    Code:
    fdisk -l
    and
    Code:
    cat /etc/fstab
    and
    Code:
    mount
    (Please put the output between CODE tags to preserve the format. You can do this by:
    a) using The Go Advanced option below right of the Response;
    b) selecting the copied/pasted computer text and hen click the # buton in the toolbar.)

    Btw, it can not be true that "I can't access my hard disk drives.", because then you would have nor running system at all.
    Henk van Velden

  3. #3

    Default Re: Not able to access DISK DRIVES...NEWLY INSTALLED OS.

    I am thankful that you spared some time for replying.
    This is the exact text which comes when I try to access any of my partition (except system,usb,rom) "YThere is no application installed that can open files of the type block device (inode/blockdevice). Do you want to try to install one?"

    OUTPUT CODE :

    1. fdisk -l
    Code:
    linux-1a49:/home/rishap # fdisk -l
    
    Disk /dev/sda: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00044460
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1               1        4569    36700461    7  HPFS/NTFS
    /dev/sda2   *        4570       60800   451675507+   5  Extended
    /dev/sda5            4570        5874    10482381   83  Linux
    /dev/sda6            5875        8323    19662848   83  Linux
    /dev/sda7            8323        8583     2095104   82  Linux swap / Solaris
    /dev/sda8            8584       21637   104856223+   7  HPFS/NTFS
    /dev/sda9           21638       34691   104856223+   7  HPFS/NTFS
    /dev/sda10          34692       47745   104856223+   7  HPFS/NTFS
    /dev/sda11          47746       60800   104864256    7  HPFS/NTFS
    2. cat/etc/fstab

    Code:
    linux-1a49:/home/rishap # cat /etc/fstab
    /dev/disk/by-id/ata-ST3500418AS_9VMFPAXP-part11 swap                 swap       defaults              0 0
    /dev/disk/by-id/ata-ST3500418AS_9VMFPAXP-part5 /                    ext4       acl,user_xattr        1 1
    /dev/disk/by-id/ata-ST3500418AS_9VMFPAXP-part1 /windows/C           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
    /dev/disk/by-id/ata-ST3500418AS_9VMFPAXP-part6 /windows/D           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
    /dev/disk/by-id/ata-ST3500418AS_9VMFPAXP-part7 /windows/E           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
    /dev/disk/by-id/ata-ST3500418AS_9VMFPAXP-part8 /windows/F           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
    /dev/disk/by-id/ata-ST3500418AS_9VMFPAXP-part9 /windows/G           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
    proc                 /proc                proc       defaults              0 0
    sysfs                /sys                 sysfs      noauto                0 0
    debugfs              /sys/kernel/debug    debugfs    noauto                0 0
    usbfs                /proc/bus/usb        usbfs      noauto                0 0
    devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
    3. mount
    Code:
    linux-1a49:/home/rishap # mount
    /dev/sda5 on / type ext4 (rw,acl,user_xattr)
    proc on /proc type proc (rw)
    sysfs on /sys type sysfs (rw)
    debugfs on /sys/kernel/debug type debugfs (rw)
    devtmpfs on /dev type devtmpfs (rw,mode=0755)
    tmpfs on /dev/shm type tmpfs (rw,mode=1777)
    devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
    fusectl on /sys/fs/fuse/connections type fusectl (rw)
    /dev/sda1 on /windows/C type fuseblk (rw,noexec,nosuid,nodev,allow_other,blksize=4096,default_permissions)
    /dev/sda8 on /windows/F type fuseblk (rw,noexec,nosuid,nodev,allow_other,blksize=4096,default_permissions)
    /dev/sda9 on /windows/G type fuseblk (rw,noexec,nosuid,nodev,allow_other,blksize=4096,default_permissions)
    securityfs on /sys/kernel/security type securityfs (rw)
    Yes,it was stupid from my part to say "Can't access my disk drive"
    Thanks in advance.

  4. #4
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,743

    Default Re: Not able to access DISK DRIVES...NEWLY INSTALLED OS.

    I only see one disk. What is this other disk?

  5. #5
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,733
    Blog Entries
    20

    Default Re: Not able to access DISK DRIVES...NEWLY INSTALLED OS.

    From the fstab it looks like SUSE is just on sda5
    so perhaps Ub* is on sda6? rather than a different drive

    Please see this for better access to ntfs:
    FSTAB - Editing Manually

    So for example, taking one of your entries I would change it to:
    Code:
    /dev/disk/by-id/ata-ST3500418AS_9VMFPAXP-part1 /windows/C           ntfs-3g defaults 0 0
    If Ubuntu was on sda6, you need to add an entry to /boot/grub/menu.lst
    like this

    Code:
    ###Don't change this comment - YaST2 identifier: Original name: Ubuntu###
    title Ubuntu
        root (hd0,5)
        kernel /vmlinuz root=/dev/sda6 ro quiet splash
        initrd /initrd.img
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  6. #6

    Default Re: Not able to access DISK DRIVES...NEWLY INSTALLED OS.

    I meant "Other Partition" but wrote it as "Other Disk" .
    Here Other partition = partition not having the Open Suse Installed in.

  7. #7
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,733
    Blog Entries
    20

    Default Re: Not able to access DISK DRIVES...NEWLY INSTALLED OS.

    Quote Originally Posted by risshahaprma View Post
    I meant "Other Partition" but wrote it as "Other Disk" .
    Here Other partition = partition not having the Open Suse Installed in.
    So did you manage the edit as per my instructions above?
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •