Přidat otázku mezi oblíbenéZasílat nové odpovědi e-mailem Ako opravit pristup k iscsi targetu (linux)

Testdisk som pouzil, bohuzial particiu som opravoval z prostredia windows, pretoze Testdisk zlyhal (hlasil len 128MB win particiu, netusim preco).

btw co je v syslogu, jak ti to navrhuje použít dmesg?

dmesg | tail
[73290687.288078] sdb: sdb1
[73290687.293773] sdc: sdc1
[73290714.102528] EXT4-fs (sdb1): bad geometry: block count 625454347 exceeds size of device (536870911 blocks)
[73290769.640397] EXT4-fs (sdb1): bad geometry: block count 625454347 exceeds size of device (536870911 blocks)
[73291681.284946] EXT4-fs (sdb1): bad geometry: block count 625454347 exceeds size of device (536870911 blocks)
[73292314.359386] EXT4-fs (sdb1): bad geometry: block count 625454347 exceeds size of device (536870911 blocks)
[73298212.165602] EXT4-fs (sdb1): bad geometry: block count 625454347 exceeds size of device (536870911 blocks)
[73298224.390040] EXT4-fs (sdb1): bad geometry: block count 625454347 exceeds size of device (536870911 blocks)
[73298424.672729] EXT4-fs (sdb1): bad geometry: block count 625454347 exceeds size of device (536870911 blocks)
[73300427.051584] EXT4-fs (sdb1): bad geometry: block count 625454347 exceeds size of device (536870911 blocks)

Takze on tvrdi, co je v poriadku, ze ten disk je vacsi ako particia (sdb1 ma 2TB, sdb ma 2.3TB). Neviem preco mu to vsak vadi.
fsck zlyha asi takto.

fsck /dev/sdb1
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
The filesystem size (according to the superblock) is 625454347 blocks
The physical size of the device is 536870911 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no
/dev/sdb1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Error reading block 536870912 (Invalid argument) while reading inode and block bitmaps. Ignore error<y>?

A dalej uz hlasi jednotlive bloky ako vadne az kym fsck nezrusi. A je jedno, ci ich opravujem alebo nie.

Z windows tam lezeš jak, skrz ten Linux?

Nie, cez vpn sa dostanem na lanku a spustim iscsi iniciator a cez neho si mountnem disk.
Problemom je, ze ide o LUN blok, ktory samotne NASko vidi ako zvazok/disk a nema k nemu pristup, takze zo samotneho NASka neviem spravit s diskom nic a vsetko musim riesit cez iscsi klientov (velkost, file system a pod). Poslal som sice poziadavku aj na support QNAPu, ale tipujem, ze ma poslu do pecka, ze to mozne nie je. Ide totizto o enterprise model a paradoxne v lacnejsich modeloch by to slo cez pripnutie virtualneho disku (robil by sam sebe aj iscsi iniciatora aj target).

Reakce na odpověď

1 Zadajte svou přezdívku:
2 Napište svou odpověď:
3 Pokud chcete dostat ban, zadejte libovolný text:

Zpět do poradny