Register a domain and help support LQ
Go Back > Forums > Linux Forums > Linux - Distributions > Ubuntu
User Name
Ubuntu This forum is for the discussion of Ubuntu Linux.


Search this Thread
Old 10-20-2011, 04:42 PM   #1
LQ Newbie
Registered: May 2006
Posts: 3

Rep: Reputation: 0
bad superblock while mounting SD card (Ubuntu 10.04)

I haven't had any problems mounting my 256mb SD card until today. I'm using an internal card reader. When I plug it in, the light blinks but nothing happens onscreen.

Here are some error messages/output:

# dmesg

[644755.383793] sd 3:0:0:0: [sdc] Device not ready
[644755.383806] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[644755.383816] sd 3:0:0:0: [sdc] Sense Key : Not Ready [current]
[644755.383829] Info fld=0x0
[644755.383835] sd 3:0:0:0: [sdc] <<vendor>> ASC=0xff ASCQ=0xffASC=0xff <<vendor>> ASCQ=0xff
[644755.383863] sd 3:0:0:0: [sdc] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[644755.383886] end_request: I/O error, dev sdc, sector 0
[644755.383900] Buffer I/O error on device sdc, logical block 0

# ls /dev
adsp dri fd0u1840 loop3 parport0 ram3 sda2 snapshot tty15 tty3 tty44 tty59 usbmon2 vcsa6
agpgart dsp fd0u1920 loop4 pktcdvd ram4 sda3 snd tty16 tty30 tty45 tty6 vcs vcsa7
audio dvd2 fd0u360 loop5 port ram5 sdc sndstat tty17 tty31 tty46 tty60 vcs1 vcsa8
block dvdrw2 fd0u720 loop6 ppp ram6 sdd sr0 tty18 tty32 tty47 tty61 vcs2 vga_arbiter
bsg ecryptfs fd0u800 loop7 psaux ram7 sde sr1 tty19 tty33 tty48 tty62 vcs3 zero
bus fb0 fd0u820 lp0 ptmx ram8 sdf stderr tty2 tty34 tty49 tty63 vcs4
cdrom fd fd0u830 mapper pts ram9 sequencer stdin tty20 tty35 tty5 tty7 vcs5
cdrom2 fd0 full mcelog ram0 random sequencer2 stdout tty21 tty36 tty50 tty8 vcs6
cdrw fd0u1040 fuse mem ram1 rfkill sg0 tty tty22 tty37 tty51 tty9 vcs7
cdrw2 fd0u1120 hpet midi ram10 root sg1 tty0 tty23 tty38 tty52 ttyS0 vcs8
char fd0u1440 input mixer ram11 rtc sg2 tty1 tty24 tty39 tty53 ttyS1 vcsa
console fd0u1600 kmsg net ram12 rtc0 sg4 tty10 tty25 tty4 tty54 ttyS2 vcsa1
core fd0u1680 log network_latency ram13 scd0 sg5 tty11 tty26 tty40 tty55 ttyS3 vcsa2
cpu_dma_latency fd0u1722 loop0 network_throughput ram14 scd1 sg6 tty12 tty27 tty41 tty56 urandom vcsa3
disk fd0u1743 loop1 null ram15 sda sg7 tty13 tty28 tty42 tty57 usbmon0 vcsa4
dmmidi fd0u1760 loop2 oldmem ram2 sda1 shm tty14 tty29 tty43 tty58 usbmon1 vcsa5

# more /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=32560173-d629-4e60-9d62-9ef496a61b97 / ext3 errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=5655bef6-584a-44c2-b4be-50eb6e3036b1 /home ext4 defaults 0 2
# swap was on /dev/sda2 during installation
UUID=40bd2341-a312-4486-bef7-35f06d954864 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

# mount
/dev/sda1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
/dev/sda3 on /home type ext4 (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/robert/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=robert)

# more /proc/mounts
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
none /dev devtmpfs rw,relatime,size=249792k,nr_inodes=62448,mode=755 0 0
none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
/dev/disk/by-uuid/32560173-d629-4e60-9d62-9ef496a61b97 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
none /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/kernel/security securityfs rw,relatime 0 0
none /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
none /var/run tmpfs rw,nosuid,relatime,mode=755 0 0
none /var/lock tmpfs rw,nosuid,nodev,noexec,relatime 0 0
none /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
/dev/sda3 /home ext4 rw,relatime,barrier=1,data=ordered 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0
gvfs-fuse-daemon /home/robert/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0

# mke2fs -n /dev/sdc
mke2fs 1.41.11 (14-Mar-2010)
/dev/sdc is entire device, not just one partition!
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
62496 inodes, 249856 blocks
12492 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67371008
31 block groups
8192 blocks per group, 8192 fragments per group
2016 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185

# dumpe2fs -o superblock=8193 /dev/sdc
dumpe2fs 1.41.11 (14-Mar-2010)
dumpe2fs: Invalid argument while trying to open /dev/sdc
Couldn't find valid filesystem superblock.

#e2fsck -b 8193 /dev/sdc
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Invalid argument while trying to open /dev/sdc

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
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>

# fsck /dev/sdc
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdc
Could this be a zero-length partition?

# dosfsck /dev/sdc
dosfsck 3.0.7, 24 Dec 2009, FAT32, LFN
Read 512 bytes at 0:Input/output error

The only recent change to my system that I can remember is that I started to try networking my windows box to my linux box with the following:

sudo apt-get install smbfs
# update-rc.d -f remove
# update-rc.d stop 15 0 6 .
# gedit .smbcredentials
# chown root .smbcredentials
# chmod 600 .smbcredentials

(based on advice at
Old 10-20-2011, 04:58 PM   #2
LQ Newbie
Registered: May 2006
Posts: 3

Original Poster
Rep: Reputation: 0
restarting Ubuntu solved the problem

I suspect that I had stopped an important filesystem service when I was trying to setup samba.



Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem mounting CD-ROM: wrong fs type, bad option, bad superblock on /dev/cdrom Oooska Linux - Newbie 7 07-10-2013 11:37 AM
Mounting Drive Bad Superblock Error Wraith86 Linux - Server 1 06-16-2010 06:27 AM
ERROR AT MOUNTING USB :mount: wrong fs type, bad option, bad superblock on /dev/sda1, saiket Linux - Hardware 3 04-12-2008 12:07 AM
Bad superblock when mounting hard drive... SamJ Linux - Hardware 5 06-04-2005 07:32 PM
trouble mounting drive, bad superblock error mattuc Linux - Hardware 3 05-27-2004 10:05 AM

All times are GMT -5. The time now is 06:03 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration