Frequently Asked Questions about iOS 15 Update Yes, it can seem a slow speed, but think that CPU has to check every sector, so drive has to stop transferring when CPU is checking sectors it has already in main memory.Ħ.
Supposing it's 4KB, yor OS is reading 645,56 * 4 KB = 2582,24 KB per second.
If 'hdparm sector size' is 4KB, your drive size has 300 GB approx.ĥ.- And I don't know how long is 'iostat sector size' in your OS. It depends on what your OS and the utility you're using assumes a sector is: If 'hdparm sector size' is 1KB, your drive size has 1,1 TB approx. Sr0 0,94 0,00 0,06 0,00 4,02 0,00 62,87 0,01 127,94 101,49 0,65Ģ.- Your /dev/dsa1 partition is having a lot of I/O activity, so it's very probable that the e2fsck is still runningģ.- Moreover, your /dev/sda1 is providing 645 reads sectors per second and 1 write per second to the operating system!Ĥ.- I don't know how long your drive is. Linux 2.6.28-11-generic (ubuntu) 09/08/09 _i686_ (2 CPU)Īvg-cpu: %user %nice %system %iowait %steal %idleĭevice: rrqm/s wrqm/s r/s w/s rsec/s wsec/s avgrq-sz avgqu-sz await svctm %util It's been about 40 hours now, and iostat -x If all this tells you something new, please let me know.ĭo you guys think I will have any chance with recovery tools like those mentioned here: As time passes by I'm losing my hopes on e2fsck finishing succesfully. In consequence -gedack explained it- I don't have any output from the e2fsck command. ata2.00: configured for I'm running e2fsck from inside GParted. ata2.00: ATAPI: Slimtype DVD A DS8A2L-A, 7H63, max UDMA/100 ata6: SATA max UDMA/133 abar port 0x947053 ata5: SATA max UDMA/133 abar port 0x947053 ata2: SATA max UDMA/133 abar port 0x947051 ata1: SATA max UDMA/133 abar port 0x947051 So you think it's possible that e2fsck is actually repairing the file system at sda1, right? I should wait maybe another 24 dmesg | grep UDMA I can't mount the root partition at all but again, I really don't care about it (it just contained a tipycal Ubuntu install, nothing I can't replicate easily). I was able to mount the home partition but it appeared empty. Sda4 holds the root partition, sda2 is my swap partition and sda1 is my home partition. EXT3 FS on sda1, internal just posting it in case any of this makes sense to you. sd 0:0:0:0: Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Is there a way to know that output from Gparted? I know that if I had run e2fsck in a terminal I would have some output telling me what's going on. The disk led is blinking so it looks like it's doing something but isn't this taking too long for a 106 GB amount of data? It's been almost 24 hours now and e2fsck -f -y -v /dev/sda1 is still running. I can always reinstall, but my home partition is very important.) (I don't care that much about the root partition. So I decided to verify the partition with Gparted.
I'm running an Ubuntu LiveCD and Gparted and Nautilus both say my home partition still holds some 106 GB in there (it's a 142 GB partition). However, my two partitions (root and home) appear "empty" now and the system won't boot. I tried Paragon yesterday and everything seemed to work fine. But for some reason Acronis stopped recognizing my Ubuntu partitions. Gparted is usually too slow for resizing, so I frequently use Acronis for that.