You are not logged in.
I had a short power outage last night and apparently my PC didn't appreciate that much.
Since then, it hangs for about 1-2 minutes while mounting the filesystems. Afterwards, it seems to load just fine.
To be more specific, it hangs while mounting /dev/sda2 (which should be mounted on /home).
I figured that out after a 'shutdown -rF now' when fsck failed miserably while checking sda2.
Also note that this is still happening even after re-formatting the partition.
Any ideas?
Here's my fstab:
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
UUID=49b4f420-239d-4645-9746-038b54b0f5d7 /boot ext4 relatime,defaults 0 1
UUID=dd3f343e-a123-460c-98df-aac65d6f4501 / ext4 relatime,defaults 0 1
UUID=c65aa4a1-6a8e-4118-8a8d-fc0f4eabba29 /usr ext4 relatime,defaults 0 1
UUID=a9f722f8-0914-4b1c-829a-a892a3cea7f1 /var ext4 relatime,defaults 0 1
UUID=914f701f-9481-47cf-96e8-d95dff47a9b4 /home ext4 relatime,defaults 0 2
UUID=7c2d02d1-ad0f-4356-a0fd-97010408a98a none swap defaults 0 0
tmpfs /tmp tmpfs nodev,nosuid 0 0The more important part of the output of blkid:
/dev/sda1: LABEL="boot" UUID="49b4f420-239d-4645-9746-038b54b0f5d7" TYPE="ext4"
/dev/sda2: UUID="914f701f-9481-47cf-96e8-d95dff47a9b4" TYPE="ext4"
/dev/sda3: LABEL="SHARED" UUID="64BCFFABBCFF7640" TYPE="ntfs"
/dev/sda5: LABEL="root" UUID="dd3f343e-a123-460c-98df-aac65d6f4501" TYPE="ext4"
/dev/sda6: LABEL="usr" UUID="c65aa4a1-6a8e-4118-8a8d-fc0f4eabba29" TYPE="ext4"
/dev/sda7: UUID="a9f722f8-0914-4b1c-829a-a892a3cea7f1" TYPE="ext4"
/dev/sda8: UUID="7c2d02d1-ad0f-4356-a0fd-97010408a98a" TYPE="swap"
/dev/sda9: UUID="d7927636-167d-4215-8264-556befde22d2" TYPE="ext4" And the last 28 lines of /var/log/boot:
Mon Aug 13 00:42:05 2012: :: Adjusting system time and setting kernel time zone [BUSY] [DONE]
Mon Aug 13 00:42:05 2012: :: Starting udev daemon [BUSY] [DONE]
Mon Aug 13 00:42:05 2012: :: Triggering udev uevents [BUSY] [DONE]
Mon Aug 13 00:42:05 2012: :: Loading user-specified modules [BUSY] [DONE]
Mon Aug 13 00:42:05 2012: :: Waiting for udev uevents to be processed [BUSY] [DONE]
Mon Aug 13 00:42:05 2012: :: Configuring virtual consoles [BUSY] %G [DONE]
Mon Aug 13 00:42:05 2012: :: Bringing up loopback interface [BUSY] [DONE]
Mon Aug 13 00:42:05 2012: :: Checking filesystems [BUSY] boot: clean, 335/26104 files, 35537/104388 blocks
Mon Aug 13 00:42:05 2012: /dev/sda7: clean, 19296/344064 files, 750745/1375557 blocks
Mon Aug 13 00:42:05 2012: /dev/sda2: clean, 231517/32768512 files, 256267993/524289304 blocks
Mon Aug 13 00:42:05 2012: [DONE]
Mon Aug 13 00:42:05 2012: :: Remounting root and API filesystems [BUSY] [DONE]
Mon Aug 13 00:42:05 2012: :: Mounting local filesystems [BUSY] [DONE]
Mon Aug 13 00:43:12 2012: :: Activating swap [BUSY] [DONE]
Mon Aug 13 00:43:12 2012: :: Initializing random seed [BUSY] [DONE]
Mon Aug 13 00:43:12 2012: :: Removing leftover files [BUSY] [DONE]
Mon Aug 13 00:43:13 2012: :: Setting hostname: arch [BUSY] [DONE]
Mon Aug 13 00:43:13 2012: :: Saving dmesg log [BUSY] [DONE]
Mon Aug 13 00:43:13 2012: INIT: Entering runlevel: 5
Mon Aug 13 00:43:13 2012: :: Starting Syslog-NG [BUSY] [DONE]
Mon Aug 13 00:43:13 2012: :: Starting network [BUSY] [DONE]
Mon Aug 13 00:43:14 2012: :: Starting NTP Daemon [BUSY] [DONE]
Mon Aug 13 00:43:15 2012: :: Starting crond daemon [BUSY] [DONE]
Mon Aug 13 00:43:15 2012: :: Starting D-BUS system messagebus [BUSY] [DONE]
Mon Aug 13 00:43:15 2012: :: Starting Secure Shell Daemon [BUSY] [DONE]
Mon Aug 13 00:43:15 2012: :: Starting Samba Server [BUSY] [DONE]
Mon Aug 13 00:43:16 2012: :: Restoring ALSA Levels [BUSY] [DONE]
Mon Aug 13 00:43:16 2012: :: Starting Up Sensors [BUSY] [DONE]Last edited by abiotic (2012-08-13 17:35:10)
Offline
Hi abiotic,
Do you know if you're hard drive supports SMART? You might want to use smartctl to see if you have a damaged hard drive.
This might explain the behavior.
Remember, when using Linux, you're the one in control
http://www.linux-answered.com
Offline
Do you know if you're hard drive supports SMART?
Not sure.
Also worth mentioning that since I'm dual-booting w/ Sabayon, I tried to mount the partition there and it worked without problems.
And fsck -cfrv /dev/sda2 works properly on both OS and reports no problem if I run the command after they finish loading (with sda2 unmounted, of course).
Offline
Using `mount -o remount`, could you see if this is caused by one specific mountpoint? Maybe then you can strace that to see what is happening.
Offline
I don't see anything wrong here...
Is there anything specific I should be looking for when issuing the command?
Here's the output of 'mount -o remount'
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=2023964k,nr_inodes=505991,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda5 on / type ext4 (rw,relatime,data=ordered)
/dev/sda6 on /usr type ext4 (rw,relatime,data=ordered)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime)
/dev/sda1 on /boot type ext4 (rw,relatime,data=ordered)
/dev/sda7 on /var type ext4 (rw,relatime,data=ordered)
/dev/sda2 on /home type ext4 (rw,relatime,data=ordered)
binfmt on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
gvfs-fuse-daemon on /home/abi0tic/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)The one mountpoint causing problems is /home, as I said earlier.
If i remove it from /etc/fstab, the system boots up really fast. Afterwards, when I do a 'mount /dev/sda2 /home' I need to wait for a whole minute until it's done. Again, this is only true for Arch. Sabayon can mount sda2 on /home really fast and it doesn't seem to have any problems. I'm beginning to doubt that there's anything wrong with the partition itself.
Could something else be broken instead?
strace -c mount /dev/sda2 /home :
╔══[root]══[~]══[#]
╚══>strace -c mount /dev/sda2 /home
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
100.00 54.553109 54553109 1 mount
0.00 0.000154 1 105 read
0.00 0.000000 0 14 open
0.00 0.000000 0 16 close
0.00 0.000000 0 8 5 stat
0.00 0.000000 0 11 fstat
0.00 0.000000 0 2 lstat
0.00 0.000000 0 102 lseek
0.00 0.000000 0 18 mmap
0.00 0.000000 0 10 mprotect
0.00 0.000000 0 4 munmap
0.00 0.000000 0 3 brk
0.00 0.000000 0 5 1 ioctl
0.00 0.000000 0 3 1 access
0.00 0.000000 0 1 execve
0.00 0.000000 0 1 uname
0.00 0.000000 0 2 fcntl
0.00 0.000000 0 5 3 readlink
0.00 0.000000 0 3 getuid
0.00 0.000000 0 2 getgid
0.00 0.000000 0 3 geteuid
0.00 0.000000 0 2 getegid
0.00 0.000000 0 2 prctl
0.00 0.000000 0 1 arch_prctl
0.00 0.000000 0 2 fadvise64
0.00 0.000000 0 3 1 openat
0.00 0.000000 0 2 1 newfstatat
------ ----------- ----------- --------- --------- ----------------
100.00 54.553263 331 12 totalLast edited by abiotic (2012-08-13 12:08:24)
Offline
What you can try is the following,
Copy data,
Delete partition,
Create partition,
Create filesystem
Copy data? :-)
I know it's a lousy fix but it might help.
Remember, when using Linux, you're the one in control
http://www.linux-answered.com
Offline
As tempting as that is, I'd rather find out what's causing the problem so I know how to fix it if it happens again without having to backup and restore data.
Besides, restoring 400+ GB of data will take a looooong time.
I'll wait for a few more ideas before giving up ![]()
Last edited by abiotic (2012-08-13 12:18:32)
Offline
Fixed by restoring the system from a 2 week old backup.
/home (/dev/sda2) was left unchanged.
Offline
Fixed by restoring the system from a 2 week old backup.
/home (/dev/sda2) was left unchanged.
lol :-D, good to hear that the problem is solved!
Remember, when using Linux, you're the one in control
http://www.linux-answered.com
Offline