Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
microsd not showing full capacity / dd failure with Raspbian
microsd not showing full capacity / dd failure with Raspbian
Why is my microSD card showing a smaller size with fdisk then lsblk?
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 2.2G 0 loop /mnt2
sda 8:0 0 477G 0 disk
├─sda1 8:1 0 460.3G 0 part /
└─sda2 8:2 0 16.6G 0 part [SWAP]
mmcblk0 179:256 0 59.5G 0 disk
└─mmcblk0p1 179:257 0 59.5G 0 part
root@t460:~# fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 7.5 GiB, 8076152832 bytes, 15773736 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
I'm trying to copy Raspbian img over, but it's failing:
root@t460:/home/awright/Downloads# dd if=2019-09-26-raspbian-buster-lite.img of=/dev/mmcblk0p1
dd: writing to '/dev/mmcblk0p1': Input/output error
3418113+0 records in
3418112+0 records out
1750073344 bytes (1.8 GB, 1.6 GiB) copied, 582.939 s, 3.0 MB/s
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 2.2G 0 loop /mnt2
sda 8:0 0 477G 0 disk
├─sda1 8:1 0 460.3G 0 part /
└─sda2 8:2 0 16.6G 0 part [SWAP]
mmcblk0 179:256 0 59.5G 0 disk
└─mmcblk0p1 179:257 0 59.5G 0 part
root@t460:~# fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 7.5 GiB, 8076152832 bytes, 15773736 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
I'm trying to copy Raspbian img over, but it's failing:
root@t460:/home/awright/Downloads# dd if=2019-09-26-raspbian-buster-lite.img of=/dev/mmcblk0p1
dd: writing to '/dev/mmcblk0p1': Input/output error
3418113+0 records in
3418112+0 records out
1750073344 bytes (1.8 GB, 1.6 GiB) copied, 582.939 s, 3.0 MB/s
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 133 times
Re: microsd not showing full capacity / dd failure with Rasp
Looks like it might be broken, does it work with other devices?ovitus wrote:Code: Select all
dd: writing to '/dev/mmcblk0p1': Input/output error
Try https://packages.debian.org/buster/f3
deadbang
-
- Emeritus
- Posts: 2435
- Joined: 2010-12-07 19:55
- Has thanked: 14 times
- Been thanked: 54 times
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 133 times
Re: microsd not showing full capacity / dd failure with Rasp
That was my first thought as well but the OP appears to be trying to burn a Raspbian image to the SD card from Debian so the thread is appropriate here IMO.arochester wrote:Raspberry Pi Forums
deadbang
Re: microsd not showing full capacity / dd failure with Rasp
I posted on the Raspberry Pi forums also. I can't mount the drive to test with F3:
root@t460:/home/awright/Downloads# mount /dev/mmcblk0p1 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1, missing codepage or helper program, or other error.
root@t460:/home/awright/Downloads# mount /dev/mmcblk0p1 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1, missing codepage or helper program, or other error.
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 133 times
Re: microsd not showing full capacity / dd failure with Rasp
Yeah that looks dead to me.
We could check the filesystem:
Then make sure the appropriate filesystem tools are installed (for example, e2fsprogs for ext{2,3,4}) so you can try again if they aren't but I wouldn't hold out much hope.
We could check the filesystem:
Code: Select all
/sbin/wipefs /dev/mmcblk0p1
deadbang
-
- Global Moderator
- Posts: 3049
- Joined: 2017-09-17 07:12
- Has thanked: 5 times
- Been thanked: 132 times
Re: microsd not showing full capacity / dd failure with Rasp
Without even checking the kernel logs with dmesg ?Head_on_a_Stick wrote:Yeah that looks dead to me.
No "filesystem tools" are required to mount most local filesystem types which have kernel drivers (such as ext* - not NFS which is a network filesystem type). Appropriate tools are required for filesystem types which have FUSE drivers, such as NTFS and exFAT.Head_on_a_Stick wrote:Then make sure the appropriate filesystem tools are installed (for example, e2fsprogs for ext{2,3,4})
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 133 times
Re: microsd not showing full capacity / dd failure with Rasp
Yes indeed, good pointp.H wrote:Without even checking the kernel logs with dmesg ?Head_on_a_Stick wrote:Yeah that looks dead to me.
@OP: make it so.
I did not know that, thanks for the correction. And e2fsprogs is an essential package anyway, how embarassing...p.H wrote:No "filesystem tools" are required to mount most local filesystem types which have kernel drivers (such as ext* - not NFS which is a network filesystem type). Appropriate tools are required for filesystem types which have FUSE drivers, such as NTFS and exFAT.
deadbang
Re: microsd not showing full capacity / dd failure with Rasp
I've gotten it working, did some reformatting with an Android phone, deleted extra partitions... anyway copying the Raspian img formats the size to something ~2GB, after which it inflates it to its maximum size during install, hence my initial confusion.