ext2fsd problem

[symon6]

Zdravim, nakolko väcsinu casu travim uz v Ubuntu, tak som si zmenil FS na externom HDD na ext4. Problém nastal az v tedy, ked som musel môj ntb odovzdat do servisu a docasne som presiel na Win7, ten ext4 nevie bezne precitat, tak som pouzil nastroj ext2fsd aby som mohol pristupovat k datam aj na Win. Problem nastal az teraz, ked som cez live USB spustil Ubuntu 14.04 a externý sa mi zrazu nepodarilo nacitat. Gparted nevie na zariadeni najst ziadnu particiu a mount /dev/sdb /mnt -t ext4 hlasi:

mount: wrong fs type, bad option, bad superblock on /dev/sdb,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

fsck /dev/sdb:

fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
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>
 or
    e2fsck -b 32768 <device>

Skusal som pouzit aj alternativne superbloky ale bez uspechu. Co je ale najdivnejsie tak vo Win cez ext2fsd sa mi stále dá bez problemov pristupovat k datam.

[ntz_reloaded]

ono to nebude urcite dev/sdb ale patrne /dev/sdb1 a nebo vyssi ..

/dev/sdb jako takove je primo odkaz na cely ten raw disk .. na mem mas vytvorene nejake oddily (sda1, sda5, sdaX) a ty mas zformatovane a pripojujes ..

podivej na disk (jako root) pomoci `fdisk -l /dev/sdb' a pomoci `blkid | grep sdb'

[symon6]

ono to nebude urcite dev/sdb ale patrne /dev/sdb1 a nebo vyssi ..

/dev/sdb jako takove je primo odkaz na cely ten raw disk .. na mem mas vytvorene nejake oddily (sda1, sda5, sdaX) a ty mas zformatovane a pripojujes ..

podivej na disk (jako root) pomoci `fdisk -l /dev/sdb' a pomoci `blkid | grep sdb'

 sudo fdisk -l /dev/sdb:

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1   976773167   488386583+  ee  GPT

sudo mount /dev/sdb1 /mnt

mount: special device /dev/sdb1 does not exist

sudo fsck /dev/sdb1

fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
fsck.ext2: No such file or directory while trying to open /dev/sdb1
Possibly non-existent device?

blkid mi ziadne sdb zariadenie ani nenaslo:

/dev/loop0: TYPE="squashfs"
/dev/loop1: LABEL="casper-rw" UUID="0a1cb875-b194-8743-b0b8-f4c36bf6fb69" TYPE="ext2"
/dev/sda1: LABEL="VyhradenM-CM-) systM-CM-)mom" UUID="560C8F3E0C8F185F" TYPE="ntfs"
/dev/sda2: UUID="BE209B64209B2307" TYPE="ntfs"
/dev/sda3: UUID="06C0565EC05653D1" TYPE="ntfs"
/dev/sdc1: LABEL="UUI" UUID="BAB5-0553" TYPE="vfat"
ubuntu@ubuntu:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/loop1: LABEL="casper-rw" UUID="0a1cb875-b194-8743-b0b8-f4c36bf6fb69" TYPE="ext2"
/dev/sda1: LABEL="VyhradenM-CM-) systM-CM-)mom" UUID="560C8F3E0C8F185F" TYPE="ntfs"
/dev/sda2: UUID="BE209B64209B2307" TYPE="ntfs"
/dev/sda3: UUID="06C0565EC05653D1" TYPE="ntfs"
/dev/sdc1: LABEL="UUI" UUID="BAB5-0553" TYPE="vfat"
ubuntu@ubuntu:~$ sudo blkid | grep sdb
ubuntu@ubuntu:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/loop1: LABEL="casper-rw" UUID="0a1cb875-b194-8743-b0b8-f4c36bf6fb69" TYPE="ext2"
/dev/sda1: LABEL="VyhradenM-CM-) systM-CM-)mom" UUID="560C8F3E0C8F185F" TYPE="ntfs"
/dev/sda2: UUID="BE209B64209B2307" TYPE="ntfs"
/dev/sda3: UUID="06C0565EC05653D1" TYPE="ntfs"
/dev/sdc1: LABEL="UUI" UUID="BAB5-0553" TYPE="vfat"

[ntz_reloaded]

pise ti to tam .. ten disk je GPT a ne normalni .. nevim, jak presne se ubuntu chova s gpt

[ntz_reloaded]

ted jen abych te neosidil jsem to zkusil u sebe .. vytvoril jsem si disk formatovanej pomoci gpt ..

Kód: [Vybrat]

# fdisk -l /dev/loop0
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.

Disk /dev/loop0: 134 MB, 134217728 bytes, 262144 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt


