[an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]
 
[an error occurred while processing this directive] [an error occurred while processing this directive]
Skåne Sjælland Linux User Group - http://www.sslug.dk Home   Subscribe   Mail Archive   Forum   Calendar   Search
MhonArc Date: [Date Prev] [Date Index] [Date Next]   Thread: [Date Prev] [Thread Index] [Date Next]   MhonArc
 

Re: [TEKNIK] PANIK HJÆLP jeg kan ikke f å adgang til mit data?



On 2011-06-05 21:28, Lasse Jensen wrote:
> Hej Group
> 
> Jeg kan ikke få adgang til mit  data...
> har lige købt en stor USB 1.5Tb disk i aldi...

usb 3.0 eller 2.0 ?
har den E-SATA stik også ?

> laver et filsystem med mkfs.ext4
> kopiere mit data
> sammenligner der hele med diff
> alt ok

hmm, måske den er gal her.
havde du prøvet umount og mount igen for at se det virkede?

> 
> dagen efter skal jeg lige ha' lidt data ud af disken og over i en windows7 box jeg har,
> tænker at "DiskInternals Linux Reader" måske lige kan klare sagen, men desværre.

aner ikke hvad det er (Diskinternals).

> så prøver jeg Ext2fsd, men heller ikke dette tool kan få adgang til mit data. det skal

kender ikke ext2fsd, men  ok http://www.ext2fsd.com/
skriver noget om nyeste version godt kan ext4

> nævnes at windows jo popper op med "ny disk indsat, skal den formateres" og naturligvis
> svare jeg NEJ TAK, og naturligvis sidder jeg ikke i 3 timer og fisker rundt med
> "DiskInternals Linux Reader" eller "Ext2fsd" i write mode, jeg går naturligvis forsigtigt
> tilværks.
> men jeg ved ikke om der kan være gået noget galt under denne windows session.

Dvs. du har formateret med ext4 og vil have windows til at læse data  ?
uha, jeg ville nok først eksperimentere en del med en kladde-disk
inden jeg bruger det "live" på vigtige data.


> men jeg skulle jo ha' noget af mit data over på denne windows box, og da jeg ikke direkte
> kan få dataen igennem USB til windows boxen må jeg jo mounte den under en linux og
> overføre mit data via net CIFS eller ligende.
> men på min linux laptop kan jeg nu heller ikke få adgang til mit data...
> PLEASE HJÆLP MIG ANYONE... jeg ved dataen ligger der...

Jeg har brugt  http://www.fs-driver.org/ til windows
men den kan kun ext2 (udvikling vist gået i stå)
Til gengæld har den virket stabilt igennem flere år.

> 
> her kommer en command historik...
> 
> sslug@sslug:~# dmesg
> [ 3799.732055] usb 1-5: new high speed USB device using ehci_hcd and address 11
> [ 3799.982905] scsi8 : usb-storage 1-5:1.0
> [ 3812.498973] scsi 8:0:0:0: Direct-Access     WDC WD15 EARS-22MVWB0  51.0 PQ: 0 ANSI: 0
> [ 3812.500306] sd 8:0:0:0: Attached scsi generic sg0 type 0
> [ 3812.511018] sd 8:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
> [ 3812.514510] sd 8:0:0:0: [sda] Write Protect is off
> [ 3812.514519] sd 8:0:0:0: [sda] Mode Sense: 23 00 00 00
> [ 3812.514527] sd 8:0:0:0: [sda] Assuming drive cache: write through
> [ 3812.518521] sd 8:0:0:0: [sda] Assuming drive cache: write through
> [ 3812.518545]  sda: sda1
> [ 3812.548502] sd 8:0:0:0: [sda] Assuming drive cache: write through
> [ 3812.548518] sd 8:0:0:0: [sda] Attached SCSI disk
> [ 3812.660984] sd 8:0:0:0: [sda] Sense Key : Recovered Error [current] [descriptor]
> [ 3812.661003] Descriptor sense data with sense descriptors (in hex):
> [ 3812.661009]         72 01 04 1d 00 00 00 0a 09 0c 00 00 00 00 00 07
> [ 3812.661035]         00 00
> [ 3812.661043] sd 8:0:0:0: [sda] ASC=0x4 ASCQ=0x1d

hmm ikke så godt med den type fejl på disken.
eller det er USB interface fejl

gør den det i log på alle computere?

hvad siger windows logbog ?



> ***
> 
> sslug@sslug:~# fdisk /dev/sda
> 
> WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
>          switch off the mode (command 'c') and change display units to
>          sectors (command 'u').
> 
> Kommando (m for hjælp): p
> 
> Disk /dev/sda: 1500.3 Gb, 1500301910016 byte
> 255 heads, 63 sectors/track, 182401 cylinders
> Units = cylindre of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x484516fa
> 
>     Enhed Opstart   Start         Slut     Blokke   Id  System
> /dev/sda1               1      182401  1465136001   83  Linux
> 
> Kommando (m for hjælp):
> 
> ***

fdisk -l /dev/sda ???

du har kun en disk i systemet;  din USB disk?
siden den hedder sda?




> 
> sslug@sslug:~# mount /dev/sda1 /mnt/USB
> mount: du skal angive filsystemtypen
> sslug@sslug:~# mount -t ext4 /dev/sda1 /mnt/USB
> mount: wrong fs type, bad option, bad superblock on /dev/sda1,
>        missing codepage or helper program, or other error
>        I nogle tilfælde vil du finde nyttige oplysninger i systemlogggen
>        - prøv 'dmesg | tail'  eller lignende
> 
> ***
> 
> sslug@sslug:~# fsck.ext4 /dev/sda1
> e2fsck 1.41.12 (17-May-2010)
> fsck.ext4: Superblock invalid, trying backup blocks...
> fsck.ext4: Bad magic number in super-block while trying to open /dev/sda1
> 
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
>     e2fsck -b 8193 <device>
> 
> ***

ok , fsck.ext4 er "lidt" utilfreds med systemet.

> 
> sslug@sslug:~# mkfs.ext4 -n /dev/sda1
> mke2fs 1.41.12 (17-May-2010)


nu har du formateret /dev/sda1

> 
> sslug@sslug:~# fsck.ext4 -b 32768 /dev/sda1
> e2fsck 1.41.12 (17-May-2010)
> fsck.ext4: Bad magic number in super-block while trying to open /dev/sda1
> 
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
>     e2fsck -b 8193 <device>
> 
> ***
> 
> sslug@sslug:~# fsck.ext4 -b 229376 /dev/sda1
> e2fsck 1.41.12 (17-May-2010)
> fsck.ext4: Bad magic number in super-block while trying to open /dev/sda1
> 
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
>     e2fsck -b 8193 <device>
> 

noget er galt med /dev/sda1

prøv std. ext2/3 formatering i stedet med f.eks. mke2fs


Hvilken linux distribution anvender du?


prøv evt. først en badblocks på enheden for at sikre dig
at disk virker og usb-enhed virker.



 
Home   Subscribe   Mail Archive   Index   Calendar   Search

 
 
Questions about the web-pages to <www_admin>. Last modified 2011-07-01, 02:01 CEST [an error occurred while processing this directive]
This page is maintained by [an error occurred while processing this directive]MHonArc [an error occurred while processing this directive] # [an error occurred while processing this directive] *