Re: fsck: CANNOT READ: BLK 4235468160

Op Sun, 07 Jan 2018 03:45:06 +0100 schreef Maximilian Pichler : If the disk is damaged, shouldn't the problematic blocks be consistent? If you mean the actual platters, then probably yes, but there are other components that can damage. If for instance the bearings

Re: fsck: CANNOT READ: BLK 4235468160

I just saw you mentioned you are using the disk inside of virtualbox. Does this same thing happen if you use the disk natively? On Mon, Jan 8, 2018 at 8:52 AM Matt M wrote: > With disks, the blocks can change. There can be any number of reasons for > this, from the actual

Re: fsck: CANNOT READ: BLK 4235468160

With disks, the blocks can change. There can be any number of reasons for this, from the actual physical platters going bad to the read heads not functioning properly, or the memory on the disk going bad. SSD is a different story, in my experience when it begins to go the behavior becomes really

Re: fsck: CANNOT READ: BLK 4235468160

When you enter the realm of hardware errors, anything can happen. If you are lucky you will see the same hard and soft errors every time you cross a bad sector, but I have seen many cases wildly varying block numbers on really sick disks. And yes, bad cables and USB interfaces can be a

fsck: CANNOT READ: BLK 4235468160

Hi, I'm running fsck on an external USB hard drive, using OpenBSD 6.2 inside VirtualBox on MacOS. On each run it gives a handful of "CANNOT READ: BLK ..." messages, but the block numbers reported are different (!) each time. If the disk is damaged, shouldn't the problematic blocks be