[SOLVED] badblocks ext4

Overview of issue.
On boot when a filesystem is being fsck, errors appear:
[ 21.638174] sd 2:0:0:0: [sdc] Unhandled sense code
[ 21.638180] sd 2:0:0:0: [sdc] Result: hostbyte=0x10 driverbyte=0x08
[ 21.638186] sd 2:0:0:0: [sdc] Sense Key : 0x3 [current]
[ 21.638192] sd 2:0:0:0: [sdc] ASC=0x11 ASCQ=0x0
[ 21.638197] sd 2:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 05 c0 00 67 00 00 40 00
[ 21.638210] end_request: critical target error, dev sdc, sector 96469095
[ 21.638289] Buffer I/O error on device sdc1, logical block 96469032
[ 21.638351] Buffer I/O error on device sdc1, logical block 96469033
[ 21.638410] Buffer I/O error on device sdc1, logical block 96469034
[ 21.638468] Buffer I/O error on device sdc1, logical block 96469035
[ 21.638525] Buffer I/O error on device sdc1, logical block 96469036
[ 21.638581] Buffer I/O error on device sdc1, logical block 96469037
[ 21.638639] Buffer I/O error on device sdc1, logical block 96469038
[ 21.638696] Buffer I/O error on device sdc1, logical block 96469039
[ 21.638762] Buffer I/O error on device sdc1, logical block 96469040
[ 21.638820] Buffer I/O error on device sdc1, logical block 96469041
[ 23.551857] sd 2:0:0:0: [sdc] Unhandled sense code
[ 23.551863] sd 2:0:0:0: [sdc] Result: hostbyte=0x10 driverbyte=0x08
[ 23.551868] sd 2:0:0:0: [sdc] Sense Key : 0x3 [current]
[ 23.551874] sd 2:0:0:0: [sdc] ASC=0x11 ASCQ=0x0
[ 23.551878] sd 2:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 05 c0 00 a7 00 00 80 00
[ 23.551890] end_request: critical target error, dev sdc, sector 96469159
[ 24.591795] sd 2:0:0:0: [sdc] Unhandled sense code
[ 24.591801] sd 2:0:0:0: [sdc] Result: hostbyte=0x10 driverbyte=0x08
[ 24.591806] sd 2:0:0:0: [sdc] Sense Key : 0x3 [current]
[ 24.591811] sd 2:0:0:0: [sdc] ASC=0x11 ASCQ=0x0
[ 24.591816] sd 2:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 05 c0 00 8f 00 00 08 00
[ 24.591828] end_request: critical target error, dev sdc, sector 96469135
I'm not familiar with that but since I can mount and read and write data my spider sense tells me it's probably bad blocks than a catastrophic mechanism failure.
Disk /dev/sdc: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 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
Disk identifier: 0x0001132a
Device Boot Start End Blocks Id System
/dev/sdc1 63 312581807 156290872+ 83 Linux
Two general goals,
Locate which files are on bad blocks.
Mark bad blocks so they can not be used again.
I have never done either before.
Plan of attack for finding damaged files,
The wiki has this fine article: https://wiki.archlinux.org/index.php/Fi … iven_Block
which describes the process for JFS (everyone uses JFS). I am unfortunately part of the minority who uses ext4. Not to worry, the article gives ideas on how to approach this:
find bad blocks using: badblocks -v -b 4096 /dev/sdc1
use debugfs's icheck to find which inodes correspond to the bad blocks
use find utility to map inodes to path
Marking bad blocks
I need help with this.
Last edited by fsckd (2011-11-10 12:45:42)

I'm not sure. When I tried -d usbcypress it hung and kill -9 took a while to take effect.
Here's the output from hdparm -I,
/dev/sdb:
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ATA device, with non-removable media
Standards:
Likely used: 1
Configuration:
Logical max current
cylinders 0 0
heads 0 0
sectors/track 0 0
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 0 MBytes
device size with M = 1000*1000: 0 MBytes
cache/buffer size = unknown
Capabilities:
IORDY not likely
Cannot perform double-word IO
R/W multiple sector transfer: not supported
DMA: not supported
PIO: pio0

Similar Messages

[Solved] Disapointing ext4 fsck performance

