FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Kubuntu User

 
 
LinkBack Thread Tools
 
Old 03-21-2011, 06:17 AM
Nils Kassube
 
Default Same fdisk errors even after running fsck.ext4 on 16GB or 32GB microSD cards

Sid Boyce wrote:
> 11.04 natty and all kernels up to 2.6.38-7-generic.

Please elaborate? What error is it? And is your card reader even capable
of handling SDHC cards?


Nils

--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
 
Old 03-21-2011, 07:31 AM
Nils Kassube
 
Default Same fdisk errors even after running fsck.ext4 on 16GB or 32GB microSD cards

Nils Kassube wrote:
> Sid Boyce wrote:
> > 11.04 natty and all kernels up to 2.6.38-7-generic.
>
> Please elaborate? What error is it? And is your card reader even
> capable of handling SDHC cards?

Please ignore that nonsense - of course your card reader can handle SDHC
cards. Somehow I didn't see the attachment with the log.

However it would have been helpful if you described what you did instead
of attaching a log without comments. In that log I don't see an error
message from fdisk as I would expect from your subject, only this one
from the mount command:

| 8 / 9: Populating rootfs Partition
| Be patient, this may take a few minutes
| mount: wrong fs type, bad option, bad superblock on /dev/sdd2,
| missing codepage or helper program, or other error
| In some cases useful info is found in syslog - try
| dmesg | tail or so

I'm not sure what the script does here because I don't know the script.
But after the error message there is this hint:

| Unable to mount /dev/sdd2 at /tmp/tmp.GvquWTpaLd/disk to complete
| populating rootfs Partition
| Please retry running the script, sometimes rebooting your system
| helps.

From the log I don't know if you tried this - well I don't think that
rebooting would be necessary but maybe it would be useful to replug the
card and then run the script again.


Nils

--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
 
Old 03-21-2011, 11:17 AM
Sid Boyce
 
Default Same fdisk errors even after running fsck.ext4 on 16GB or 32GB microSD cards

11.04 natty and all kernels up to 2.6.38-7-generic.
I added an attachment to the original post which didn't get through, so
here goes with cut and paste.

------------------------------------------------------------------------
root@sdrbox:/usr/src/ubuntu-natty-alpha3-r0-minimal-armel#
./setup_sdcard.sh --mmc /dev/sdd -uboot beagle --rootfs ext4 --swap_file
1000 --debug


I see...
sfdisk -l:
Disk /dev/sda: 19457 cylinders, 255 heads, 63 sectors/track
Disk /dev/sdd: 32000 cylinders, 64 heads, 32 sectors/track

mount:
/dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0)

Are you 100% sure, on selecting [/dev/sdd] (y/n)? y


2 / 9: Unmountting Partitions

3 / 9: Creating Boot Partition

WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').

Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-32000, default 1): Last
cylinder, +cylinders or +size{K,M,G} (1-32000, default 32000):

Command (m for help): Selected partition 1
Hex code (type L to list codes): Changed system type of partition 1 to e
(W95 FAT16 (LBA))


Command (m for help):
Disk /dev/sdd: 33.6 GB, 33554432000 bytes
64 heads, 32 sectors/track, 32000 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d3d04

Device Boot Start End Blocks Id System
/dev/sdd1 1 65 66544 e W95 FAT16 (LBA)

Command (m for help): The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
Syncing disks.

4 / 9: Creating ext4 Partition

5 / 9: Formatting Boot Partition
mkfs.vfat 3.0.9 (31 Jan 2010)

6 / 9: Formatting ext4 Partition
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=rootfs
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
2044000 inodes, 8175360 blocks
408768 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
250 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208,

4096000, 7962624

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 23 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.

7 / 9: Populating Boot Partition
uImage
Image Name: 2.6.37.2-x3
Created: Mon Mar 21 00:13:17 2011
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4261220 Bytes = 4161.35 kB = 4.06 MB
Load Address: 80008000
Entry Point: 80008000
uInitrd
Image Name: initramfs
Created: Mon Mar 21 00:13:19 2011
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 3659054 Bytes = 3573.29 kB = 3.49 MB
Load Address: 00000000
Entry Point: 00000000
`/tmp/readme.txt' -> `/tmp/tmp.GvquWTpaLd/disk/tools/readme.txt'
`/tmp/update_boot_files.sh' ->
`/tmp/tmp.GvquWTpaLd/disk/tools/update_boot_files.sh'

