Re: [arch-general] AARG! kinit: cannot open dev(8,7) kernel panic
On Sonntag, 17. Mai 2009 10:02 David C. Rankin, J.D.,P.E. wrote: > After switching /boot/grub/menu.lst and /etc/fstab from disk/by-uuid labels > to the standard /dev/sda# labels everything boots and runs fine. Now the > question of why the by-uuid labels did not work? I updated the uuid lables > in each file with the right value from /dev/disk/by-uuid using strick copy > and paste to eliminate typos and then verified 3 times, they were right. There is a longer existing second mechanism in linux named disklabel. See here: http://wiki.archlinux.org/index.php/Persistent_block_device_naming The advantage is that you can recreate partitions without a problem if you use the same name for a disklabel as before. The disadvantage is that a lot of people think that this labels can get lost instead this never happens to me.-) See this as an optional information about your problem. See you, Attila
Re: [arch-general] hal has lost its mind again.
On or about Sunday 17 May 2009 at approximately 03:16:26 David C. Rankin, J.D.,P.E. composed: > Listmates, > > On my laptop, automounting of usb drives and mmc/sd cards were working > fine, now I get the "...mount.removable no <-- (action, result)" Full error > dialog: > > http://www.3111skyline.com/download/Archlinux/bugs/hal-mount.removable.jpg > > The system configures the drives or cards just fine, it just will not > create the directory under /media to allow access. It is really ironic > because the drives/cards are fully accessible under "media:/". So, nothing > in "/media", but OK in "media:/". > > I am concerned that changes made > in /etc/hal/fdi/policy/20-ntfs-config-write-policy.fdi to allow NTFS mounts > messed something else up. The file contains: > > > > >bool="true"> >type="string">ntfs-3g >type="string">ntfs-3g > > > > > which is straight from the wiki. The everything log contains the > following: > > May 17 02:50:23 alchemy kernel: tifm_core: MMC/SD card detected in socket > 0:1 May 17 02:50:23 alchemy kernel: mmc1: new SD card at address e624 > May 17 02:50:23 alchemy kernel: isa bounce pool size: 16 pages > May 17 02:50:23 alchemy kernel: mmcblk0: mmc1:e624 SD02G 1.89 GiB > May 17 02:50:23 alchemy kernel: mmcblk0: p1 > May 17 02:55:20 alchemy hald: mounted /dev/mmcblk0p1 on behalf of uid 0 > May 17 03:06:54 alchemy kernel: ACPI: EC: missing confirmations, switch off > interrupt mode. > > I don't know if the ACPI kernel message is evidence of the problem, but > I > included it just in case. I am slowly trying to make friends with hal/dbus, > but I could use any help you can give in sorting this out. Thanks. Another interesting note. When I inserted the card, there was no entry created in /media. Now 10 minutes later after I have been copying the photos, etc., the mount of /dev/mmcblk0p1 has *appeared* mounted on /media/disk? Huh? I can't tell you when it appeared, but I can tell you that for at least 4-5 minutes. So why the initial error and why the magical appearance after the error telling me it wasn't going to be mounted? What to check for more info? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
[arch-general] hal has lost its mind again.
Listmates, On my laptop, automounting of usb drives and mmc/sd cards were working fine, now I get the "...mount.removable no <-- (action, result)" Full error dialog: http://www.3111skyline.com/download/Archlinux/bugs/hal-mount.removable.jpg The system configures the drives or cards just fine, it just will not create the directory under /media to allow access. It is really ironic because the drives/cards are fully accessible under "media:/". So, nothing in "/media", but OK in "media:/". I am concerned that changes made in /etc/hal/fdi/policy/20-ntfs-config-write-policy.fdi to allow NTFS mounts messed something else up. The file contains: ntfs-3g ntfs-3g which is straight from the wiki. The everything log contains the following: May 17 02:50:23 alchemy kernel: tifm_core: MMC/SD card detected in socket 0:1 May 17 02:50:23 alchemy kernel: mmc1: new SD card at address e624 May 17 02:50:23 alchemy kernel: isa bounce pool size: 16 pages May 17 02:50:23 alchemy kernel: mmcblk0: mmc1:e624 SD02G 1.89 GiB May 17 02:50:23 alchemy kernel: mmcblk0: p1 May 17 02:55:20 alchemy hald: mounted /dev/mmcblk0p1 on behalf of uid 0 May 17 03:06:54 alchemy kernel: ACPI: EC: missing confirmations, switch off interrupt mode. I don't know if the ACPI kernel message is evidence of the problem, but I included it just in case. I am slowly trying to make friends with hal/dbus, but I could use any help you can give in sorting this out. Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Re: [arch-general] AARG! kinit: cannot open dev(8,7) kernel panic
On or about Saturday 16 May 2009 at approximately 20:28:49 David C. Rankin, J.D.,P.E. composed: > On or about Saturday 16 May 2009 at approximately 20:13:11 pyther composed: > > Try replacing the disk-by-uuid stuff with direct paths to the device > > nodes (ex. /dev/sda2, etc). If you can get this to work then start > > switching back to disk-by-uuid. > > > > ~pyther > > Hmm, > > I'll give it a go and report back. My fingers are getting sore from all > the mount and chroot typing though ;-) Ok, After switching /boot/grub/menu.lst and /etc/fstab from disk/by-uuid labels to the standard /dev/sda# labels everything boots and runs fine. Now the question of why the by-uuid labels did not work? I updated the uuid lables in each file with the right value from /dev/disk/by-uuid using strick copy and paste to eliminate typos and then verified 3 times, they were right. I guess I'll go back and substitute uuid labels one-by-one and see where it fails. My luck, it will work this time. If I find a failure, then we will have narrowed the error down. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
