[opensuse] strange ext4 problem
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Hello, I have a strange ext4 problem. The disk was an old backup I didn't use and just wanted to reuse, but just in case I would like to know how to fix it and see if the disk is not damaged. any hint? thanks jdd dmesg says: EXT4-fs (sdn1): bad geometry: block count 488378390 exceeds size of device (488378389 blocks) notice there is only one block error then: LANG=us ; mount /dev/sdn1 /mnt mount: wrong fs type, bad option, bad superblock on /dev/sdn1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. fsck.ext4 /dev/sdn1 e2fsck 1.42.11 (09-Jul-2014) The filesystem size (according to the superblock) is 488378390 blocks The physical size of the device is 488378389 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? no sauvegarde-2t 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 sauvegarde-2t: 957175/122101760 files (0.9% non-contiguous), 453175967/488378390 blocks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
On Fri, Jan 15, 2016 at 11:27 AM, jdd
fsck.ext4 /dev/sdn1 e2fsck 1.42.11 (09-Jul-2014) The filesystem size (according to the superblock) is 488378390 blocks The physical size of the device is 488378389 blocks
fdisk -l /dev/sdn would be useful here. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Le 15/01/2016 10:02, Andrei Borzenkov a écrit :
On Fri, Jan 15, 2016 at 11:27 AM, jdd
wrote: fsck.ext4 /dev/sdn1 e2fsck 1.42.11 (09-Jul-2014) The filesystem size (according to the superblock) is 488378390 blocks The physical size of the device is 488378389 blocks
fdisk -l /dev/sdn would be useful here.
Disk /dev/sdn: 1.8 TiB, 2000398931968 bytes, 3907029164 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 Disklabel type: dos Disk identifier: 0x703d7f42 Device Boot Start End Sectors Size Id Type /dev/sdn1 2048 3907029167 3907027120 1.8T 83 Linux I can change the partition table, but can this solve the problem? looks like the partition size is in the superblock? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/b4047644c59f2d63b88e9464c02743fd.jpg?s=120&d=mm&r=g)
On January 15, 2016 12:27:50 AM PST, jdd
Hello,
I have a strange ext4 problem. The disk was an old backup I didn't use and just wanted to reuse, but just in case I would like to know how to fix it and see if the disk is not damaged.
any hint? thanks jdd
dmesg says:
EXT4-fs (sdn1): bad geometry: block count 488378390 exceeds size of device (488378389 blocks)
notice there is only one block error
then:
LANG=us ; mount /dev/sdn1 /mnt mount: wrong fs type, bad option, bad superblock on /dev/sdn1, missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so.
fsck.ext4 /dev/sdn1 e2fsck 1.42.11 (09-Jul-2014) The filesystem size (according to the superblock) is 488378390 blocks The physical size of the device is 488378389 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? no sauvegarde-2t 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 sauvegarde-2t: 957175/122101760 files (0.9% non-contiguous), 453175967/488378390 blocks
Do you care at this point? About data recovery I mean? What does SMART say? Are all spare sectors assigned? If not, I'd nuke it, define the whole thing as a new partition, format, then run diagnostics. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/9c06031aaadda145089b2480338feb86.jpg?s=120&d=mm&r=g)
Dne Pá 15. ledna 2016 09:27:50, jdd napsal(a):
I have a strange ext4 problem. The disk was an old backup I didn't use and just wanted to reuse, but just in case I would like to know how to fix it and see if the disk is not damaged.
any hint?
testdisk can tell a lot about the partition layout (even in case of broken discs) and possibly restore wrong/damaged/lost partitions. But before any manipulation - if there are valuable data - I'd make backup with dd. HTH, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Well. Problem solved. looks like it was a hardware problem, not on the disk but on the usb link. I plugged this (usb3) device in an external hub, and the system didn't like it. My usb3 link is already an extension card plugged in pci-e port. Usb3 usually works with disks, but not there. I discovered this trying an other dock and plugin it directly on the back of the computer. Very curious error though. I don't catch how an usb error can drive to a disk size error. so good thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
jdd composed on 2016-01-15 10:52 (UTC+0100):
I don't catch how an usb error can drive to a disk size error.
Years ago I remember similar vexation trying to move PATA disks between PC's onboard controllers and USB docks. Only thing I can think of is there must be some kind of interpretation or translation going on in the docking device's firmware before data is passed to the USB bus, affecting interpretation of partition table logical "geometry" that gets it out of sync with sector count. But, by only one block out of 488378389? Sheesh. :-p -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 01/15/2016 11:51 AM, Felix Miata wrote:
jdd composed on 2016-01-15 10:52 (UTC+0100):
I don't catch how an usb error can drive to a disk size error.
Years ago I remember similar vexation trying to move PATA disks between PC's onboard controllers and USB docks. Only thing I can think of is there must be some kind of interpretation or translation going on in the docking device's firmware before data is passed to the USB bus, affecting interpretation of partition table logical "geometry" that gets it out of sync with sector count. But, by only one block out of 488378389? Sheesh. :-p
Maybe a bug in the USB dock firmware (off by one). Or a size limitation, which actually happens quite often. There is translation involved. Sometimes it changes reported sector size, I heard. -- Cheers/Saludos Carlos E. R. (openSUSE Leap 42.1, test at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Andrei Borzenkov
-
Carlos E. R.
-
Felix Miata
-
jdd
-
John Andersen
-
Vojtěch Zeisek