`/tmp/fix_zippy2.sh' -> `/tmp/tmp.GvquWTpaLd/disk/tools/fix_zippy2.sh'
`/tmp/latest_kernel.sh' -> `/tmp/tmp.GvquWTpaLd/disk/tools/latest_kernel.sh'
`/tmp/minimal_xfce.sh' -> `/tmp/tmp.GvquWTpaLd/disk/tools/minimal_xfce.sh'
`/tmp/get_chrome.sh' -> `/tmp/tmp.GvquWTpaLd/disk/tools/get_chrome.sh'
`/tmp/dsp-init' -> `/tmp/tmp.GvquWTpaLd/disk/tools/dsp/dsp-init'
`/tmp/install-dsp-init.sh' ->
`/tmp/tmp.GvquWTpaLd/disk/tools/dsp/install-dsp-init.sh'
`/tmp/install-gst-dsp.sh' ->
`/tmp/tmp.GvquWTpaLd/disk/tools/dsp/install-gst-dsp.sh'


Finished populating Boot Partition

8 / 9: Populating rootfs Partition
Be patient, this may take a few minutes
mount: wrong fs type, bad option, bad superblock on /dev/sdd2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


Unable to mount /dev/sdd2 at /tmp/tmp.GvquWTpaLd/disk to complete
populating rootfs Partition

Please retry running the script, sometimes rebooting your system helps.
root@sdrbox:/usr/src/ubuntu-natty-alpha3-r0-minimal-armel#

root@sdrbox:/usr/src/ubuntu-natty-alpha3-r0-minimal-armel# fsck.ext4
/dev/sdd2

e2fsck 1.41.14 (22-Dec-2010)
Superblock has an invalid journal (inode 8).
Clear<y>? yes

*** ext3 journal has been deleted - filesystem is now ext2 only ***

Superblock has_journal flag is clear, but a journal inode is present.
Clear<y>? yes

rootfs was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Journal inode is not in use, but contains data. Clear<y>? yes

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: +(524288--532495) +(819200--820224)
+(884736--885760) +(1048576--1056783) +(1572864--1581071)
+(1605632--1606656) +(2097152--2105359) +(2621440--2629647)
+(2654208--2655232) +(3145728--3153935) +(3670016--3678223)
+(4096000--4097024) +(4194304--4202511) +(4718592--4726799)
+(5242880--5251087) +(5767168--5775375) +(6291456--6299663)
+(6815744--6823951) +(7340032--7348239) +(7864320--7864329)
+(7864336--7864345) +(7864352--7869461) +(7962624--7963648)

Fix<y>? yes

Free blocks count wrong for group #113 (0, counted=32768).
Fix<y>? yes

Free blocks count wrong (8002036, counted=8034804).
Fix<y>? yes

Recreate journal<y>? yes

Creating journal (32768 blocks): y Done.

*** journal has been re-created - filesystem is now ext3 again ***

rootfs: ***** FILE SYSTEM WAS MODIFIED *****
rootfs: 11/2044000 files (0.0% non-contiguous), 173324/8175360 blocks
root@sdrbox:/usr/src/ubuntu-natty-alpha3-r0-minimal-armel# fsck.ext4
/dev/sdd2

e2fsck 1.41.14 (22-Dec-2010)
Superblock has an invalid journal (inode 8).
Clear<y>? yes

*** ext3 journal has been deleted - filesystem is now ext2 only ***

Superblock has_journal flag is clear, but a journal inode is present.
Clear<y>? yes

rootfs was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Journal inode is not in use, but contains data. Clear<y>? yes

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: +(524288--532495) +(819200--820224)
+(884736--885760) +(1048576--1056783) +(1572864--1581071)
+(1605632--1606656) +(2097152--2105359) +(2621440--2629647)
+(2654208--2655232) +(3145728--3153935) +(3670016--3678223)
+(4096000--4097024) +(4194304--4202511) +(4718592--4726799)
+(5242880--5251087) +(5767168--5775375) +(6291456--6299663)
+(6815744--6823951) +(7340032--7348239) +(7864320--7864329)
+(7864336--7864345) +(7864352--7869461) +(7962624--7963648)

Fix<y>? yes

Free blocks count wrong for group #113 (0, counted=32768).
Fix<y>? yes

Free blocks count wrong (8002036, counted=8034804).
Fix<y>? yes

Recreate journal<y>? yes

Creating journal (32768 blocks): Done.

*** journal has been re-created - filesystem is now ext3 again ***

rootfs: ***** FILE SYSTEM WAS MODIFIED *****
rootfs: 11/2044000 files (0.0% non-contiguous), 173324/8175360 blocks
root@sdrbox:/usr/src/ubuntu-natty-alpha3-r0-minimal-armel#
------------------------------------------------------------------------
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach

Microsoft Windows Free Zone - Linux used for all Computing Tasks



--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
 
Old 03-21-2011, 11:30 AM
Sid Boyce
 