#         Start          End    Size  Type            Name
 1         2048        51199     24M  Linux filesyste Linux filesystem
 2        51200       262110    103M  Linux LVM       Linux LVM

# gdisk -l /dev/loop0
GPT fdisk (gdisk) version 0.8.7

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/loop0: 262144 sectors, 128.0 MiB
Logical sector size: 512 bytes
Disk identifier (GUID): 43645AA2-A756-4FE2-B355-ED8D47073CDA
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 262110
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048           51199   24.0 MiB    8300  Linux filesystem
   2           51200          262110   103.0 MiB   8E00  Linux LVM
a nem si udelal v prvnim oddilu ntfs a ve druhem oddilu lvm a v nem jeden oddil "test" .. oba jsem pripojil:

Kód: [Vybrat]

# mount | grep loop
/dev/mapper/loopy-test on /mnt/tmp type ext4 (rw,relatime,data=ordered)
/dev/mapper/loop0p1 on /mnt/iso2 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
nevim proc to u tebe nefunguje .. me normalne blkid vypisuje i ten samotnej raw disk (u me /dev/loop0 alias /dev/sdb u tebe, nenech se mast nulou na konci u me)

Kód: [Vybrat]

# blkid | grep loop
/dev/loop0: PTTYPE="gpt"
/dev/mapper/loop0p1: LABEL="ntfs test" UUID="6FB57F6A2E566629" TYPE="ntfs" PARTLABEL="Linux filesystem" PARTUUID="77065763-5b8e-479b-9d06-d95fcd55d159"
/dev/mapper/loop0p2: UUID="4luhwz-llX9-vcxB-Tcr6-jiJO-1qi6-M98YwR" TYPE="LVM2_member" PARTLABEL="Linux LVM" PARTUUID="c98d8b36-6e51-42fa-a42c-7a6791fde710"
/dev/mapper/loopy-test: UUID="74720107-12f7-41f2-b996-2184e6976085" TYPE="ext4"
zkus sem dat prosim vystup z:

Kód: [Vybrat]

kpartx -vl /dev/sdb

[symon6]

Kód: [Vybrat]

ubuntu@ubuntu:~$ sudo kpartx -vl /dev/sdb
Primary GPT is invalid, using alternate GPT.
sdb1 : 0 976771072 /dev/sdb 2048


[ntz_reloaded]

zkus zadat `kpartx -va /dev/sdb', to by melo to sdb1 zpristupnit a napsat ti neco podobneho jak u me:

Kód: [Vybrat]

# kpartx -vl /dev/loop0
loop0p1 : 0 49152 /dev/loop0 2048
loop0p2 : 0 210911 /dev/loop0 51200


# kpartx -va /dev/loop0
add map loop0p1 (253:4): 0 49152 linear /dev/loop0 2048
add map loop0p2 (253:5): 0 210911 linear /dev/loop0 51200


# ls -l /dev/mapper/loop0p*
lrwxrwxrwx 1 root root 7 Jul 13 17:00 /dev/mapper/loop0p1 -> ../dm-4
lrwxrwxrwx 1 root root 7 Jul 13 17:00 /dev/mapper/loop0p1_part1 -> ../dm-4
lrwxrwxrwx 1 root root 7 Jul 13 17:00 /dev/mapper/loop0p2 -> ../dm-5
lrwxrwxrwx 1 root root 7 Jul 13 17:00 /dev/mapper/loop0p2_part2 -> ../dm-5
potom to normalne pripoj .. ja us sebe bych napsal ``mount -vv /dev/mapper/loop0p1 /mnt/tmp'' a mel bych to pripojene do /mnt/tmp .. ty samozrejme dosad spravny /dev/mapper/* soubor a nejaky pripojny bod ktery existuje ..

[symon6]

Ďakujem, posledný spôsob funguje. Po zadaní, mi uz particiu rozozná nautilus, avšak problem je v tom, že po jeho odpojeni a opätovnom pripojeni treba postup opakovať. Bolo by teda možné upraviť to nastálo? Poprípade vyriesiť problem, ktory to sposobuje. Najlepsie bez straty dát.

[ntz_reloaded]

bohuzel tohle nevim .. je to spis otazka, jak je nastavene prostredi (tedy ted unity/gnome) jestli spravne rozeznava gpt a jestli ubunti automounter take sleduje /dev/mapper zarizeni ..

snad ti nekdo zkusenejsi s ubuntu poradi .. sam (bohuzel) pouzivam opensuse a kde a tady to proste funguje samo .. nikdy jsem to neohledaval, ted jsem to akorat vyzkousel s tim gpt a slo to opet samo .. tu rucni metodu s kpartx jsem ti samozrejme napsal jako manualni reseni ..

zdravim