Find the answer to your Linux question:
Page 1 of 3 1 2 3 LastLast
Results 1 to 10 of 25
Afternoon all, I have racked my brains and spent an age on this and I literally can't find a solution which I can follow so I thought I'd come to ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Aug 2010
    Posts
    14

    Question [SOLVED] My Dilemma - Mounting A External Ext3 Formatted h/d


    Afternoon all,

    I have racked my brains and spent an age on this and I literally can't find a solution which I can follow so I thought I'd come to the experts. My problem 'seems' simple to solve, but has yet to work out that way, if anyone can help... I'd be eternally grateful!

    My problem:
    I 'had' a WesternDigital NAS, Raid1, dual 500GB, it failed, one of the drives I think (no diagnostic tools to tell me).
    WD replaced my drive, however they 'upgraded' me as my product line was discontinued, so I now have a WD dual 1TB drive.
    Obviously this leaves me with the useful dilemma of not being able to just pop my 'working' drive back into a Raid array and have it rebuild, so I need to get the data back.

    What I have to work with:
    Now I found out, through exciting means, that WD format their NAS raid array drives with Linux and my two 500Gb h/d's are formatted with EXT3.
    I have my SATA drive out of the WD NAS and plugged into a ("Sharkoon QuickPort Combo" - you can see it in Amazon using that search) 3.5"USB h/d docking station and my windows workstations see the drive no problems.
    Yes, you heard right, I am not a Linux o/s user and only have Windows (bleeeurgh, yes please don't kill me) o/s (XP/ Vista). However I have VMWare of Linux installed on my Vista workstation with Ubuntu, Fedora and DSL seemingly running without any problems and all the o/s see the USB drive (from what I can tell).

    What I've tried
    I have used DiskInternals within the Windows OS to extract 'some' data from my drives, but most annoyingly the data that has taken me the longest to build up (i.e. my TV series' and my films) are not available in this program (and believe me, I've left the drives to 'scan' file structure with this program for 12-16hrs at a time on probably a dozen seperate occasions and I still can't see the data!!
    I've tried and failed to use KNOPPIX in VMWare mode (not in bootable CD - as I didn't see the difference) and whilst I got it working I couldn't see any way to get the data

    Can you tell me...
    How do I mount the drive within any of the above Linux o/s (or any other I can DL in ISO format and run in VMWare) so I can extract the data from it.
    I can open terminal and scan the drive etc but as for finding the actual data in order to copy the files... I'm TOTALLY baffled to say the least!



    REALLLLLLY appreciate any help anyone can give!!

  2. #2
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,410
    Actually, I wouldnt go the way via virtualization.

    1) Get a Knoppix ISO and either
    a) burn it as a bootable CD
    b) use UNetbootin - Homepage and Downloads to create a bootable USB stick
    The goal here is to boot a linux natively.

    2) Setup your new 1TB WD NAS to the point where it is useable.
    aka CIFS and/or NFS should work.
    A gigabit network between your PC and the NAS would be good,
    but 100MBit/s should also suffice

    3) connect your 500GB drive to that sharkoon device

    4) boot your PC from CD or USB stick

    5) Some information gathering / setup steps
    a) open a console, become root
    Code:
    sudo su -
    b) create a mountpoint for the NAS and mount it
    Code:
    mkdir /mnt/nas
    mount -t cifs -o username=<USERNAME> //<IP_OF_NAS>/<SHARE /mnt/nas
    c) see if and how the 500GByte disc is recognized
    Code:
    fdisk -l
    dmesg

    Please post the output of 5c) here and *please* use the code tags of the forum to do so.
    You must always face the curtain with a bow.

  3. #3
    Just Joined!
    Join Date
    Aug 2010
    Posts
    14

    Thumbs up

    Thanks for the response Irithori. I'll get on that now.

  4. $spacer_open
    $spacer_close
  5. #4
    Just Joined!
    Join Date
    Aug 2010
    Posts
    14
    Right. Well that went smoother than I expected.
    (TBF, I actually never saw that KNOPPIX o/s like that without the USB boot, so clearly I wasn't doing that correctly!)

    Anyway, as advised, booted, mounted my nas on the directory creation and saved the file out. Details with [ code] tags as requested below...

    Code:
    knoppix@Microknoppix:~$ sudo su
    root@Microknoppix:/home/knoppix# mkdir /mnt/nas
    root@Microknoppix:/home/knoppix# mount -t cifs -o username=v1per //192.168.1.1/data /mnt/nas
    Password: 
    root@Microknoppix:/home/knoppix# fdisk -l
    omitting empty partition (5)
    
    Disk /dev/sda: 320.1 GB, 320072933376 bytes
    255 heads, 63 sectors/track, 38913 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x80000000
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1               1           8       64228+  de  Dell Utility
    /dev/sda2               9        1313    10482160+   7  HPFS/NTFS
    /dev/sda3   *        1314       21509   162220770+   7  HPFS/NTFS
    /dev/sda4           21510       38914   139800181+   f  W95 Ext'd (LBA)
    /dev/sda5           21510       31900    83465676    7  HPFS/NTFS
    /dev/sda6           31901       31908       60370    7  HPFS/NTFS
    /dev/sda7           31909       38914    56270182+   7  HPFS/NTFS
    
    Disk /dev/sdb: 1011 MB, 1011351040 bytes
    4 heads, 32 sectors/track, 15431 cylinders
    Units = cylinders of 128 * 512 = 65536 bytes
    Disk identifier: 0x00000000
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdb1   *           1       15432      987631+   b  W95 FAT32
    
    Disk /dev/sdc: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00007a00
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdc1               4         369     2939895   fd  Linux raid autodetect
    /dev/sdc2             370         382      104422+  fd  Linux raid autodetect
    /dev/sdc3             383         505      987997+  fd  Linux raid autodetect
    /dev/sdc4             506       60801   484327588+   7  HPFS/NTFS
    root@Microknoppix:/home/knoppix# dmesg
     usb6: Manufacturer: Linux 2.6.32.6 uhci_hcd
    [    1.864407] usb usb6: SerialNumber: 0000:00:1d.0
    [    1.864459] usb usb6: configuration #1 chosen from 1 choice
    [    1.864493] hub 6-0:1.0: USB hub found
    [    1.864497] hub 6-0:1.0: 2 ports detected
    [    1.864531] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
    [    1.864535] uhci_hcd 0000:00:1d.1: setting latency timer to 64
    [    1.864538] uhci_hcd 0000:00:1d.1: UHCI Host Controller
    [    1.864581] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
    [    1.864600] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000fa00
    [    1.864622] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
    [    1.864624] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    1.864626] usb usb7: Product: UHCI Host Controller
    [    1.864627] usb usb7: Manufacturer: Linux 2.6.32.6 uhci_hcd
    [    1.864629] usb usb7: SerialNumber: 0000:00:1d.1
    [    1.864684] usb usb7: configuration #1 chosen from 1 choice
    [    1.864715] hub 7-0:1.0: USB hub found
    [    1.864719] hub 7-0:1.0: 2 ports detected
    [    1.864753] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    [    1.864757] uhci_hcd 0000:00:1d.2: setting latency timer to 64
    [    1.864760] uhci_hcd 0000:00:1d.2: UHCI Host Controller
    [    1.864804] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
    [    1.864823] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000f900
    [    1.864846] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001
    [    1.864848] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    1.864850] usb usb8: Product: UHCI Host Controller
    [    1.864851] usb usb8: Manufacturer: Linux 2.6.32.6 uhci_hcd
    [    1.864853] usb usb8: SerialNumber: 0000:00:1d.2
    [    1.864904] usb usb8: configuration #1 chosen from 1 choice
    [    1.864939] hub 8-0:1.0: USB hub found
    [    1.864943] hub 8-0:1.0: 2 ports detected
    [    1.865034] Initializing USB Mass Storage driver...
    [    1.865076] usbcore: registered new interface driver usb-storage
    [    1.865078] USB Mass Storage support registered.
    [    1.865101] usbcore: registered new interface driver ums-alauda
    [    1.865126] usbcore: registered new interface driver ums-cypress
    [    1.865152] usbcore: registered new interface driver ums-datafab
    [    1.865176] usbcore: registered new interface driver ums-freecom
    [    1.865199] usbcore: registered new interface driver ums-isd200
    [    1.865222] usbcore: registered new interface driver ums-jumpshot
    [    1.865247] usbcore: registered new interface driver ums-karma
    [    1.865270] usbcore: registered new interface driver ums-onetouch
    [    1.865294] usbcore: registered new interface driver ums-sddr09
    [    1.865318] usbcore: registered new interface driver ums-sddr55
    [    1.865341] usbcore: registered new interface driver ums-usbat
    [    1.865432] PNP: No PS/2 controller found. Probing ports directly.
    [    1.865780] serio: i8042 KBD port at 0x60,0x64 irq 1
    [    1.865785] serio: i8042 AUX port at 0x60,0x64 irq 12
    [    1.865951] mice: PS/2 mouse device common for all mice
    [    1.866169] rtc_cmos 00:04: RTC can wake from S4
    [    1.866211] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
    [    1.866231] rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
    [    1.866274] device-mapper: uevent: version 1.0.3
    [    1.866327] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
    [    1.866380] EISA: Probing bus 0 at eisa.0
    [    1.866407] cpuidle: using governor ladder
    [    1.866409] cpuidle: using governor menu
    [    1.866412] ioatdma: Intel(R) QuickData Technology Driver 4.00
    [    1.866734] usbcore: registered new interface driver hiddev
    [    1.866760] usbcore: registered new interface driver usbhid
    [    1.866762] usbhid: v2.6:USB HID core driver
    [    1.866791] Advanced Linux Sound Architecture Driver Version 1.0.21.
    [    1.866990] ALSA device list:
    [    1.866992]   No soundcards found.
    [    1.867046] TCP cubic registered
    [    1.867048] Initializing XFRM netlink socket
    [    1.867051] NET: Registered protocol family 17
    [    1.867057] NET: Registered protocol family 15
    [    1.867089] lib80211: common routines for IEEE802.11 drivers
    [    1.867090] lib80211_crypt: registered algorithm 'NULL'
    [    1.867517] Using IPI No-Shortcut mode
    [    1.867895] rtc_cmos 00:04: setting system clock to 2010-08-08 18:18:58 UTC (1281291538)
    [    1.867936] Freeing unused kernel memory: 484k freed
    [    2.206684] usb 2-1: new high speed USB device using ehci_hcd and address 2
    [    2.330830] usb 2-1: New USB device found, idVendor=08ec, idProduct=2039
    [    2.330833] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [    2.330835] usb 2-1: Product: DT Secure
    [    2.330836] usb 2-1: Manufacturer: Kingston
    [    2.330838] usb 2-1: SerialNumber: 07A1597100F0D8DC
    [    2.330966] usb 2-1: configuration #1 chosen from 1 choice
    [    2.336592] scsi6 : SCSI emulation for USB Mass Storage devices
    [    2.336665] usb-storage: device found at 2
    [    2.336673] usb-storage: waiting for device to settle before scanning
    [    2.443761] usb 2-2: new high speed USB device using ehci_hcd and address 3
    [    2.464653] attempt to access beyond end of device
    [    2.464657] sda4: rw=0, want=66, limit=2
    [    2.464660] isofs_fill_super: bread failed, dev=sda4, iso_blknum=16, block=32
    [    2.465578] attempt to access beyond end of device
    [    2.465582] sda4: rw=0, want=18, limit=2
    [    2.465586] REISERFS warning (device sda4): sh-2006 read_super_block: bread failed (dev sda4, block 8, size 1024)
    [    2.465591] attempt to access beyond end of device
    [    2.465593] sda4: rw=0, want=130, limit=2
    [    2.465596] REISERFS warning (device sda4): sh-2006 read_super_block: bread failed (dev sda4, block 64, size 1024)
    [    2.465885] attempt to access beyond end of device
    [    2.465888] sda4: rw=0, want=4, limit=2
    [    2.465890] EXT3-fs: unable to read superblock
    [    2.466172] attempt to access beyond end of device
    [    2.466175] sda4: rw=0, want=4, limit=2
    [    2.466177] EXT2-fs: unable to read superblock
    [    2.568457] usb 2-2: New USB device found, idVendor=152d, idProduct=2338
    [    2.568460] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
    [    2.568463] usb 2-2: Product: USB to ATA/ATAPI Bridge
    [    2.568465] usb 2-2: Manufacturer: JMicron
    [    2.568467] usb 2-2: SerialNumber: D57CA3533984
    [    2.568593] usb 2-2: configuration #1 chosen from 1 choice
    [    2.569398] scsi7 : SCSI emulation for USB Mass Storage devices
    [    2.569533] usb-storage: device found at 3
    [    2.569534] usb-storage: waiting for device to settle before scanning
    [    2.673356] usb 2-5: new high speed USB device using ehci_hcd and address 4
    [    2.854583] usb 2-5: New USB device found, idVendor=0644, idProduct=0200
    [    2.854586] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [    2.854589] usb 2-5: Product: CA-200
    [    2.854591] usb 2-5: Manufacturer: TEAC
    [    2.854593] usb 2-5: SerialNumber: 000001111BA2
    [    2.854725] usb 2-5: configuration #1 chosen from 1 choice
    [    2.854913] scsi8 : SCSI emulation for USB Mass Storage devices
    [    2.855049] usb-storage: device found at 4
    [    2.855051] usb-storage: waiting for device to settle before scanning
    [    3.080014] usb 5-1: new low speed USB device using uhci_hcd and address 2
    [    3.248186] usb 5-1: New USB device found, idVendor=046d, idProduct=c517
    [    3.248189] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    3.248192] usb 5-1: Product: USB Receiver
    [    3.248194] usb 5-1: Manufacturer: Logitech
    [    3.248307] usb 5-1: configuration #1 chosen from 1 choice
    [    3.265438] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:1.0/input/input3
    [    3.265546] logitech 0003:046D:C517.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1a.2-1/input0
    [    3.297189] logitech 0003:046D:C517.0002: fixing up Logitech keyboard report descriptor
    [    3.297902] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:1.1/input/input4
    [    3.298132] logitech 0003:046D:C517.0002: input,hiddev96,hidraw1: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1a.2-1/input1
    [    5.529979] attempt to access beyond end of device
    [    5.529982] sda4: rw=0, want=66, limit=2
    [    5.529986] isofs_fill_super: bread failed, dev=sda4, iso_blknum=16, block=32
    [    5.530884] attempt to access beyond end of device
    [    5.530887] sda4: rw=0, want=18, limit=2
    [    5.530892] REISERFS warning (device sda4): sh-2006 read_super_block: bread failed (dev sda4, block 8, size 1024)
    [    5.530896] attempt to access beyond end of device
    [    5.530899] sda4: rw=0, want=130, limit=2
    [    5.530902] REISERFS warning (device sda4): sh-2006 read_super_block: bread failed (dev sda4, block 64, size 1024)
    [    5.531192] attempt to access beyond end of device
    [    5.531196] sda4: rw=0, want=4, limit=2
    [    5.531198] EXT3-fs: unable to read superblock
    [    5.531484] attempt to access beyond end of device
    [    5.531487] sda4: rw=0, want=4, limit=2
    [    5.531489] EXT2-fs: unable to read superblock
    [    7.337134] scsi 6:0:0:0: Direct-Access     Kingston DT Secure        6.52 PQ: 0 ANSI: 0 CCS
    [    7.337410] sd 6:0:0:0: Attached scsi generic sg2 type 0
    [    7.337875] sd 6:0:0:0: [sdb] 1975295 512-byte logical blocks: (1.01 GB/964 MiB)
    [    7.338371] sd 6:0:0:0: [sdb] Write Protect is off
    [    7.338374] sd 6:0:0:0: [sdb] Mode Sense: 45 00 00 08
    [    7.338376] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    [    7.339999] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    [    7.340008]  sdb:
    [    7.340033] usb-storage: device scan complete
    [    7.340499]  sdb1
    [    7.341993] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    [    7.341996] sd 6:0:0:0: [sdb] Attached SCSI removable disk
    [    7.567508] scsi 7:0:0:0: Direct-Access     WDC WD50 00AAVS-00ZTB0    1B01 PQ: 0 ANSI: 2 CCS
    [    7.567722] sd 7:0:0:0: Attached scsi generic sg3 type 0
    [    7.568248] sd 7:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/465 GiB)
    [    7.568995] sd 7:0:0:0: [sdc] Write Protect is off
    [    7.568998] sd 7:0:0:0: [sdc] Mode Sense: 00 38 00 00
    [    7.569000] sd 7:0:0:0: [sdc] Assuming drive cache: write through
    [    7.570371] sd 7:0:0:0: [sdc] Assuming drive cache: write through
    [    7.570374]  sdc: sdc1 sdc2 sdc3 sdc4
    [    7.571089] usb-storage: device scan complete
    [    7.572620] sd 7:0:0:0: [sdc] Assuming drive cache: write through
    [    7.572623] sd 7:0:0:0: [sdc] Attached SCSI disk
    [    7.863511] scsi 8:0:0:0: Direct-Access     TEAC     USB   HS-CF Card 4.08 PQ: 0 ANSI: 0
    [    7.863723] sd 8:0:0:0: Attached scsi generic sg4 type 0
    [    7.871137] scsi 8:0:0:1: Direct-Access     TEAC     USB   HS-xD/SM   4.08 PQ: 0 ANSI: 0
    [    7.871324] sd 8:0:0:1: Attached scsi generic sg5 type 0
    [    7.875497] sd 8:0:0:0: [sdd] Attached SCSI removable disk
    [    7.883011] scsi 8:0:0:2: Direct-Access     TEAC     USB   HS-MS Card 4.08 PQ: 0 ANSI: 0
    [    7.883188] sd 8:0:0:2: Attached scsi generic sg6 type 0
    [    7.887497] sd 8:0:0:1: [sde] Attached SCSI removable disk
    [    7.891013] scsi 8:0:0:3: Direct-Access     TEAC     USB   HS-SD Card 4.08 PQ: 0 ANSI: 0
    [    7.891199] sd 8:0:0:3: Attached scsi generic sg7 type 0
    [    7.903497] sd 8:0:0:2: [sdf] Attached SCSI removable disk
    [    7.908121] sd 8:0:0:3: [sdg] Attached SCSI removable disk
    [    7.908274] usb-storage: device scan complete
    [    8.878524] attempt to access beyond end of device
    [    8.878528] sda4: rw=0, want=66, limit=2
    [    8.878531] isofs_fill_super: bread failed, dev=sda4, iso_blknum=16, block=32
    [    8.879463] attempt to access beyond end of device
    [    8.879466] sda4: rw=0, want=18, limit=2
    [    8.879470] REISERFS warning (device sda4): sh-2006 read_super_block: bread failed (dev sda4, block 8, size 1024)
    [    8.879475] attempt to access beyond end of device
    [    8.879477] sda4: rw=0, want=130, limit=2
    [    8.879481] REISERFS warning (device sda4): sh-2006 read_super_block: bread failed (dev sda4, block 64, size 1024)
    [    8.879769] attempt to access beyond end of device
    [    8.879772] sda4: rw=0, want=4, limit=2
    [    8.879774] EXT3-fs: unable to read superblock
    [    8.880058] attempt to access beyond end of device
    [    8.880061] sda4: rw=0, want=4, limit=2
    [    8.880063] EXT2-fs: unable to read superblock
    [    9.374077] cloop: Initializing cloop v2.631
    [    9.374942] cloop: loaded (max 8 devices)
    [    9.387985] aufs 2-standalone.tree-31-20090921
    [    9.388365] cloop: Can't open device read-write in mode 0x1f
    [    9.400257] cloop: losetup_file: 15110 blocks, 131072 bytes/block, largest block is 131158 bytes.
    [    9.423003] cloop: preloaded 32 blocks into cache.
    [    9.434563] ISO 9660 Extensions: RRIP_1991A
    [   14.462629] aufs test_add:242:busybox[1844]: uid/gid/perm /KNOPPIX 0/0/0755, 0/0/01777
    [   14.994997] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 18 (level, low) -> IRQ 18
    [   15.001285] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
    [   15.001288] e1000e: Copyright (c) 1999-2008 Intel Corporation.
    [   15.001320]   alloc irq_desc for 20 on node -1
    [   15.001322]   alloc kstat_irqs on node -1
    [   15.001327] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    [   15.001334] e1000e 0000:00:19.0: setting latency timer to 64
    [   15.001401]   alloc irq_desc for 25 on node -1
    [   15.001403]   alloc kstat_irqs on node -1
    [   15.001411] e1000e 0000:00:19.0: irq 25 for MSI/MSI-X
    [   15.042977] ohci1394 0000:02:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [   15.042982] ohci1394 0000:02:01.0: setting latency timer to 64
    [   15.095779] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[16]  MMIO=[fdcff000-fdcff7ff]  Max Packet=[2048]  IR/IT contexts=[8/8]
    [   15.101879] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:1a:a0:94:31:3c
    [   15.101882] 0000:00:19.0: eth0: Intel(R) PRO/10/100 Network Connection
    [   15.101900] 0000:00:19.0: eth0: MAC: 7, PHY: 7, PBA No: ffffff-0ff
    [   15.102836]   alloc irq_desc for 22 on node -1
    [   15.102838]   alloc kstat_irqs on node -1
    [   15.102843] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    [   15.102867] HDA Intel 0000:00:1b.0: setting latency timer to 64
    [   15.184687] hda_codec: ALC888: BIOS auto-probing.
    [   15.383781] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
    [   15.440886] FDC 0 is a post-1991 82077
    [   16.370135] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[0000d10080c3a8c8]
    [   16.964289] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input5
    [   19.969483] [drm] Setting GART location based on new memory map
    [   19.970338] [drm] Loading R500 Microcode
    [   19.970342] platform radeon_cp.0: firmware: using built-in firmware radeon/R520_cp.bin
    [   19.970386] [drm] Num pipes: 1
    [   19.970392] [drm] writeback test succeeded in 1 usecs
    [   82.140383] lp: driver loaded but no devices found
    [   82.157801] ppdev: user-space parallel port driver
    [   82.177266] e1000e 0000:00:19.0: irq 25 for MSI/MSI-X
    [   82.230691] e1000e 0000:00:19.0: irq 25 for MSI/MSI-X
    [   82.296133] NET: Registered protocol family 10
    [   82.296252] lo: Disabled Privacy Extensions
    [   82.296320] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [   83.897418] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
    [   83.897422] 0000:00:19.0: eth0: 10/100 speed: disabling TSO
    [   83.897592] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [   94.303343] eth0: no IPv6 routers present
    [  543.405932] Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
    [  543.405937]  CIFS VFS: Send error in SessSetup = -13
    [  543.405943]  CIFS VFS: cifs_mount failed w/return code = -13
    root@Microknoppix:/home/knoppix# 

  6. #5
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,410
    I can see three issues:

    1) You do have a intel gigabit NIC, but the speed is only 100MBit/s.
    Presumably, because your switch is not gigabit?
    Code:
    [   83.897418] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
    [   83.897422] 0000:00:19.0: eth0: 10/100 speed: disabling TSO
    [   83.897592] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    This is not a problem in itself, but the file sync will take longer.
    I would expect 5-6MByte/s, while CIFS over gigabit with consumer hardware usually reaches something like 30MByte/s

    2) The CIFS mount did not succeed
    Code:
    [  543.405932] Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
    [  543.405937]  CIFS VFS: Send error in SessSetup = -13
    [  543.405943]  CIFS VFS: cifs_mount failed w/return code = -13
    Easiest case: You just mistyped your password.
    If it worked, then /mnt/nas should show up after you type
    Code:
    mount
    Also, the following should show the directoy listing of the CIFShare
    Code:
    ls -la /mnt/nas/
    To start troubleshooting:
    Can you
    Code:
    ping 192.168.1.1
    and that username does have a 1 on purpose? v1per


    3) The 500GByte disc can be seen. Good.
    The biggest partition on it is sdc4.
    But strangely, its partitiontype is ntfs. It should be "linux raid autodetect", like the other ones.
    Hopefully no data got corrupted while you were using the DiskInternal tools..

    So, *usually* this should give you access
    Code:
    mkdir /mnt/usbdrive
    mount -t ext3 /dev/sdc4 /mnt/usbdrive
    ls -la /mnt/usbdrive
    If not, try to mount without giving the filesystem type (ie: omitting -t ext3)
    or (but that would be strange) by using -t ntfs
    You must always face the curtain with a bow.

  7. #6
    Just Joined!
    Join Date
    Aug 2010
    Posts
    14

    Thumbs up

    Hi Irithori,

    Thanks for your help with this.
    TBH, I have no immediate problems with latency to the NAS as KNOPPIX also seems to see the local drive partitions on the machine the USB is running on so I can always copy the data there if needed.

    To answer your questions tho, I can ping the NAS and the "1" was intentional yes. It's mapped ok second time around as /mnt/nas no problem at all.

    I have to say I agree with you on the confusion re: NTFS/ Ext3. For starters I know it's not NTFS because a) DiskInternals reads it as Ext3, b) the native Windows o/s on my machine asks me to format it as soon as the USB dock powers up and it's listed in Windows' 'Disk Manager' as not an NTFS partition. So I'm not sure really??
    For me this is where the problems start because, I haven't a clue how Western Digital create their Raid Array (this is only 1 of the 2 500Gb drives in the 'dead' NAS' mirrored Raid1).

    I tried as you suggested to mount as 'Ext3' and as 'NTFS' and I got the below answers.
    I guess I should try the same with the 'other' 500Gb drive in tho I have to say I am not hopeful.

    Can you shed any light on the errors below??


    Code:
    knoppix@Microknoppix:~$ sudo su
    root@Microknoppix:/home/knoppix# mkdir /mnt/usbdrive
    root@Microknoppix:/home/knoppix# mount -t ext3 /dev/sdc4 /mnt/usbdrive
    mount: wrong fs type, bad option, bad superblock on /dev/sdc4,
           missing codepage or helper program, or other error
           In some cases useful info is found in syslog - try
           dmesg | tail  or so
    
    root@Microknoppix:/home/knoppix# mount -t ntfs /dev/sdc4 /mnt/usbdrive
    NTFS signature is missing.
    Failed to mount '/dev/sdc4': Invalid argument
    The device '/dev/sdc4' doesn't seem to have a valid NTFS.
    Maybe the wrong device is used? Or the whole disk instead of a
    partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
    root@Microknoppix:/home/knoppix# 

  8. #7
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,410
    The errors mean, that neither the ntfs kernel code, nor the ext3 filesystem kernel code can make sense of that partition.
    Ntfs was expected.
    But ext3 is bad, as this was/is the filesystem used, according to your information.

    You could try ext4
    Code:
    mount -t ext4 /dev/sdc4 /mnt/usbdrive
    or let linux try to figure it out
    Code:
    mount /dev/sdc4 /mnt/usbdrive
    You might also go through the exercise with the other 500GB disc.
    - Unplug the usb device,
    - exchange the discs
    - plug the usb device back in
    - fdisk -l
    - mount...

    But all information up to now rather point to a damaged partition/filesystem.
    One broken raiddisc usually does not cause that kind of damage.
    To be honest, it points to the restore attempts afterwards. Sorry.

    If that it is case, you have two choices:
    a) try to recover yourself
    TestDisk - CGSecurity
    PhotoRec - CGSecurity
    b) ship the discs to a professional restore service
    You must always face the curtain with a bow.

  9. #8
    Just Joined!
    Join Date
    Aug 2010
    Posts
    14
    Interesting news Irithori, please let me know your thoughts.

    Upon plugging in the 'other' 500GB h/d, I can now see that the fdisk -l command now gives the amended line:

    Code:
    /dev/sdc4             506       60801   484327588+  fd  Linux raid autodetect
    When I saw this, I tried again to mount this using the previous commands and bingo, that worked!

    I can now see the drive structure within my KNOPPIX 'explorer' window. Which is definitely further than I've got before.

    (p.s. - at this point could you please give me the commands for 'dismount' and 'deldir' as the 'explorer' does look a bit messy atm!)

    Now I have the 'new' problem that, when I try to open a share within the data structure that was permissioned previously I get a "Error - premission denied".

    I kinda understand that, I assume it means that because I just did a 'standard' mount command without a [username] or [password] (like I did with my 'new' NAS) the old one is only letting me into the 'public' folders that were the drive. I can see the others but I can't browse them.
    Ok, that makes sense.

    Pls can you give me the command to enter a 'username and password' when I mount, so I can mount the drive with the right account which will, I hope!, let me browse the rest of my data...??!

  10. #9
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,410
    Just a thought:
    As the other disc just workd(tm): Maybe you mixed them up?

    Anyway:
    you can use
    umount /mnt/usbdrive
    to (surprise) unmount.

    And
    rm -rf <DIRECTORY>
    to delete directories.
    Needles to say that the last one is to be used with caution.

    As for the permission problem:
    The knoppix user is not the user that was used on the NAS, hence no access.

    A easy way would be to stay on the comandline and copy/rsync with the root user.

    You can use
    Code:
    cp -r /mnt/usbdrive/* <DESTINATIONDIR>
    But this might be a better approach:
    Code:
    rsync -r /mnt/usbdrive/* <DESTINATIONDIR>
    Note:
    - It doesnt really matter, where <DESTINATIONDIR> is. Local disc or new NAS doesnt matter, it just needs to be mounted.
    - Both commands will take a long time.
    You can watch the progress:
    Open another console and type
    Code:
    vmstat 1
    Look for bi and bo (block in, block out)
    I would expect to see about 30MByte/s from the usb drive.
    You must always face the curtain with a bow.

  11. #10
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,410
    While the machine is busy copying, you might want to open yet another console and do
    Code:
    man rsync
    man cp
    man vmstat
    man mount
    man mount.cifs
    to learn, what the h*** you are doing just now

    You can quit the man pages with q.
    Search with /
    You must always face the curtain with a bow.

Page 1 of 3 1 2 3 LastLast

Posting Permissions

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