Hi all,
Yesterday I converted my main partition to ext4, using the tune2fs + fsck method, and changing my partition type to ext4 in fstab. I thought one of the main points of ext4 was a faster fsck, however in my case the contrary is happening. I don't have any precise figures, but I would say an fsck takes about twice as long as before, in the order of several minutes for a 170GB partition with about 50GB of stuff on it.
Any insight? Is this normal or am I missing something?
Last edited by lardon (2009-01-22 13:28:25)

lardon wrote:
skottish wrote:I'm not sure if this question got asked yet. Did you convert your data over to use the new device mapping? Simply converting the hard disc isn't enough. I don't know if that's a factor, but I do know that fsck is way faster for me now.
mmm, no I didn't, since e4defrag is not available yet with the standard kernel. Well, I guess that settles my problem then! Thanks for the answer.
Sorry I didn't respond sooner. I used the CK defrag script found here:
http://ck.kolivas.org/apps/defrag/defrag-0.06/defrag
which was found in post #62 here:
http://bbs.archlinux.org/viewtopic.php?id=61602
There's been some discussion around on whether defragging is a good idea or not, but I didn't see anyone fully explain why it's not. This is where I heard it from:
http://bbs.archlinux.org/viewtopic.php?id=63228
On my system, fsck use to take something like 4 minutes on my data discs with ext3. It now takes about 20 seconds with ext4. That includes recreating the lost+found folder, which for some reason seems to take a bit of time.

[solved] Check EXT4 partition automatically

