How can I read files on LaCie Drive using Linux

[shanemun]

Hi arnauerola,
thanks for your post. I went through your steps but id idint seem to work for me. I was booting from a usb memory key. then had to install mdadm from the software center. It gave me an error on the install. here are the details:

installArchives() failed: Preconfiguring packages ...
Preconfiguring packages ...
Selecting previously deselected package mdadm.
(Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 121715 files and directories currently installed.)
Unpacking mdadm (from .../mdadm_2.6.7.1-1ubuntu16_amd64.deb) ...
Selecting previously deselected package postfix.
Unpacking postfix (from .../postfix_2.7.1-1_amd64.deb) ...
Processing triggers for ureadahead ...
Processing triggers for doc-base ...
Processing 31 changed 1 added doc-base file(s)...
Registering documents with scrollkeeper...
Processing triggers for man-db ...
Processing triggers for ufw ...
WARN: / is world writable!
WARN: / is group writable!
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)
cp: cannot stat `/vmlinuz': No such file or directory
dpkg: error processing mdadm (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up postfix (2.7.1-1) ...
Adding group `postfix' (GID 123) ...
Done.
Adding system user `postfix' (UID 114) ...
Adding new user `postfix' (UID 114) with group `postfix' ...
Not creating home directory `/var/spool/postfix'.
Creating /etc/postfix/dynamicmaps.cf
Adding tcp map entry to /etc/postfix/dynamicmaps.cf
Adding group `postdrop' (GID 124) ...
Done.
setting myhostname: ubuntu
setting alias maps
setting alias database
mailname is not a fully qualified domain name. Not changing /etc/mailname.
setting destinations: ubuntu, localhost.localdomain, , localhost
setting relayhost:
setting mynetworks: 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
setting mailbox_size_limit: 0
setting recipient_delimiter: +
setting inet_interfaces: all
/etc/aliases does not exist, creating it.
WARNING: /etc/aliases exists, but does not have a root alias.

Postfix is now set up with a default configuration. If you need to make
changes, edit
/etc/postfix/main.cf (and others) as needed. To view Postfix configuration
values, see postconf(1).

After modifying main.cf, be sure to run '/etc/init.d/postfix reload'.

Running newaliases
* Stopping Postfix Mail Transport Agent postfix
...done.
* Starting Postfix Mail Transport Agent postfix
...done.
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.35-22-generic
cp: cannot stat `/vmlinuz': No such file or directory
dpkg: error processing initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Setting up initramfs-tools (0.98.1ubuntu6) ...
update-initramfs: deferring update (trigger activated)
cp: cannot stat `/vmlinuz': No such file or directory
dpkg: error processing initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mdadm:
mdadm depends on initramfs-tools (>= 0.85eubuntu24); however:
Package initramfs-tools is not configured yet.
dpkg: error processing mdadm (--configure):
dependency problems - leaving unconfigured


So then I proceeded anyway with your advice above. here is the text from that:

ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 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: 0x0b5289df

Device Boot Start End Blocks Id System
/dev/sda1 1 125 1004031 5 Extended
/dev/sda2 126 91201 731567970 83 Linux
/dev/sda5 1 16 128457 82 Linux swap / Solaris
/dev/sda6 17 17 8001 83 Linux
/dev/sda7 18 18 8001 83 Linux
/dev/sda8 19 40 176683+ 83 Linux
/dev/sda9 41 124 674698+ 83 Linux
/dev/sda10 125 125 8001 83 Linux

Disk /dev/sdb: 2002 MB, 2002780160 bytes
62 heads, 62 sectors/track, 1017 cylinders
Units = cylinders of 3844 * 512 = 1968128 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xbb0eb409

This doesn't look like a partition table
Probably you selected the wrong device.

Device Boot Start End Blocks Id System
/dev/sdb1 ? 896832 1382432 933323145+ 66 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(1010, 16, 43) logical=(896831, 25, 13)
Partition 1 has different physical/logical endings:
phys=(906, 97, 3) logical=(1382431, 23, 27)
Partition 1 does not end on cylinder boundary.
/dev/sdb2 ? 1 1 0 72 Unknown
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(101, 116, 32) logical=(0, 41, 32)
Partition 2 has different physical/logical endings:
phys=(370, 114, 47) logical=(0, 41, 31)
Partition 2 does not end on cylinder boundary.

Partition table entries are not in disk order