Default Same fdisk errors even after running fsck.ext4 on 16GB or 32GB microSD cards

To the other question, the new card reader is capable of handling
microSD cards. I originally built the same on the same cards. It booted
fine but problems only appeared after I added a number of packages. Some
way through I got a message that it couldn't write to the filesystem.
Since then I ran into the problem. Even deleting the partitions and
running the script again I hit the problem where the SD has the errors
seen in the post.
It's possible the reader has developed a problem, so I'll get a
different new one to try.

Regards
Sid.

On 21/03/11 12:17, Sid Boyce wrote:

11.04 natty and all kernels up to 2.6.38-7-generic.
I added an attachment to the original post which didn't get through, so
here goes with cut and paste.
------------------------------------------------------------------------
root@sdrbox:/usr/src/ubuntu-natty-alpha3-r0-minimal-armel#
./setup_sdcard.sh --mmc /dev/sdd -uboot beagle --rootfs ext4 --swap_file
1000 --debug

I see...
sfdisk -l:
Disk /dev/sda: 19457 cylinders, 255 heads, 63 sectors/track
Disk /dev/sdd: 32000 cylinders, 64 heads, 32 sectors/track

mount:
/dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0)

Are you 100% sure, on selecting [/dev/sdd] (y/n)? y


2 / 9: Unmountting Partitions

3 / 9: Creating Boot Partition

WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').

Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-32000, default 1): Last
cylinder, +cylinders or +size{K,M,G} (1-32000, default 32000):
Command (m for help): Selected partition 1
Hex code (type L to list codes): Changed system type of partition 1 to e
(W95 FAT16 (LBA))

Command (m for help):
Disk /dev/sdd: 33.6 GB, 33554432000 bytes
64 heads, 32 sectors/track, 32000 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d3d04

Device Boot Start End Blocks Id System
/dev/sdd1 1 65 66544 e W95 FAT16 (LBA)

Command (m for help): The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
Syncing disks.

4 / 9: Creating ext4 Partition

5 / 9: Formatting Boot Partition
mkfs.vfat 3.0.9 (31 Jan 2010)

6 / 9: Formatting ext4 Partition
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=rootfs
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
2044000 inodes, 8175360 blocks
408768 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
250 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 23 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.

7 / 9: Populating Boot Partition
uImage
Image Name: 2.6.37.2-x3
Created: Mon Mar 21 00:13:17 2011
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4261220 Bytes = 4161.35 kB = 4.06 MB
Load Address: 80008000
Entry Point: 80008000
uInitrd
Image Name: initramfs
Created: Mon Mar 21 00:13:19 2011
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 3659054 Bytes = 3573.29 kB = 3.49 MB
Load Address: 00000000
Entry Point: 00000000
`/tmp/readme.txt' -> `/tmp/tmp.GvquWTpaLd/disk/tools/readme.txt'
`/tmp/update_boot_files.sh' ->
`/tmp/tmp.GvquWTpaLd/disk/tools/update_boot_files.sh'
`/tmp/fix_zippy2.sh' -> `/tmp/tmp.GvquWTpaLd/disk/tools/fix_zippy2.sh'
`/tmp/latest_kernel.sh' ->
`/tmp/tmp.GvquWTpaLd/disk/tools/latest_kernel.sh'
`/tmp/minimal_xfce.sh' -> `/tmp/tmp.GvquWTpaLd/disk/tools/minimal_xfce.sh'
`/tmp/get_chrome.sh' -> `/tmp/tmp.GvquWTpaLd/disk/tools/get_chrome.sh'
`/tmp/dsp-init' -> `/tmp/tmp.GvquWTpaLd/disk/tools/dsp/dsp-init'
`/tmp/install-dsp-init.sh' ->
`/tmp/tmp.GvquWTpaLd/disk/tools/dsp/install-dsp-init.sh'
`/tmp/install-gst-dsp.sh' ->
`/tmp/tmp.GvquWTpaLd/disk/tools/dsp/install-gst-dsp.sh'

Finished populating Boot Partition

8 / 9: Populating rootfs Partition
Be patient, this may take a few minutes
mount: wrong fs type, bad option, bad superblock on /dev/sdd2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


Unable to mount /dev/sdd2 at /tmp/tmp.GvquWTpaLd/disk to complete
populating rootfs Partition
Please retry running the script, sometimes rebooting your system helps.
root@sdrbox:/usr/src/ubuntu-natty-alpha3-r0-minimal-armel#

root@sdrbox:/usr/src/ubuntu-natty-alpha3-r0-minimal-armel# fsck.ext4
/dev/sdd2
e2fsck 1.41.14 (22-Dec-2010)
Superblock has an invalid journal (inode 8).
Clear<y>? yes

