> Failing boot sector? > Some other sector it has to read is failing? > Check the logs. Try (from smartmontools): ~ I don't know exactly which of your questions/suggestions running: ~ smartctl -A /dev/sda | egrep -i "sector|realloc" ~ relates to, but it didn't report any error message. Without grep I got: ~ $ sudo smartctl -A /dev/sda smartctl 5.43 2012-05-01 r3539 [i686-linux-3.3.7] (local build) Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 115 082 006 Pre-fail Always - 96695847 3 Spin_Up_Time 0x0003 096 095 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 365 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 17316569764 9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 2678 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 395 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 059 045 045 Old_age Always In_the_past 41 (Min/Max 40/41) 194 Temperature_Celsius 0x0022 041 055 000 Old_age Always - 41 (0 23 0 0 0) 195 Hardware_ECC_Recovered 0x001a 078 057 000 Old_age Always - 102323103 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always - 0 $ > Because your disk is sleeping? ~ That I think may be the reason why. I did notice and check that it always seems to happen after suspending my box, even if you unmount all drives before, but what I don't get is that may people would be complaining about that same problem. I have seem people complaining all the time about hardware-related issues with suspending a box, but not such delays and I always thought when you awaken your box after suspending it, it should go to its initial state. Is there a way to "awaken" all harddrive/partitions you are using? ~ > Could it be a missing swap partition is slowing down drive access? ~ $ cat /proc/swaps Filename Type Size Used Priority /dev/zram0 partition 1942352 0 0 ~ > I don't know if you were connected to the internet ~ I wasn't, but I have notice weird things happening when I am and, of course, my work horse box I don't connect to the Internet at all ~ > So... fdisk -l took 38 seconds - which is a bit much. ~ Yep! Exactly 38 seconds!?! ~ $ date; fdisk -l; date Fri Sep 28 07:13:45 UTC 2012 Disk /dev/sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 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: 0x00052568 Device Boot Start End Blocks Id System /dev/sda1 63 39086144 19543041 c W95 FAT32 (LBA) /dev/sda2 39086145 78140159 19527007+ c W95 FAT32 (LBA) /dev/sda3 78140160 234420479 78140160 83 Linux /dev/sda4 234420480 488396799 126988160 5 Extended /dev/sda5 234420543 353429999 59504728+ c W95 FAT32 (LBA) /dev/sda6 353430063 372981104 9775521 c W95 FAT32 (LBA) /dev/sda7 372981168 392516144 9767488+ c W95 FAT32 (LBA) /dev/sda8 392516208 431570159 19526976 83 Linux /dev/sda9 431570223 441353744 4891761 83 Linux /dev/sda10 441353808 446253569 2449881 83 Linux /dev/sda11 446253633 449819999 1783183+ 83 Linux /dev/sda12 449822720 488396799 19287040 83 Linux Fri Sep 28 07:14:23 UTC 2012 knoppix@Microknoppix:~$ date; fdisk -l; date Fri Sep 28 07:14:41 UTC 2012 Disk /dev/sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 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: 0x00052568 Device Boot Start End Blocks Id System /dev/sda1 63 39086144 19543041 c W95 FAT32 (LBA) /dev/sda2 39086145 78140159 19527007+ c W95 FAT32 (LBA) /dev/sda3 78140160 234420479 78140160 83 Linux /dev/sda4 234420480 488396799 126988160 5 Extended /dev/sda5 234420543 353429999 59504728+ c W95 FAT32 (LBA) /dev/sda6 353430063 372981104 9775521 c W95 FAT32 (LBA) /dev/sda7 372981168 392516144 9767488+ c W95 FAT32 (LBA) /dev/sda8 392516208 431570159 19526976 83 Linux /dev/sda9 431570223 441353744 4891761 83 Linux /dev/sda10 441353808 446253569 2449881 83 Linux /dev/sda11 446253633 449819999 1783183+ 83 Linux /dev/sda12 449822720 488396799 19287040 83 Linux Fri Sep 28 07:15:19 UTC 2012 ~ > Question: How long does "fdisk -l /dev/sda" take? (note: specifying "/dev/sda" explicitly, rather than fdisk figure it out) ~ knoppix@Microknoppix:~$ date; fdisk -l /dev/sda; date Fri Sep 28 07:15:38 UTC 2012 Disk /dev/sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 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: 0x00052568 Device Boot Start End Blocks Id System /dev/sda1 63 39086144 19543041 c W95 FAT32 (LBA) /dev/sda2 39086145 78140159 19527007+ c W95 FAT32 (LBA) /dev/sda3 78140160 234420479 78140160 83 Linux /dev/sda4 234420480 488396799 126988160 5 Extended /dev/sda5 234420543 353429999 59504728+ c W95 FAT32 (LBA) /dev/sda6 353430063 372981104 9775521 c W95 FAT32 (LBA) /dev/sda7 372981168 392516144 9767488+ c W95 FAT32 (LBA) /dev/sda8 392516208 431570159 19526976 83 Linux /dev/sda9 431570223 441353744 4891761 83 Linux /dev/sda10 441353808 446253569 2449881 83 Linux /dev/sda11 446253633 449819999 1783183+ 83 Linux /dev/sda12 449822720 488396799 19287040 83 Linux Fri Sep 28 07:15:38 UTC 2012 ~ > If this is a lot shorter, then your problem may be related to how > fdisk chooses a default device to look at, and the contents of > /proc/partitions becomes interesting... ~ knoppix@Microknoppix:~$ cat /proc/partitions major minor #blocks name 240 0 9740032 cloop0 251 0 1942356 zram0 8 0 244198584 sda 8 1 19543041 sda1 8 2 19527007 sda2 8 3 78140160 sda3 8 4 1 sda4 8 5 59504728 sda5 8 6 9775521 sda6 8 7 9767488 sda7 8 8 19526976 sda8 8 9 4891761 sda9 8 10 2449881 sda10 8 11 1783183 sda11 8 12 19287040 sda12 11 0 4084128 sr0 2 0 4 fd0 knoppix@Microknoppix:~$ ~ So, I guess my questions are" ~ What is going on here? ~ How do you make sure your disks are safely awakened after your system awakens from "suspended" mode? ~ and by the way I am on: ~ $ uname -a Linux Microknoppix 3.3.7 #38 SMP PREEMPT Tue May 22 06:21:01 CEST 2012 i686 GNU/Linux ~ and I need to use "fdisk -l" as part of a script that uses the "Disk identifier" as part of the name of the log file. Can you get the "Disk identifier" any other (somewhat) -standard- way? ~ lbrtchx -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFakBwigBJXAid=fvezwbox_vshogwwd0ipy69cvogxmzwo...@mail.gmail.com