Disk /dev/sdc: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 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: 0xbb14e257

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sdc2 13 25497 204697600 7 HPFS/NTFS
/dev/sdc3 25497 57368 256000000 7 HPFS/NTFS
/dev/sdc4 57368 91202 271771648 7 HPFS/NTFS
ubuntu@ubuntu:~$ sudo mount
aufs on / type aufs (rw)
none on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
/dev/sdb on /cdrom type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/loop0 on /rofs type squashfs (ro,noatime)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/ubuntu/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=ubuntu)
ubuntu@ubuntu:~$ ls -la dev/md*
ls: cannot access dev/md*: No such file or directory
ubuntu@ubuntu:~$ ls -la /dev/md1
brw-rw---- 1 root disk 9, 1 2010-11-19 11:54 /dev/md1
ubuntu@ubuntu:~$ sudo mdadm --stop /dev/md1
mdadm: stopped /dev/md1
ubuntu@ubuntu:~$ ls -la /dev/md*
brw-rw---- 1 root disk 9, 0 2010-11-19 11:54 /dev/md0
brw-rw---- 1 root disk 9, 1 2010-11-19 18:57 /dev/md1
brw-rw---- 1 root disk 9, 2 2010-11-19 11:54 /dev/md2
brw-rw---- 1 root disk 9, 3 2010-11-19 11:54 /dev/md3
brw-rw---- 1 root disk 9, 4 2010-11-19 11:54 /dev/md4
ubuntu@ubuntu:~$ sudo unmount /dev/md1
sudo: unmount: command not found
ubuntu@ubuntu:~$ sudo mdadm --stop /dev/md0
mdadm: stopped /dev/md0
ubuntu@ubuntu:~$ sudo mdadm --stop /dev/md1
mdadm: stopped /dev/md1
ubuntu@ubuntu:~$ sudo mdadm --stop /dev/md2
mdadm: stopped /dev/md2
ubuntu@ubuntu:~$ sudo mdadm --stop /dev/md3
mdadm: stopped /dev/md3
ubuntu@ubuntu:~$ sudo mdadm --stop /dev/md4
mdadm: stopped /dev/md4
ubuntu@ubuntu:~$ ls -la /dev/sda2 /mnt/xfs
ls: cannot access /mnt/xfs: No such file or directory
brw-rw---- 1 root disk 8, 2 2010-11-19 11:54 /dev/sda2
ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 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: 0x0b5289df

Device Boot Start End Blocks Id System
/dev/sda1 1 125 1004031 5 Extended
/dev/sda2 126 91201 731567970 83 Linux
/dev/sda5 1 16 128457 82 Linux swap / Solaris
/dev/sda6 17 17 8001 83 Linux
/dev/sda7 18 18 8001 83 Linux
/dev/sda8 19 40 176683+ 83 Linux
/dev/sda9 41 124 674698+ 83 Linux
/dev/sda10 125 125 8001 83 Linux

Disk /dev/sdb: 2002 MB, 2002780160 bytes
62 heads, 62 sectors/track, 1017 cylinders
Units = cylinders of 3844 * 512 = 1968128 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xbb0eb409

This doesn't look like a partition table
Probably you selected the wrong device.

Device Boot Start End Blocks Id System
/dev/sdb1 ? 896832 1382432 933323145+ 66 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(1010, 16, 43) logical=(896831, 25, 13)
Partition 1 has different physical/logical endings:
phys=(906, 97, 3) logical=(1382431, 23, 27)
Partition 1 does not end on cylinder boundary.
/dev/sdb2 ? 1 1 0 72 Unknown
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(101, 116, 32) logical=(0, 41, 32)
Partition 2 has different physical/logical endings:
phys=(370, 114, 47) logical=(0, 41, 31)
Partition 2 does not end on cylinder boundary.

Partition table entries are not in disk order

Disk /dev/sdc: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 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: 0xbb14e257

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sdc2 13 25497 204697600 7 HPFS/NTFS
/dev/sdc3 25497 57368 256000000 7 HPFS/NTFS
/dev/sdc4 57368 91202 271771648 7 HPFS/NTFS
ubuntu@ubuntu:~$



The device is obviously the sda device.

I am getting more comfortable wtih ubuntu now but still really dont know what I am doing here. any hepl is again much muCH APPRECIATED

Shane

 

[arnauerola]

Hi,

mdadm: stopped /dev/md4
ubuntu@ubuntu:~$ ls -la /dev/sda2 /mnt/xfs
ls: cannot access /mnt/xfs: No such file or directory
brw-rw---- 1 root disk 8, 2 2010-11-19 11:54 /dev/sda2
ubuntu@ubuntu:~$ sudo fdisk -l

After stopped the last raid-device and before enter to your partion disc you must mount the partition! In your case:

$sudo mount -t xfs -r /dev/sda2 /mnt/xfs

and now you can enter to the disc: ls -la /mnt/xfs

Best regards.

 

[shanemun]

Thanks again!

I think I'm almost there. It is just not letting me mount at the last step. any suggestions?


