Hi everyone:
I have an Ultra Fit 3.1 Gen1 USBFD that I use for storing logs and software for my (Linux-based) router. (I have very very little knowledge of Linux). It barely gets any activity, since logging is such a low data activity. However, a recent test done via the router output the following:
root@router:/tmp/home/root# fsck.ext4 /dev/sda1
e2fsck 1.47.0 (5-Feb-2023)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sda1
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>
Fdisk showed the following partition data on the flash drive before I ran the test:
root@router:/tmp/home/root# fdisk /dev/sda
The number of cylinders for this disk is set to 7480.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sda: 57 GB, 61530439680 bytes, 120176640 sectors
7480 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sda1 0,1,1 1023,254,63 63 58368062 58368000 27.8G 83 Linux
/dev/sda2 1023,254,63 1023,254,63 58368063 120176639 61808577 29.4G 83 Linux
I spoke with a rep. at Sandisk, and he claimed that this was probably caused by my creating more than one partition on the drive. Their drives, he said, "aren't made to handle more than on partition". That sounded like bullsh*t to me. I asked him for documentation as proof of his claim. So far, no proof.
He told me to repartition it with one partition only, and reformat. I did that. I'm running h2testw on it right now.
Can partitioning a Sandisk flash drive cause bad blocks, as Sandisk claims?
I have an Ultra Fit 3.1 Gen1 USBFD that I use for storing logs and software for my (Linux-based) router. (I have very very little knowledge of Linux). It barely gets any activity, since logging is such a low data activity. However, a recent test done via the router output the following:
root@router:/tmp/home/root# fsck.ext4 /dev/sda1
e2fsck 1.47.0 (5-Feb-2023)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sda1
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>
Fdisk showed the following partition data on the flash drive before I ran the test:
root@router:/tmp/home/root# fdisk /dev/sda
The number of cylinders for this disk is set to 7480.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sda: 57 GB, 61530439680 bytes, 120176640 sectors
7480 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sda1 0,1,1 1023,254,63 63 58368062 58368000 27.8G 83 Linux
/dev/sda2 1023,254,63 1023,254,63 58368063 120176639 61808577 29.4G 83 Linux
I spoke with a rep. at Sandisk, and he claimed that this was probably caused by my creating more than one partition on the drive. Their drives, he said, "aren't made to handle more than on partition". That sounded like bullsh*t to me. I asked him for documentation as proof of his claim. So far, no proof.
He told me to repartition it with one partition only, and reformat. I did that. I'm running h2testw on it right now.
Can partitioning a Sandisk flash drive cause bad blocks, as Sandisk claims?
Last edited: