Find the answer to your Linux question:
Results 1 to 9 of 9
Hi all. My first post and only my second day using Linux (Ubuntu 10.10), so please be gentle with me. lol. Bit of back ground to my problem. I have ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Dec 2010
    Posts
    6

    Unable to mount array?


    Hi all.
    My first post and only my second day using Linux (Ubuntu 10.10), so please be gentle with me. lol.
    Bit of back ground to my problem.
    I have a Netgear Stora that has just died, but realy need the info off the drive inside.
    Support have told me that the drive can be read on Linux, so here I am.
    Right.
    Places-Computer shows drive as "array".
    System-Administrator-Disk utility gives me everything blank apart from State : not running, not enough componets to start.
    Now there is a button under this "Start Array".
    Can I simply just click this or is there more to it than that as I don't want to lose anything on the drive.
    Thanks in advance.
    J
    Last edited by jaysback; 12-05-2010 at 10:40 PM.

  2. #2
    Just Joined! barriehie's Avatar
    Join Date
    Apr 2008
    Location
    The Desert!
    Posts
    85
    Quote Originally Posted by jaysback View Post
    Hi all.
    My first post and only my second day using Linux (Ubuntu 10.10), so please be gentle with me. lol.
    Bit of back ground to my problem.
    I have a Netgear Stora that has just died, but realy need to info off the drive in it.
    Support have told me that drive can be read on Linux, so here I am.
    Right.
    Places-Computer shows drive as "array".
    System-Administrator-Disk utility gives me everything blank apart from State : not running, not enough componets to start.
    Now there is a button under this "Start Array".
    Can I simply just click this or is there more to it than that as I don't want to lose anything on the drive.
    Thanks in advance.
    J
    From a terminal post the output of:
    Code:
    sudo fdisk -l
    (that's a little L)

  3. #3
    Just Joined!
    Join Date
    Dec 2010
    Posts
    6
    Hi barriehie.
    As requested.

    kids@kids-P35C-DS3R:~$ sudo fdisk -l

    Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 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: 0x0000cd45

    Device Boot Start End Blocks Id System
    /dev/sda1 1 121577 976562500 fd Linux RAID autodetect

    Hope this sheds some light on it for you.

  4. #4
    Just Joined! barriehie's Avatar
    Join Date
    Apr 2008
    Location
    The Desert!
    Posts
    85
    Hmm, search engine results tell me that's a proprietary 'box' you've got their! Since the manual indicates a section on failed drives I'ld stay away from it! Sorry!

  5. #5
    Just Joined!
    Join Date
    Dec 2010
    Posts
    6
    DOH!
    Thats not good
    So much for Netgear's customer support.
    Cheers for taking a look though.
    J

  6. #6
    Just Joined!
    Join Date
    Dec 2010
    Posts
    6
    I have just tried mdadm.
    This so far hasn't worked
    Here is the output for anyone who may be interested.

    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages were automatically installed and are no longer required:
    linux-headers-2.6.35-22 linux-headers-2.6.35-22-generic
    Use 'apt-get autoremove' to remove them.
    The following NEW packages will be installed
    mdadm
    0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded.
    Need to get 0B/237kB of archives.
    After this operation, 676kB of additional disk space will be used.
    Preconfiguring packages ...
    Selecting previously deselected package mdadm.
    (Reading database ... 145217 files and directories currently installed.)
    Unpacking mdadm (from .../mdadm_2.6.7.1-1ubuntu16_i386.deb) ...
    Processing triggers for ureadahead ...
    Processing triggers for doc-base ...
    Processing 1 added doc-base file(s)...
    Registering documents with scrollkeeper...
    Processing triggers for man-db ...
    Setting up mdadm (2.6.7.1-1ubuntu16) ...
    Generating array device nodes... /var/lib/dpkg/info/mdadm.postinst: 170: /dev/MAKEDEV: not found
    failed.
    Generating mdadm.conf... done.
    Removing any system startup links for /etc/init.d/mdadm-raid ...
    update-initramfs: deferring update (trigger activated)
    update-rc.d: warning: mdadm start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (S)
    update-rc.d: warning: mdadm stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (0 6)
    * Starting MD monitoring service mdadm --monitor [ OK ]
    Processing triggers for initramfs-tools ...
    update-initramfs: Generating /boot/initrd.img-2.6.35-23-generic
    kids@kids-P35C-DS3R:~$ mdadm --assemble --scan
    mdadm: failed to create /dev/md0

    **edit**
    Just tried a restart and running "mdadm --assemble --scan
    mdadm: error opening /dev/md0: permission denied
    Last edited by jaysback; 12-06-2010 at 06:47 PM.

  7. #7
    Just Joined!
    Join Date
    Dec 2010
    Posts
    6
    Things are looking up
    I can now see all the folders in the drive
    I don't have access to them due to permissions

  8. #8
    Just Joined!
    Join Date
    Dec 2010
    Posts
    6
    Permission problem sorted and stuff of the drive.
    Had to set a password for the root login and then was all good.
    Cheers all for your help

  9. #9
    Just Joined!
    Join Date
    Jan 2011
    Posts
    1
    I am also a Linux newbie... I had a buffalo terrastation die on me I believe I over filled the RAID and when I lost power I did not have room to load the needed files how it did not get a chance to delete them before the power was lost.

    I found this article
    buffalo.nas-central.org/wiki/Terastation_Data_Recovery

    So I borrowed a Intel PowerPC Mac Mini from a friend and got adapters and a USB hub to plug the drives into the Mac Mini. I made a Ubuntu 10.10 disk and booted into it and it see's the array but can not mount it.

    I figured out how to enable root and logged into it and tried to run the steps but still no luck.

    I did a sudo fdisk -l with the following results:





    root@ubuntu:~# sudo fdisk -l
    WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.

    Disk /dev/sda: 60.0 GB, 60011642880 bytes
    255 heads, 63 sectors/track, 7296 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: 0x000045b4

    Device Boot Start End Blocks Id System
    /dev/sda1 1 7296 58605116 ee GPT

    Disk /dev/sdb: 160.0 GB, 160041885696 bytes
    255 heads, 63 sectors/track, 19457 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: 0x5b6ac646

    Device Boot Start End Blocks Id System
    /dev/sdb1 1 19457 156288321 c W95 FAT32 (LBA)

    Disk /dev/sdc: 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: 0x35353535

    Device Boot Start End Blocks Id System
    /dev/sdc1 1 48 385528+ fd Linux raid autodetect
    /dev/sdc2 49 65 136552+ 82 Linux swap / Solaris
    /dev/sdc3 66 60772 487620946 fd Linux raid autodetect
    /dev/sdc4 60772 60801 240974 fd Linux raid autodetect

    Disk /dev/sdd: 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: 0x35353535

    Device Boot Start End Blocks Id System
    /dev/sdd1 1 48 385528+ fd Linux raid autodetect
    /dev/sdd2 49 65 136552+ 82 Linux swap / Solaris
    /dev/sdd3 66 60772 487620946 fd Linux raid autodetect
    /dev/sdd4 60772 60801 240974 fd Linux raid autodetect

    Disk /dev/sde: 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: 0x35353535

    Device Boot Start End Blocks Id System
    /dev/sde1 1 48 385528+ fd Linux raid autodetect
    /dev/sde2 49 65 136552+ 82 Linux swap / Solaris
    /dev/sde3 66 60772 487620946 fd Linux raid autodetect
    /dev/sde4 60772 60801 240974 fd Linux raid autodetect

    Disk /dev/sdf: 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: 0x35353535

    Device Boot Start End Blocks Id System
    /dev/sdf1 1 48 385528+ fd Linux raid autodetect
    /dev/sdf2 49 65 136552+ 82 Linux swap / Solaris
    /dev/sdf3 66 60772 487620946 fd Linux raid autodetect
    /dev/sdf4 60772 60801 240974 fd Linux raid autodetect


    I noticed the mention of mdadm i downloaded it but could not figure how to install it. I was not sure if I had to have a true install of Ubuntu and not just boot off the CD. When I unzip the folder there is a install file that when I double click it tells me: To build mdadm, simply run: make to install, run make installs root. No configuration is necessary.


    Please help MUST get some files off the RAID

Posting Permissions

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