Device Boot Start End Blocks Id System
/dev/sdb1 1 125 1004031 5 Extended
/dev/sdb2 126 91201 731567970 83 Linux
/dev/sdb5 1 16 128457 82 Linux swap / Solaris
/dev/sdb6 17 17 8001 83 Linux
/dev/sdb7 18 18 8001 83 Linux
/dev/sdb8 19 40 176683+ 83 Linux
/dev/sdb9 41 124 674698+ 83 Linux
/dev/sdb10 125 125 8001 83 Linux
shannonfeindel@ubuntu:~$ sudo mount -t xfs -r /dev/sdb2 /mnt/xfs
mount: mount point /mnt/xfs does not exist
shannonfeindel@ubuntu:~$ ls -la /dev/md*
brw-rw---- 1 root disk 9, 0 2010-11-26 12:24 /dev/md0
brw-rw---- 1 root disk 9, 1 2010-11-26 12:24 /dev/md1
shannonfeindel@ubuntu:~$ sudo mdadm --stop /dev/md0
mdadm: stopped /dev/md0
shannonfeindel@ubuntu:~$ sudo mdadm --stop /dev/md1
mdadm: stopped /dev/md1
shannonfeindel@ubuntu:~$ ls -la /dev/md*
brw-rw---- 1 root disk 9, 1 2010-11-26 12:26 /dev/md1
shannonfeindel@ubuntu:~$ sudo mdadm --stop /dev/md1
mdadm: stopped /dev/md1
shannonfeindel@ubuntu:~$ ls -la /dev/md*
brw-rw---- 1 root disk 9, 1 2010-11-26 12:26 /dev/md1
shannonfeindel@ubuntu:~$ sudo mdadm --stop /dev/md1
mdadm: stopped /dev/md1
shannonfeindel@ubuntu:~$ ls -la /dev/md*
brw-rw---- 1 root disk 9, 1 2010-11-26 12:27 /dev/md1
shannonfeindel@ubuntu:~$ sudo mdadm --stop /dev/md1
mdadm: error opening /dev/md1: No such file or directory
shannonfeindel@ubuntu:~$ ls -la /dev/md*
ls: cannot access /dev/md*: No such file or directory
shannonfeindel@ubuntu:~$ sudo mount -t xfs -r /dev/sdb2 /mnt/xfs
mount: mount point /mnt/xfs does not exist
shannonfeindel@ubuntu:~$ sudo mount -t xfs -r /dev/sdb2 /mnt/xfs
mount: mount point /mnt/xfs does not exist
shannonfeindel@ubuntu:~$ sudo mount -t xfs -r /dev/sdb5 /mnt/xfs
mount: mount point /mnt/xfs does not exist
shannonfeindel@ubuntu:~$



Thanks a bunch

shane

 

[arnauerola]

mount point /mnt/xfs does not exist

Before mount you may create de directory:

$sudo mkdir /mnt/xfs

Then you can mount the partition.

 

[shanemun]

Hello!,

Thanks for such awesome information. That step worked too. It is probably a silly question now but how would I access the files on the disk? The "computer" tab shows the 5 different raid drives but when I click on each one it tells me that it is unable to mount that volume. Do I access the raid drive files I need through the terminal. I really just want to place the files on the raid drive onto my main computer drive. I think I am there but missing something obvious! Here is the code for the last bit

\mdadm: error opening /dev/md4: No such file or directory
shannonfeindel@ubuntu:~$ ls -la /dev/md*
ls: cannot access /dev/md*: No such file or directory
shannonfeindel@ubuntu:~$ sudo mkdir /mnt/xfs
shannonfeindel@ubuntu:~$ sudo mount -t xfs -r /dev/sdb2 /mnt/xfs
shannonfeindel@ubuntu:~$ ls -la /mnt/xfs
total 4
drwxr-xr-x 3 root root 18 2000-01-04 11:59 .
drwxr-xr-x 3 root root 4096 2010-11-28 21:41 ..
drwxr-xr-x 3 root root 26 2000-01-04 12:15 share
shannonfeindel@ubuntu:~$

Thank you very much for your patience and help! Great for newbies like me 😱

Shane

 

[arnauerola]

Hi Shane!

These are good news! Your partition are operable again. Problably your data is inside the folder share/C.

You can acces to your data easely with the graphic interface. On the menu of the desktop Places -> File System -> mnt -> xfs -> share -> etc. etc. You can copy the files normally with right clic on the mouse and then paste to another drive.

 

[gnatk]

I did try that, but it didn't like it. I was actually using Ubuntu, and then tried Knoppix. No dice on that, but I ended up getting tired of fighting it and purchased the UFS Explorer program. I just connected the drive up to windows xp, ran the program and it was like butter. About $50, but sometimes the money is worth it. Like in this case. Thanks for the replies though.

Crasty, can you outline the steps you took using the UFS Explorer program? I can't figure out how to use or even view where my files. I see one of the my Raid 1 (Safe) mounted but that is it. Thanks.

TK

 

[pe1biv]

Well, seems I'm another one with dead hardware in a LaCie 2big network drive...
The system indeed does not show up in the network, and also no reply on the static IP it did have.
From the back (drive side) the right one comes up blue steady normally, but the left one keeps on blinking, even when exchanging the drives.
I have had the same left bay blinking red-blue.

Both drives were tested using Spinrite, and though one had quite a few ECC errors, it still came through the test.

And obviously the backup on an external USB drive is not 100% up to date.....
I guess the first step is going to be to find another computer, as the FSC P4-3000 does not want to boot from USB, or create a Ubuntu CD..

 

[arnauerola]

You only need an Ubuntu Live CD and follow the steps below.

BR

 

[mclovin31]

I had the same issue with a broken LaCie NAS device. I removed the drive from the case and mounted it to a windows 8 machine using usb. Of course the OS did not see the drive although disk manager listed it. The solution is: UFS Explorer Professional Recovery. The software found all my data and it only took minutes.