I have a Debian OpenBox that boots from any usb port. The Debian LXDE will only boot from one specific port. It needs to look at all of them to find and be root, and mount the root filesystem by UUID. Both are full installs to 16GB flash drives.
That is not being done.
It says during boot after initrd loads :
Then it won't mount the root filesystem which is the UUID it starts booting from.
grub2 searches, finds the correct UUID, does initrd, but then won't complete the boot and mount the darn root filesystem. Says that UUID does not exist except from one specific USB
port when booted from, not the others.
Perhaps some parameter needs to be changed so it does a better job of mounting the root filesystem, specified by grub2 with the UUID. Then remake initrd so it does it all the time ?
I don't know what change to make so the initial ramdisk would work right then.
Probably a simple fix, one adjustment to make. Any ideas ?
THX
Patrick
Last edited by jim mcnamara; 04-10-2013 at 05:44 PM..
On a HP-UX box, I can execute the sar command which will give me the device, %busy, etc. I would like to know how to take a given device name and determine on which filesystem it's located when I do a bdf.
I've done some searching through the posts but so far have not had any luck in... (2 Replies)
Hi guys,
The data store behind our CVS server is on a windows box for reasons best known to my predecessors. Therefore the CVSROOT is a cifs mount point, actually it's /mnt/CVS but that's by the by.
The problem I have is that CVSWeb fails to recognise mount points as directories, and tells... (0 Replies)
i have a Simple Tech hard drive that i use between two computers. it is formatted to ntfs. i have a dell desktop with Ubuntu 7.10 and Ubuntu 8.04 and Windows XP Home. and i have a laptop with Ubuntu 7.10 and Ubuntu 8.04. the laptop recognizes the hard drive on both 8.04 and 7.10 but my desktop... (9 Replies)
Hello:
NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Greetings,
I have a oracle database server and i keep getting grid control message
Metric=Disk Device Busy (%)
Metric Value=98.66
Disk Device=ssd430
Severity=Critical
Message=Disk Device ssd430 is 98.66% busy.
so I am trying to correlate the ssd430 to the filesystem. I understand this... (3 Replies)
Hi all,
I'm attempting to remove some EMC hdisk devices which we recently had made available to one of our backup servers. This is an AIX 5.3 server. When I try doing an rmdev I get the following:
root@********:/dev# rmdev -d -l hdisk495
Method error (/usr/lib/methods/ucfgdevice):
... (2 Replies)
Dear all,
We are facing prolem when we are going to mount AIX filesystem, the system returned the following error
0506-307The AFopen call failed
: A file or directory in the path name does not exist.
But when we ls filesystems in the /etc/ directory it show
-rw-r--r-- 0 root ... (2 Replies)
Hi,
on running system, a disk was added
hdiskx
then importvg -y oraclevg hdiskx
but hdiskx was actually a rootvg so since rootvg was already present in the existing system this happened
Imported hdisk2 which was rootvg as importvg -y oraclevg hdisk2 in server since rootvg already... (1 Reply)
I am able to mount samba but it just won't mount when i reboot system
what is stopping it from mounting after reboot?
I mounted before reboot but right after reboot...i ran mount
# mount
/dev/mapper/vg_sda2-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs... (0 Replies)
Hi all,
Q1) Due to application requirement, i am required to have more swap space.
Currently my swap is on a partition with 32GB.
I have another partition with 100GB, but it already has a UFS filesystem on it.
Can i just swap -d /dev/dsk/current32gb and swap -a /dev/dsk/ufs100gb ?
Will... (17 Replies)
Discussion started by: javanoob
17 Replies
LEARN ABOUT POSIX
systemd-cryptsetup-generator
SYSTEMD-CRYPTSETUP-GENERATOR(8) systemd-cryptsetup-generator SYSTEMD-CRYPTSETUP-GENERATOR(8)NAME
systemd-cryptsetup-generator - Unit generator for /etc/crypttab
SYNOPSIS
/lib/systemd/system-generators/systemd-cryptsetup-generator
DESCRIPTION
systemd-cryptsetup-generator is a generator that translates /etc/crypttab into native systemd units early at boot and when configuration of
the system manager is reloaded. This will create systemd-cryptsetup@.service(8) units as necessary.
systemd-cryptsetup-generator implements systemd.generator(7).
KERNEL COMMAND LINE
systemd-cryptsetup-generator understands the following kernel command line parameters:
luks=, rd.luks=
Takes a boolean argument. Defaults to "yes". If "no", disables the generator entirely. rd.luks= is honored only by initial RAM disk
(initrd) while luks= is honored by both the main system and the initrd.
luks.crypttab=, rd.luks.crypttab=
Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any devices configured in /etc/crypttab
(luks.uuid= will still work however). rd.luks.crypttab= is honored only by initial RAM disk (initrd) while luks.crypttab= is honored
by both the main system and the initrd.
luks.uuid=, rd.luks.uuid=
Takes a LUKS superblock UUID as argument. This will activate the specified device as part of the boot process as if it was listed in
/etc/crypttab. This option may be specified more than once in order to set up multiple devices. rd.luks.uuid= is honored only by
initial RAM disk (initrd) while luks.uuid= is honored by both the main system and the initrd.
If /etc/crypttab contains entries with the same UUID, then the name, keyfile and options specified there will be used. Otherwise, the
device will have the name "luks-UUID".
If /etc/crypttab exists, only those UUIDs specified on the kernel command line will be activated in the initrd or the real root.
luks.name=, rd.luks.name=
Takes a LUKS super block UUID followed by an "=" and a name. This implies rd.luks.uuid= or luks.uuid= and will additionally make the
LUKS device given by the UUID appear under the provided name.
rd.luks.name= is honored only by initial RAM disk (initrd) while luks.name= is honored by both the main system and the initrd.
luks.options=, rd.luks.options=
Takes a LUKS super block UUID followed by an "=" and a string of options separated by commas as argument. This will override the
options for the given UUID.
If only a list of options, without an UUID, is specified, they apply to any UUIDs not specified elsewhere, and without an entry in
/etc/crypttab.
rd.luks.options= is honored only by initial RAM disk (initrd) while luks.options= is honored by both the main system and the initrd.
luks.key=, rd.luks.key=
Takes a password file name as argument or a LUKS super block UUID followed by a "=" and a password file name.
For those entries specified with rd.luks.uuid= or luks.uuid=, the password file will be set to the one specified by rd.luks.key= or
luks.key= of the corresponding UUID, or the password file that was specified without a UUID.
rd.luks.key= is honored only by initial RAM disk (initrd) while luks.key= is honored by both the main system and the initrd.
SEE ALSO systemd(1), crypttab(5), systemd-cryptsetup@.service(8), cryptsetup(8), systemd-fstab-generator(8)systemd 237SYSTEMD-CRYPTSETUP-GENERATOR(8)