*** ext3 journal has been deleted - filesystem is now ext2 only ***

Superblock has_journal flag is clear, but a journal inode is present.
Clear<y>? yes

rootfs was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Journal inode is not in use, but contains data. Clear<y>? yes

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: +(524288--532495) +(819200--820224)
+(884736--885760) +(1048576--1056783) +(1572864--1581071)
+(1605632--1606656) +(2097152--2105359) +(2621440--2629647)
+(2654208--2655232) +(3145728--3153935) +(3670016--3678223)
+(4096000--4097024) +(4194304--4202511) +(4718592--4726799)
+(5242880--5251087) +(5767168--5775375) +(6291456--6299663)
+(6815744--6823951) +(7340032--7348239) +(7864320--7864329)
+(7864336--7864345) +(7864352--7869461) +(7962624--7963648)
Fix<y>? yes

Free blocks count wrong for group #113 (0, counted=32768).
Fix<y>? yes

Free blocks count wrong (8002036, counted=8034804).
Fix<y>? yes

Recreate journal<y>? yes

Creating journal (32768 blocks): y Done.

*** journal has been re-created - filesystem is now ext3 again ***

rootfs: ***** FILE SYSTEM WAS MODIFIED *****
rootfs: 11/2044000 files (0.0% non-contiguous), 173324/8175360 blocks
root@sdrbox:/usr/src/ubuntu-natty-alpha3-r0-minimal-armel# fsck.ext4
/dev/sdd2
e2fsck 1.41.14 (22-Dec-2010)
Superblock has an invalid journal (inode 8).
Clear<y>? yes

*** ext3 journal has been deleted - filesystem is now ext2 only ***

Superblock has_journal flag is clear, but a journal inode is present.
Clear<y>? yes

rootfs was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Journal inode is not in use, but contains data. Clear<y>? yes

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: +(524288--532495) +(819200--820224)
+(884736--885760) +(1048576--1056783) +(1572864--1581071)
+(1605632--1606656) +(2097152--2105359) +(2621440--2629647)
+(2654208--2655232) +(3145728--3153935) +(3670016--3678223)
+(4096000--4097024) +(4194304--4202511) +(4718592--4726799)
+(5242880--5251087) +(5767168--5775375) +(6291456--6299663)
+(6815744--6823951) +(7340032--7348239) +(7864320--7864329)
+(7864336--7864345) +(7864352--7869461) +(7962624--7963648)
Fix<y>? yes

Free blocks count wrong for group #113 (0, counted=32768).
Fix<y>? yes

Free blocks count wrong (8002036, counted=8034804).
Fix<y>? yes

Recreate journal<y>? yes

Creating journal (32768 blocks): Done.

*** journal has been re-created - filesystem is now ext3 again ***

rootfs: ***** FILE SYSTEM WAS MODIFIED *****
rootfs: 11/2044000 files (0.0% non-contiguous), 173324/8175360 blocks
root@sdrbox:/usr/src/ubuntu-natty-alpha3-r0-minimal-armel#
------------------------------------------------------------------------
Regards
Sid.



--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach

Microsoft Windows Free Zone - Linux used for all Computing Tasks


--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
 
Old 03-21-2011, 08:28 PM
Nils Kassube
 
Default Same fdisk errors even after running fsck.ext4 on 16GB or 32GB microSD cards

Sid Boyce wrote:
> To the other question, the new card reader is capable of handling
> microSD cards. I originally built the same on the same cards. It
> booted fine but problems only appeared after I added a number of
> packages. Some way through I got a message that it couldn't write to
> the filesystem. Since then I ran into the problem. Even deleting the
> partitions and running the script again I hit the problem where the
> SD has the errors seen in the post.

OK, that clarifies the situation.

> It's possible the reader has developed a problem, so I'll get a
> different new one to try.

Yes, the reader might be faulty, especially if both cards have the same
error. OTOH, maybe there is a problem with Natty. Can you give some
instructions how I could try to reproduce the situation? I have a test
partition for cases like this on a harddisk and I could try it on a SD
card as well.

Another option might be to fill (one of) the cards with zeros (dd
if=/dev/zero of=/dev/sdX) and then retry the script. But make sure there
are no valuable data on the card because the zeros will of course erase
everything.

> On 21/03/11 12:17, Sid Boyce wrote:
> > 11.04 natty and all kernels up to 2.6.38-7-generic.
> > I added an attachment to the original post which didn't get
> > through, so here goes with cut and paste.

Actually that attachment came through but I just didn't recognize it
before I sent the first reply.


Nils

--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
 

Thread Tools




All times are GMT. The time now is 12:54 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org