Raspbian Stretch下自动挂载外置硬盘失败，报Wrong fs type等错误求助

Hey Jordi, let's work through this frustrating fstab auto-mount issue you're facing with your ext4 external drive on Raspbian Stretch. That "Wrong fs type, bad option, bad superblock" error gives us a few clear areas to check—let's go step by step:

1. Double-check the drive is actually formatted as ext4 #

Sometimes formatting can fail silently, or you might be targeting the wrong device entirely. Run this command to verify:

blkid /dev/sdaX

Look for TYPE="ext4" in the output. If it's missing, your drive didn't format correctly. Backup any data first, then re-format with:

sudo mkfs.ext4 /dev/sdaX

2. Audit your fstab entry for syntax/parameter errors #

A tiny typo here can break everything. Your fstab line for an ext4 drive should follow this structure:

UUID=your-drive-uuid /path/to/mountpoint ext4 defaults,uid=www-data,gid=www-data 0 0

Key things to verify:

• You're using the UUID (not /dev/sdaX)—device names can shift after reboots
• The uid/gid values match the actual numbers you retrieved for www-data
• The final two numbers: 0 (disable dump backups) and 0 (skip fsck checks for non-root drives) are correct
• No typos in options (e.g., extra commas, misspelled parameters)

3. Ensure the mount point has proper permissions & ownership #

Even if fstab is correct, a misconfigured mount directory can cause issues. Set the right ownership and permissions with:

sudo chown www-data:www-data /path/to/mountpoint
sudo chmod 755 /path/to/mountpoint

Adjust the permission to 775 if you need www-data to have write access, depending on your use case.

4. Fix a corrupted superblock (if that's the issue) #

The error mentions a bad superblock—ext4 keeps backup superblocks we can use. First, find where the backups are stored:

dumpe2fs /dev/sdaX | grep -i superblock

Then use one of the backup superblocks to run a filesystem check:

sudo umount /dev/sdaX  # Unmount first if possible
sudo e2fsck -b [backup-superblock-number] /dev/sdaX

For example, if the backup is at 32768, run sudo e2fsck -b 32768 /dev/sdaX. Follow the prompts to repair errors.

5. Test mounting with verbose output to pinpoint issues #

Instead of just running mount -a, test the mount directly with verbose mode to get detailed error messages:

sudo mount -v UUID=your-drive-uuid /path/to/mountpoint

The -v flag will show exactly what's failing—whether it's a filesystem type mismatch, invalid option, or superblock problem.

6. Confirm ext4 support is enabled on your system #

While Raspbian Stretch includes ext4 support by default, it's worth checking if the kernel module is loaded:

lsmod | grep ext4

If there's no output, load the module manually:

sudo modprobe ext4

Then retry the mount.

If you still hit issues after these steps, share your exact fstab line and the full verbose error output—we can dig deeper from there!

内容的提问来源于stack exchange，提问作者Jordi Huertas