Hello everyone,
I have two EXT4 partition on my HD (sda2 and sda4):
$ fdisk -l
Device Boot Start End Blocks Id System
/dev/sda1 * 1 3264 26218048+ 7 HPFS/NTFS
/dev/sda2 3265 6528 26218080 83 Linux
/dev/sda3 6529 6590 498015 82 Linux swap / Solaris
/dev/sda4 6591 19457 103354177+ 83 Linux
Eventually, sda2 partition (root partition) is checked automatically on boot, but sda4 never checked. On dmesg appears:
EXT4-fs (sda4): warning: maximal mount count reached, running e2fsck is recommended
On wiki (http://wiki.archlinux.org/index.php/Fsck) is written:
The Arch Linux boot process conveniently takes care of the Fsck procedure for you and will periodically check ALL relevant partitions on your hard drive automatically in a scheduled manner.
Can I turn automatically check on for sda4 partition too? Or I have to do this manually ?
My fstab:
UUID=324658b1-0c1a-494b-bc6e-93ca1d138b1b swap swap defaults 0 0
UUID=fc37e80c-fe03-4932-b9af-c8388190f19c / ext4 defaults 0 1
UUID=b19fe1b6-aee6-4bda-b17f-b76674016525 /media/Dados ext4 defaults,noatime,nodiratime 0 0
/dev/sda1 /media/Windows ntfs-3g defaults 0 0
Thanks in advance.
Last edited by alessandro_ufms (2010-04-07 20:11:42)

Have a look at the <pass> definition in fstab: http://wiki.archlinux.org/index.php/Fstab
File systems with a <pass> value 0 will not be checked by the fsck utility.

[SOLVED] Broken ext4, recoverable?

I was trying to rearrange my partitions using gparted so that the free space was in a usable place.
I shrank my second partition and clicked apply. It finished successfully.
I then tried to expand my third partition downwards. It sait it would take about 90 minutes, so I went to bed.
When I came back, the screen showed it had stopped in some kind of boot state. I rebooted and found the keyboard didn't work in Xorg. Two cold boots later and it magically worked again.
The expanded partition had not mounted to I loaded gparted up again and got "unable to detect filesystem" on that partition.
emyr@emyr-desktop:~$ sudo mke2fs -n /dev/sdb3
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
23707648 inodes, 94823304 blocks
4741165 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
2894 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968
emyr@emyr-desktop:~$
emyr@emyr-desktop:~$ sudo fdisk -l
[sudo] password for emyr:
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x24bf24be
Device Boot Start End Blocks Id System
/dev/sda1 1 5992 48130708+ 7 HPFS/NTFS
/dev/sda2 5993 15722 78156225 7 HPFS/NTFS
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe5f3ed43
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 7012 56319952+ 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sdb2 7208 13582 51200588+ 83 Linux
/dev/sdb3 13582 60801 379293216+ 83 Linux
/dev/sdb4 7012 7207 1570243+ 82 Linux swap / Solaris
Partition table entries are not in disk order
Disk /dev/sdc: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b717b
Device Boot Start End Blocks Id System
/dev/sdc1 1 6527 52426752 6 FAT16
/dev/sdc2 6528 30401 191767905 0 Empty
emyr@emyr-desktop:~$
I googled a bit and read about backup superblocks, so I tried this:
emyr@emyr-desktop:~$ sudo e2fsck -b 163840 /dev/sdb3
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb3
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>
emyr@emyr-desktop:~$
What should be my next step?
Last edited by Emyr (2011-07-23 00:36:16)

Managed to recover the lost partition, and simultaneously lose my / partition. Oops. Attempt 2 after doing a partial backup got it all back.
Now to buy a very large new drive so I can make my partitions ridiculously large!

[Solved] ext4 partition reported as NTFS

I was testing a SSD disk before installing and i plugged it to a Wndows machine for benchmarking purposes
For performing such tests, I created 2 NTFS partitions.
Afterwards, I plugged the disk to the SATA interface of the computer I would use it in.
I formatted the two partitions that were in the disk.
mkfs.ext4 /dev/sda1
mkfs.ext4 /dev/sda2
...and got no errors...
When I run fdisk -l I get:
System: HPFS/NTFS/exFAT
But if i run cfdisk, it's being reported as ext4 - same happens when i open gparted.....
Why can this be?
EDIT: Fixed changing the partition type to 83 from cfdisk (prior unmount)
I didn't lose any data in the process....
Last edited by Xi0N (2012-10-21 19:54:57)

Glad to see you solved this yourself. Please don't forget to mark the post as [Solved] and keep our forums organized (mostly).

[SOLVED][ext4]Tuning "bytes-per-inode ratio" ?

Hi,
I'd like to format two partitions (under LVM) with ext4, a / (20GB) and a /home (890GB). The usage pattern for the /home partition will be fairly standard (smalls documents, configuration files, a lot of media).
The wiki mentions something about tuning the "bytes-per-inode ratio" for partition of more than 750GB (https://wiki.archlinux.org/index.php/Ex … filesystem).
It does however not reference any links / documentation for it.
The mke2fs man page isn't any more helful toward offering pragmatic advice.
My question is the following : Should I bother tuning this option for /home (I'm assuming that the default is good enough for /, correct?) and if so, how (range of ratios from "conservative" to "probably too much") ?
Thank you for reading.
Last edited by Resistance (2015-05-10 14:48:19)

1) Removing reserved blocks can result in an immediate gain of up to 5% space (although reducing it to 0 is kind of risky if you plan on actually filling the drive).
2) The defaults for inode creation is 1 inode for every 16MB of data. inodes occupy 256 bytes. That means for every 16M of data you lose 256 bytes, or about 1.5%. I've confirmed that to be the case using df and df -i on drives of various sizes and doing the math.
The thread linked above showed 22GB for a 1.5T drive which is roughly 1.5%. So you can reduce your inodes and maybe squeeze out another percent or so, but TMK you can't undo it without reformatting. If you haven't removed reserved blocks yet, that's a more fruitful source of disk space.
EDIT: Sorry, didn't see your [SOLVED] post until after I posted. Sounds like you made the right call.
Last edited by mwillems (2015-05-10 15:06:25)

[solved] Ext4 goes read-only after nodealloc

Hello.
I've been trying this many times, but never succeed with using my partitions powered by ext4 file system with nodealloc option in fstab. It doesn't matter, if I add this option after defaults or replace defaults with nodealloc only. After reboot, all ext4 partitions (/ and /home) goes read-only, so I can't do anything with Arch, not even change fstab back. There are no problems, if I put other options to fstab (for example: relatime to ext3 file systems).
Anyone have same problem?
Last edited by weakhead (2009-04-20 19:32:30)

Whoa! That explains everything. I will try one more time.
EDIT: Yeah, this is it. It's nodelalloc, not nodealloc...
Thanks
Last edited by weakhead (2009-04-20 19:32:13)

[SOLVED] Could I broke my SD card with badblocks or dd? [I coudn't]

I found some old, 1GB SD Card and wanted to use it as my EFI partition (well, wanted to check if my EFI system will even see it as I have no idea if it's possible or not). There were some old pictures so I thought - okay, it's working. I've wiped it with
badblocks -wsv
and the final output was
Pass completed, 216640 bad blocks found. (0/0/216640 errors)
which seems to me like ALL blocks are "bad" (corruption error). Well, I thought that maybe badblocks wasn't created to check SD cards. I then used gdisk to get:
Command (? for help): p
Disk /dev/mmcblk0: 1984000 sectors, 968.8 MiB
Logical sector size: 512 bytes
Disk identifier (GUID): 84DBE3FD-1D8A-4E49-80D1-9F9594BB1974
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1983966
Partitions will be aligned on 2048-sector boundaries
Total free space is 8158 sectors (4.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 8192 1983966 964.7 MiB EF00 EFI System
After writing changes to the card (
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/mmcblk0.
The operation has completed successfully.
) I saw no extra partition in my /dev so I ran gdisk again and it prompted:
Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!
Caution! After loading partitions, the CRC doesn't check out!
Warning! Main partition table CRC mismatch! Loaded backup partition table
instead of main partition table!
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
I've tried to
dd if=/dev/urandom
too and all the other options I could think of, just to start over... but... it is just broken now? Was it broken before?
Last edited by smsware (2013-07-17 11:57:24)

It was in some old phone of mine and appears to be as clean as brand new. But
sudo dcfldd if=/dev/urandom of=/dev/mmcblk0 bs=4M count=1
gave
1+0 records in
1+0 records out
as an output so I actually can write into it, right? I played a little with the lock label but it's acting the same. If lock label is set to protect the data, the output is
dcfldd:/dev/mmcblk0: Read-only file system
so it's not the problem. I want to buy new card anyway but I just want to be sure that I will not broke it too. ;-)
I've found this:
The SD/SDHC/SDXC memory cards have a "Protected Area" on the card for the SD standard's security function. The SD Formatter does not format the "Protected Area".
and also (but can't find it again to quote) that you should leave first 8192 sectors (blocks? I'm really bad with hardware) free of modification because the performance would be worse then (but no information about braking it!).

[SOLVED] I cannot make mounted ext4 partition writeable.

I want to make /dev/sdc2 (mounted on /mnt/SteamLinux) writeable, so I could install Steam games on it.
/etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdb3
UUID=7cfc361a-47e1-45b9-8429-054d31302402 / ext4 rw,relatime,data=ordered 0 1
# /dev/sdb4
UUID=04b8a615-8738-4d5c-b4de-16a0f92ade4d /home ext4 rw,relatime,data=ordered 0 2
# /dev/sdc2
UUID=1501a760-5c07-4279-a2c2-9695e08a6cdd /mnt/SteamLinux ext4 defaults 0 0
# NTFS drives
/dev/sda1 /mnt/Blue ntfs-3g defaults 0 0
/dev/sdc1 /mnt/Black ntfs-3g defaults 0 0
fsck /dev/sdc2 result:
fsck from util-linux 2.22.2
e2fsck 1.42.7 (21-Jan-2013)
fsck.ext4: Permission denied while trying to open /dev/sdc2
You must have r/w access to the filesystem or be root
What should I do to make it writeable without root access?
Last edited by White girl (2013-03-31 00:10:21)

Mr.Elendig wrote:uhm, just run fsck as root? And for access as a normal user: chown and chmod
Ran fsck as root, it went fine. Remounted /dev/sdc2, then ran
sudo chmod -R +w /dev/sdc2
I assume it's a command to make this partition writeable for regular user. Steam still threw me as readonly.
Got it working by using /mnt/SteamLinux instead of /dev/sdc2.
Steam issue is still not resolved, but it's irrelevant to the thread now... (Steam refuses to download anything to this partition, it returns me as 0MB available space)
Last edited by White girl (2013-03-30 14:16:23)

3TB HDD, GPT, EXT4 HPA enabled, [SOLVED]

I started my HTPC as usual, only to be greeted with "movie share" not found. I was suprised, looking at console, it seemed the kernely suddently stopped looking for my HDD.
Manually mounting the HDD
mount -t ext4 /dev/sdg1 /mnt
mount: special device /dev/sdg1 does not exist
fdisk /dev/sdg
Disk /dev/sdg: 3000.6 GB, 3000591900160 bytes, 5860531055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdg1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.
dmesg | grep sdg
8.035214] sd 8:0:0:0: [sdg] 5860531055 512-byte logical blocks: (3.00 TB/2.72 TiB)
[ 8.035217] sd 8:0:0:0: [sdg] 4096-byte physical blocks
[ 8.035280] sd 8:0:0:0: [sdg] Write Protect is off
[ 8.035282] sd 8:0:0:0: [sdg] Mode Sense: 00 3a 00 00
[ 8.035306] sd 8:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 8.090129] sdg:
[ 8.090458] sd 8:0:0:0: [sdg] Attached SCSI disk.
stat /dev/sdg1
stat: cannot stat /dev/sdg1: No such file or directory
Also ran testdisk, tried the analyze, it said all okay, tried rebuilding partition structure. I think maybe that's why it's now complaining about "Error: Can't have a partition outside the disk!"
sudo parted /dev/sdg unit s print
Error: Can't have a partition outside the disk!
Model: ATA ST3000DM001-1CH1 (scsi)
Disk /dev/sdg: 5860531055s
Sector size (logical/physical): 512B/4096B
Partition Table: unknown
Disk Flags:
I've read this guide: http://gparted.sourceforge.net/h2-fix-msdos-pt.php
Thanks to iranshaksi on IRC, very friendly and kind fellow. But i'm still puzzled what to do.
It's a fresh HDD, couple of weeks old, seagate 3TB, partioned with GPT/EXT4. I have over 300GB stored of PERSONAL video files on this HDD.
Please is there away at all to get access to my files? I just want to transfer the files I have on the hdd onto another one.
And perhaps re-partion this HDD. How can a hdd just stop working like this?
Is there a "magical" way i'm suppose to partition a 3TB hdd? My other 3TB works just fine. I'm quite puzzled here gentlemen
Last edited by greenfish (2013-10-24 09:12:54)

graysky wrote:Anything in dmegs about errors? You sure it's still /dev/sdg1? Post the output of `lsblk -f` In the future, you might want to consider using labels or UUIDs for mounting since drive letters can change if you add/remove a device or if something changes in the BIOS, etc. Labels are better in my opinion because you name them whereas UUIDs are meaningless to the user.
Yes sir, it's the only HDD that refuses to mount. Tried it on my other linux box as well.
fdisk -l | less
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes, 1953525168 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
Disk label type: dos
Disk identifier: 0xe81808b3
Device Boot Start End Blocks Id System
/dev/sda1 63 1953520064 976760001 83 Linux
Disk /dev/sdb: 4022 MB, 4022337024 bytes, 7856127 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
Disk label type: dos
Disk identifier: 0x43756644
Device Boot Start End Blocks Id System
/dev/sdb1 * 0 1077247 538624 0 Empty
/dev/sdb2 4728 68215 31744 ef EFI (FAT-12/16/32)
Disk /dev/sdb1: 551 MB, 551550976 bytes, 1077248 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
Disk label type: dos
Disk identifier: 0x43756644
Device Boot Start End Blocks Id System
/dev/sdb1p1 * 0 1077247 538624 0 Empty
/dev/sdb1p2 4728 68215 31744 ef EFI (FAT-12/16/32)
Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes, 2930277168 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
Disk label type: dos
Disk identifier: 0x31f60035
Device Boot Start End Blocks Id System
/dev/sdc1 63 2930272064 1465136001 83 Linux
Disk /dev/sdd: 1000.2 GB, 1000203804160 bytes, 1953523055 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
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdd1 63 1953520064 976760001 83 Linux
Disk /dev/sde: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sde1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/sdf: 160.0 GB, 160040803840 bytes, 312579695 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
Disk label type: dos
Disk identifier: 0x000c4ba1
Device Boot Start End Blocks Id System
/dev/sdf1 2048 293603327 146800640 83 Linux
/dev/sdf2 293603328 312579694 9488183+ 83 Linux
Disk /dev/sdg: 3000.6 GB, 3000591900160 bytes, 5860531055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdg1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/mapper/arch_root-image: 1561 MB, 1561329664 bytes, 3049472 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
root@archiso ~ # stat /dev/sdg1
stat: cannot stat â/dev/sdg1â: No such file or directory
1 root@archiso ~ # stat /dev/sdg1
stat: cannot stat â/dev/sdg1â: No such file or directory
1 root@archiso ~ # stat: cannot stat dev/sdg1 No such file or directory
zsh: correct 'stat:' to 'stat' [nyae]? n
zsh: command not found: stat:
127 root@archiso ~ # sudo fdisk -l | less
/dev/sdc1 63 2930272064 1465136001 83 Linux
Disk /dev/sdd: 1000.2 GB, 1000203804160 bytes, 1953523055 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
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdd1 63 1953520064 976760001 83 Linux
Disk /dev/sde: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sde1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/sdf: 160.0 GB, 160040803840 bytes, 312579695 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
Disk label type: dos
Disk identifier: 0x000c4ba1
Device Boot Start End Blocks Id System
/dev/sdf1 2048 293603327 146800640 83 Linux
/dev/sdf2 293603328 312579694 9488183+ 83 Linux
Disk /dev/sdg: 3000.6 GB, 3000591900160 bytes, 5860531055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdg1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/mapper/arch_root-image: 1561 MB, 1561329664 bytes, 3049472 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
Log file is already in use (press RETURN)
dmesg http://bpaste.net/show/142956/
Tried:
dmesg | grep EE
dmesg | grep WW
dmesg | grep /dev/sdg*
Didn't see anything useful.
lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
ââsda1 ext4 1TB-D fc268167-056f-4e5b-9e02-74626236a500 /mnt/1
sdb iso9660 ARCH_201308 2013-08-01-08-13-08-00
ââsdb1 iso9660 ARCH_201308 2013-08-01-08-13-08-00 /run/archiso/bootmnt
ââsdb2 vfat ARCHISO_EFI 8567-F798
sdc
ââsdc1 ext4 1.5TB-F 0fba37d8-a29a-4214-a5b7-f725de4bbb4e /mnt/2
sdd
ââsdd1 ext4 1TB-C d5651eb3-6e63-4e27-a13d-a02eb13983c6 /mnt/3
sde
ââsde1 ext4 7d7c8734-b060-4715-a867-3886dddf54e6 /mnt/4
sdf
ââsdf1 ext4 87c51044-75cf-496c-9733-936047c5ec18
ââsdf2 swap 2cfb72c0-4d1e-450c-a807-6875fa094543
sdg
loop0 squashfs /run/archiso/sfs/root-image
loop1 ext4 46e2ebd2-7640-49d1-89e9-a45d6e236fa7
ââarch_root-image ext4 46e2ebd2-7640-49d1-89e9-a45d6e236fa7 /
loop2 ext4 46e2ebd2-7640-49d1-89e9-a45d6e236fa7
ââarch_root-image ext4 46e2ebd2-7640-49d1-89e9-a45d6e236fa7 /
Yeah I usually rely on UUID, but I had to make a fresh arch install, that's why they are using deviceid instead of uuid.
Thank You
Last edited by greenfish (2013-10-22 20:39:50)

[Solved -sorta] systemd-fsck []: fsck: /sbin/fsck.ext4: execute failed

Greetings.
I am getting the following on boot:
Starting Version 218
A password is required to access the MyStorage volume:
Enter passphrase for /dev/sda3
/dev/mapper/MyStorage-rootvol: clean, 210151/983040 files, 2284613/3932160 block
[ 78.084720] systemd-fsck [280]: fsck: /sbin/fsck.ext4: execute failed: Exec format error
[ 78.085215] systemd-fsck [287]: fsck: /sbin/fsck.ext2: execute failed: Exec format error
I then end up at a login prompt but if I try to login, I get “Login incorrect”. Sometimes Getty will stop and restart on tty1. Then I get returned to the login prompt.
This came about after upgrading with Pacman (which included “upgraded e2fsprogs (1.42.12-1 -> 1.42.12-2)”) a few days ago. Pacman completed successfully but on reboot the system froze forcing a hard reset.
I've booted to a USB and run fsck on the boot partition (the only ext2 partition). Ditto on the root and home volumes. All fine. I've also mounted all three and can access the data.
I would have thought it was something to do with the e2fs upgrade but it obviously scanned the root volume fine and I haven't been able to find any similar reports online.
I've searched online for ideas and I've also searched for logs which might give me some indication of what the cause is but at this point, I've reached my limits.
I'd just nuke the data and start again but I really want to understand what happened here.
Any thoughts on what caused this or suggestions on how to proceed?
Thank you.
Stephen
Last edited by FixedWing (2015-03-16 01:40:20)

Head_on_a_Stick wrote:
https://wiki.archlinux.org/index.php/Pa … ond_repair
However, it may be simplest to just re-install in your case -- it depends whether you want to use the troubleshooting & repairing as a learning process or if you just want your system up & running again ASAP...
All fixed and working just like nothing happened.
I did use the advice at the referred link plus a few others on archlinux.org and elsewhere. Yes, an absolutely wonderful learning experience!
I manually reinstalled e2fsprogs. That got Pacman working again and I was able to boot into the system. Then I used Pacman to reinstall e2fsprogs properly plus the other seven packages which were also installed during the same Pacman session despite their being corrupted.
What I really don't get is how Pacman could accept a package with 0 bytes and install it? How could such a package possible pass the security check? When I reinstalled the packages, Pacman of course refused to install the corrupt packages in the cache and deleted them. So why didn't that happen initially? I can only think that a corrupt file in that process terminated prematurely and that Pacman wasn't robust enough to detect this so simply continued on, now skipping the scans and installing the corrupt packages. So just to be sure it wasn't a corrupt file in Pacman itself, I also forced a reinstall of that package as well. I've upgraded packages since without issue so I have to assume that whatever the issue was is now gone.
Anyway, thanx for the help!
Stephen

[SOLVED] How do I increase the size of an existing GPT ext4 partition?

I found some advice here
http://ubuntuforums.org/showthread.php?t=1389429
but I'm not sure whether the information is correct
1 Run parted on your device: parted /dev/sdX
2 Change display unit to sectors: unit s
3 Print current partition table and note the start sector for your partition: p
4 Delete your partition (won't delete the data or filesystem): rm <number>
5 Recreate the partition with the starting sector from above: mkpart primary <start> <end>
6 Exit parted: quit
7 Check the filesystem: sudo e2fsck -f /dev/sdXX
8 Resize filesystem: sudo resize2fs /dev/sdXX
I'd like to increase partition #2 from 200 Gig to 300 Gig using gnu parted.
(parted) p
Modell: ATA WDC WD15EARX-00Z (scsi)
Festplatte /dev/sda: 1500GB
Sektorgröße (logisch/physisch): 512B/4096B
Partitionstabelle: gpt
Disk Flags:
Nummer Anfang Ende Größe Dateisystem Name Flags
1 2048s 25167871s 25165824s ext4 Linux filesystem
2 25167872s 444598271s 419430400s ext4
or with unit set to GiB:
Nummer Anfang Ende Größe Dateisystem Name Flags
1 0,00GiB 12,0GiB 12,0GiB ext4 Linux filesystem
2 12,0GiB 212GiB 200GiB ext4
What is the correct way for doing this?
Last edited by goodboy (2012-10-28 18:33:43)

goodboy wrote:No, I'm not using gparted but "gnu parted", the command line tool, as I already mentioned above. From what I understood so far, gparted doesn't handle GPT** disks at all.
From the wiki gparted topic:
GParted is a GTK+ frontend to GNU Parted and the official GNOME Partition Editor application.
I think gparted can do anything gnu parted can do. The warning about ext4 in the topic you linked is from 2009, and recommends using gparted with a version higher than 0.6.2-2. Gparted 0.14.0-1 is currently in the Arch repo, so I think it's probably safe.
Last edited by 2ManyDogs (2012-10-28 18:29:03)

[Solved] Grub Error 13, ext4 and 2.6.28.1

Hi guys!!!
I have formatted my laptop disk in new ext4 format, following wiki instructions:
http://wiki.archlinux.org/index.php/Cre … _Partition
and all wok fine.
But after today update (pacman -Syu), my arch don't boot.
Grub messages (lastest grub version, normal grub no grub2):
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/.............
Error 13: invalid or unsupported executable format
No Normal image nor Fallback image boot.
Any suggestion?
P.D. Sorry for my englis xD
Check wiki solution:
http://wiki.archlinux.org/index.php/Cre … B_Error_13
Last edited by superchango (2009-01-23 02:19:19)

from grub's web site:
13 : Invalid or unsupported executable format
This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).
I think your vmlinuz26 file is wrong in some ways, or grub can't read ext4 correctly (I have done a fresh install with ext4, but I have made a separate partition for /boot in ext2)
superchango wrote:following wiki instructions:
http://wiki.archlinux.org/index.php/Cre … _Partition
did you create from scratch or did you convert from ext3 ?

Question about "fast fsck", ext4 and defragmentation status [SOLVED]

I'm trying to use fsck to do a defacto defragmentation check of an ext4 partition. I'm running fsck from a live cd (SysRescue 1.15) to check one of my ext4 partitions. The ext4 partition is unmounted, of course.
The check goes amazingly fast, but it doesn't give me any info about the percentage of non-contiguous inodes, which I understand to be the the same as the percentage of defragmentation (true?). I'm thinking this is because of the new "fast fsck" feature of ext4, as detailed below.
My question: can I force a "slow fsck" in order to get a complete check including the inode-contiguity info? Or is there another way to get at the defragmentation status using fsck?
Thanks.
FWIW, here's the info on "fast fsck" from the excellent http://kernelnewbies.org/Ext4 page:
2.7. Fast fsck
Fsck is a very slow operation, especially the first step: checking all the inodes in the file system. In Ext4, at the end of each group's inode table will be stored a list of unused inodes (with a checksum, for safety), so fsck will not check those inodes. The result is that total fsck time improves from 2 to 20 times, depending on the number of used inodes (http://kerneltrap.org/Linux/Improving_f … ds_in_Ext4). It must be noticed that it's fsck, and not Ext4, who will build the list of unused inodes. This means that you must run fsck to get the list of unused inodes built, and only the next fsck run will be faster (you need to pass a fsck in order to convert a Ext3 filesystem to Ext4 anyway). There's also a feature that takes part in this fsck speed up - "flexible block groups" - that also speeds up filesystem operations.
Last edited by dhave (2009-02-17 22:09:49)

Ranguvar wrote:
Woot! http://fly.isti.cnr.it/cgi-bin/dwww/usr … z?type=man
fsck.ext4 -E fragcheck /dev/foo
Thanks, Ranguvar. I had read the man page for fsck.ext3, but I hadn't run across the page for fsck.ext4. The link was helpful.

[SOLVED] EXT4 Data Corruption Bug Linux 3.6.2 & 3.6.3

Be careful
EXT4 Data Corruption Bug Hits Stable Linux Kernels
http://www.phoronix.com/scan.php?page=n … px=MTIxNDQ
https://lkml.org/lkml/2012/10/23/779
Edited: Removed the [ALERT] label.
Last edited by ontobelli (2012-11-01 04:58:43)

headkase wrote:
Even though it is a severe bug the chances of it happening to you are low. You have to unmount and immediately remount an EXT4 partition twice in a row for it to happen. On a normally operating system that is not a normal thing to happen. Just wait on your desktop for 5 minutes before rebooting again.
Arch, as a general rule, tends to stick as close to upstream as possible. I'm sure the devs are very competent people but a quick hack or branch revert has the possibility of introducing issues of its own. With the chance of the bug occurring low on a normally operating system I think it is better to wait for a fix from upstream.
Well maybe i am a bit over stressed about this since with this computer i have quite a lot of troube which i cannot find solutions to. Also a kernel panic after a reboot this morning -probably not related to this- got me in a bad mood.
Anyway.

[SOLVED] badblocks ext4

Similar Messages

Maybe you are looking for