Hi list,
a harddrive got some bad sectors and now one NILFS filesystem can't be mounted;
mount: /dev/sda3: can't read superblock
I can (try to) copy this filesystem to another drive; how do I proceed form
that point? Does it make any sense to substitute another superblock for this
one?
Hi,
On Mon, 2012-07-23 at 10:45 +0200, dexen deVries wrote:
Hi list,
a harddrive got some bad sectors and now one NILFS filesystem can't be
mounted;
mount: /dev/sda3: can't read superblock
I can (try to) copy this filesystem to another drive; how do I proceed form
that point? Does
Hi Dexen,
On Mon, 2012-07-23 at 11:24 +0200, dexen deVries wrote:
Hi Vyacheslaw,
On Monday 23 of July 2012 13:17:28 you wrote:
It exits second superblock at the end of NILFS volume. But it can be not
in fully synchronous state with primary ones (as I guess).
Theoretically, it is
Hi,
On Mon, 23 Jul 2012 13:17:28 +0400, Vyacheslav Dubeyko wrote:
Hi,
On Mon, 2012-07-23 at 10:45 +0200, dexen deVries wrote:
Hi list,
a harddrive got some bad sectors and now one NILFS filesystem can't be
mounted;
mount: /dev/sda3: can't read superblock
I can (try to)
Hi Ryusuke,
On Monday 23 of July 2012 18:39:07 you wrote:
# mount -t nilfs2 device mount-point
that's what I've tried.
I guess the problem is, the harddrive have not re-allocated the sector as of
yet, so it is /unreadable/ rather than merely containing wrong data.
I'll see later on a
Hi again,
On Monday 23 of July 2012 18:39:07 you wrote:
Looks weird. mount.nilfs2 doesn't output this error message.
another computer, same drive:
coil!root!/mnt # mount.nilfs2 -v /dev/sdc3 x -o errors=continue,norecovery
mount.nilfs2: Error while mounting /dev/sdc3 on x: Input/output error
Hi,
On Mon, 23 Jul 2012 13:06:57 +0200, dexen deVries wrote:
Hi again,
On Monday 23 of July 2012 18:39:07 you wrote:
Looks weird. mount.nilfs2 doesn't output this error message.
another computer, same drive:
coil!root!/mnt # mount.nilfs2 -v /dev/sdc3 x -o errors=continue,norecovery
On Mon, 23 Jul 2012 20:24:10 +0200, dexen deVries wrote:
Hi again,
I've copied the whole filesystem elsewhere (to a file) with `ddrescue'. It
found
one damaged area on the drive, but apparently neither at start nor at the end
of partition.
The FS on the drive was marked as `dirty'
