1 |
2014-03-16 8:24 GMT-06:00 Dale <rdalek1967@×××××.com>: |
2 |
|
3 |
> Howdy, |
4 |
> |
5 |
> I got this when rebooting after we had a power outage. I have a UPS so |
6 |
> I was able to perform a regular shutdown. |
7 |
> |
8 |
> |
9 |
> [ 2.567061] hub 8-1:1.0: state 7 ports 4 chg 0000 evt 0000 |
10 |
> [ 2.567069] hub 8-1:1.0: hub_suspend |
11 |
> [ 2.579644] usb 8-1: usb auto-suspend, wakeup 1 |
12 |
> [ 2.591677] hub 8-0:1.0: hub_suspend |
13 |
> [ 2.591682] usb usb8: bus auto-suspend, wakeup 1 |
14 |
> [ 3.362374] dracut: root has been mounted 29 times without being |
15 |
> checked, check forced. |
16 |
> [ 3.363014] dracut: root: 28323/1525920 files (0.4% non-contiguous), |
17 |
> 580665/6102684 blocks |
18 |
> [ 3.364957] dracut: Mounting |
19 |
> /dev/disk/by-uuid/888352dd-9c91-4a9f-9595-cd0e74b74ee7 with -o defaults,ro |
20 |
> [ 3.474224] EXT4-fs (sda6): mounted filesystem with ordered data |
21 |
> mode. Opts: (null) |
22 |
> [ 3.522894] dracut: Mounted root filesystem /dev/sda6 |
23 |
> [ 3.568630] dracut: Mounting /usr with -o defaults,ro |
24 |
> [ 3.600028] dracut: mount: special device /dev/disk/by-label/usr does |
25 |
> not exist |
26 |
> |
27 |
|
28 |
Seems like the block device for /usr couldn't be found by it's label, root |
29 |
partition seems fine after check and properly mounted, so I'd say it has |
30 |
nothing to do. |
31 |
|
32 |
|
33 |
> [ 3.601749] dracut Warning: Mounting /usr to /sysroot/usr failed |
34 |
> [ 3.602452] dracut Warning: *** Dropping you to a shell; the system |
35 |
> will continue |
36 |
> [ 3.603419] dracut Warning: *** when you leave the shell. |
37 |
> [ 3.604892] dracut Warning: |
38 |
> [ 3.849621] blkid (2070) used greatest stack depth: 4576 bytes left |
39 |
> + '[' -f /run/initramfs/init.log ']' |
40 |
> root@fireball / # |
41 |
> |
42 |
> |
43 |
> It seems to me that the / file system needed to be checked. For that |
44 |
> reason, it couldn't mount /usr after the check was performed. That's my |
45 |
> thinking on this. Anyone think otherwise? Is this a one off event or |
46 |
> should I be concerned about this? |
47 |
> |
48 |
|
49 |
Is the block device corresponding to /usr available under another directory |
50 |
in /dev? if not something wrong might be going on with that block device. |
51 |
I personally prefer using UUIDs for finding partitions at boot, they are |
52 |
more fail-proof. |
53 |
|
54 |
Is there some way to avoid this in the future without disabling file |
55 |
> system check for /? |
56 |
> |
57 |
|
58 |
Again, maybe UUIDs. |
59 |
|
60 |
> |
61 |
> Another related LVM question. I have some partitions on LVM. If I |
62 |
> moved the drives to another system, would the new LVMs be found on the |
63 |
> new system or is there some magic involved to find and get them |
64 |
> mounted? Example. My /home is on its own LVM partition. If I moved |
65 |
> the drive that has that on it, would the new system see it or would I |
66 |
> have to do something to make it see it? I suspect and wouldn't want it |
67 |
> to mount automatically. I'd just want to be able to see it and mount it |
68 |
> if needed. Sort of a question I have always wondered about. |
69 |
> |
70 |
> |
71 |
|
72 |
On my experience as long, as udev and lvm are running on the receiving |
73 |
system, they should be found and placed for access under /dev, not mounted |
74 |
automatically. |
75 |
if for some reason it doesnt happen, its easy to do a 'pvscan' to see if |
76 |
the physical volume is recognized, and if it is, 'vgchange -ay |
77 |
volume_group_name ' activates all LVs. |
78 |
|
79 |
|
80 |
> Thanks much. |
81 |
> |
82 |
> Dale |
83 |
> |
84 |
> :-) :-) |
85 |
> |
86 |
> P. S. For those who recall my brother having cancer. He is close to |
87 |
> the end of his treatments. Lost a LOT of weight but hanging in there. |
88 |
> |
89 |
> |