Re: Recover deleted files on LVM volume
On 2019-03-18 00:58, Ben Finney wrote: Howdy all, How can I recover files deleted on a ext4 volume, in a logical (LVM) volume? I've never done that but seen people have copied the disk then looked through it for anything looks like the deleted files. Think the important thing whatever you use is not to use the disk until you've sorted it so you don't overwrite the "deleted" files. good luck mick -- Key ID4BFEBB31
Re: Recover deleted files on LVM volume
Hi. On Mon, Mar 18, 2019 at 11:58:36AM +1100, Ben Finney wrote: > Howdy all, > > How can I recover files deleted on a ext4 volume, in a logical (LVM) > volume? Snapshot a volume. Run "photorec" on a shapshot. > In the past I have successfully used ‘testdisk’ to discover and recover > deleted files. However when I try now, the tool apparently gets confused > that there's no partition table. Because there is not any. But you don't need "testdisk", you need "photorec". Reco
Recover deleted files on LVM volume
Howdy all, How can I recover files deleted on a ext4 volume, in a logical (LVM) volume? I accidentally deleted a tree of directories and files, after completing a move of those files from elsewhere :-( In the past I have successfully used ‘testdisk’ to discover and recover deleted files. However when I try now, the tool apparently gets confused that there's no partition table. The “Advanced” menu item normally leads to a filesystem browser of deleted files. On this (still quite happily working) LVM volume though, ‘testdisk’ complains that it can't find any partitions. Should I be using ‘testdisk’ in a different way because this is an LVM logical volume? Should I be using some other tool to recover a tree of deleted files? -- \“The right to search for truth implies also a duty; one must | `\ not conceal any part of what one has recognized to be true.” | _o__) —Albert Einstein | Ben Finney
Crowdfunding para DebConf19
Olá, Lançamos a nossa campanha de financiamento coletivo para a DebConf19 - Conferência Mundial de Desenvolvedores(as) do Projeto Debian, que acontecerá de 21 a 28 de julho na UTFPR em Curitiba. Você pode contribuir com qualquer valor acima de R$ 10,00. https://www.catarse.me/debconf19 Ajuda lá! Tem recompensas legais :-) Abraços, -- Paulo Henrique de Lima Santana (phls) Curitiba - Brasil Debian Developer Diretor do Instituto para Conservação de Tecnologias Livres Membro da Comunidade Curitiba Livre Site: http://www.phls.com.br GNU/Linux user: 228719 GPG ID: 0443C450 Organizador da DebConf19 - Conferência Mundial de Desenvolvedores(as) Debian Curitiba - 21 a 28 de julho de 2019 http://debconf19.debconf.org signature.asc Description: OpenPGP digital signature
Re: Fstab Questions (Final time)
Hi, I would like to offer you a general tip for future queries. On Sun, 17 Mar 2019 at 22:44, Stephen P. Molnar wrote: > > Here is my current drive structure: > [...] > > Here are the the results of blkid: > [...] > > Here is the curerent fstab (missing exteraneous comment statements): > [...] >From the perspective of someone reading your message in order to possibly assist you, this style of presenting information is unsettling, because often the output of a command can be different depending on the details of the command used. There's no need to write "here are the results of", just copy and paste both the entire command and its output. For examples: # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 931.5G 0 disk # cat /etc/fstab LABEL=FOO/ext4errors=remount-ro0 1 Or cat /etc/fstab | grep -v '^#' if you want to strip comments. That style is both more concise, and more informative to the reader.
Re: Recuperar contraseña root en LVM
> Estas cagado Dario ... si te lo digo es porque funciona y ya lo he hecho. > Revisa la documentacion del shadow, la estructura y listo. Si tienes > preocupaciones respaldo el fulano archivo original. Jaja bueno si cagado significa temor a borrar datos o similar sí, estoy cagado de hacerlo en esa máquina. Sin embargo acabo de probar con la live de Slackware de 64 bits, modifiqué la password de root de uno de los dos sistemas operativos que tengo en la notebook y funcionó perfecto, hay que tener presente que debe ser la live de 64 bits ya que el Huayra que tengo instalado es de 64, probé con otra live de 32 y dio error al ejecutar chroot. Los pasos fueron bastante simples: crear un directorio para montar la partición correspondiente/montar la partición allí/chroot /mnt/directorio_montado passwd root y reescribir exit umount /mnt/directorio_montado Esta semana voy a ver si puedo hacerlo en aquella pc con la live cd, ya que una vez que recupere la contraseña de root, el resto de usuarios ya es recuperable. > http://enciclopedia.us.es/index.php/Navaja_de_Ockham > > "En lenguaje moderno significa que no se deben multiplicar las causas, es > decir las hipótesis en un razonamiento: Un raciocinio basado en premisas > menos numerosas y más sencillas es más verosímil. Cuanto menos se supone, > mejor." > > El problema no es cambiar el passwd sino hacerlo con efectividad: menos > tiempo menos pasos. Exacto, creo que de esta manera fue muy eficiente, igualmente le voy a dar otra oportunidad a la modificación de grub en otra notebook de prueba.
Printer pull half of a second blank page after the first printed page and stops
Hi, I am having problems with my HP Laserjet 1020 printer installed in Debian 9 "Stretch". I installed the drivers from: http://foo2zjs.rkkda.com/ ||bash$ | wget |-O | /|foo2zjs.tar.gz http://foo2zjs.rkkda.com/foo2zjs.tar.gz|/| ||bash$ | tar |-xzvf | /|foo2zjs.tar.gz |/| ||bash$ | cd /|foo2zjs |/| ||bash$ | make | ||bash$ | ./getweb 1020 | and ||bash# | make /|install |/| ||bash# | make /|install-hotplug |/| ... It worked normally for about 5 years, but suddenly started the following problem: When I print multiple pages, it prints only the first page and pulls a second blank sheet until the half of the sheet and stops. To remove the sheet I need to turn off, remove the toner cartridge and pull the sheet. Any tip about what may be the cause of this problem? Thanks, Markos
Re: mouse-wheel on a laptop?
For starters, have you tried using the mouse on a different computer? Certainly it is possible that the mouse wheel itself is not functioning. I assume that you are trying to use the mouse in a graphical (X) session? >From a terminal window, try running the "xev" command, available in the "x11-utils" package (which is probably already installed). This will popup a nondescript window with a black square. Hover the cursor over the window and then try to scroll up and down with the mouse wheel. Do lines appear in the terminal window? They should indicate ButtonPress and ButtonRelease events for button 4 (up) or button 5 (down). There are plenty of other things which might be wrong, but start with these two. On Wed, Mar 6, 2019, at 11:19, Sharon Kimble wrote: > > I have an Entroware notebook computer, model W950PU, which when it > boots shows it as a 'style-note', and I can disable the touch pad when > I use a USB mouse. > > But I can't get the mouse-wheel working! > > So how can I get full functions with the mouse please on this laptop? > > Thanks > Sharon. > -- > A taste of linux = http://www.sharons.org.uk > TGmeds = http://www.tgmeds.org.uk > DrugFacts = https://www.drugfacts.org.uk > Debian 9.8, fluxbox 1.3.7, emacs 26.1.92, org 9.2.1 > > Attachments: > * signature.asc
Re: Format an MS-DOS floppy on /dev/sdc
On Sun 17 Mar 2019 at 13:19:29 (+0100), Anders Andersson wrote:
> I got myself a USB 3.5" disk drive and want to format a 3.5" HD disk
> so that it Just Works™ as a standard MS-DOS floppy.
I'm not sure that you really can. What's your reasoning for
doing this? Are you just spoiling for an unnecessary fight?
Or do you really want to boot off it?
> Normally I would have used mformat from the mtools package, but it
> appears that I can not supply a device name, just "emulated names"
> like A: which are then translated to /dev/fd0 etc.
It's a long time ago, but I seem to remember they did a good job.
> The problem is that my disk drive shows up as a SCSI device on
> /dev/sdc and I can not find a way to tell mformat to use it, so it
> seems that I have to use the traditional mkfs.fat to format my disk.
> However, there are dozens of parameters such as number of FATs, FAT
> size, "media type", and I don't know anything about that! Can someone
> figure out what type of magic I need to supply to mkfs.fat for it to
> do exactly what mformat would to do a floppy, or alternatively, how to
> make mformat work with /dev/sdc?
Here's an example dialogue for formatting a FAT disk. Try it,
see if it meets the unwritten criteria that apply to your
instance and if it does, stick with it. If not, just try again
with any mtools advice you get. (FAT format will stick around.
Who knows about mtools?)
# You should always blank the start of FAT partitions/disks
# dd bs=512 of=/dev/sdz if=/dev/zero count=2048
2048+0 records in
2048+0 records out
1048576 bytes (1.0 MB) copied, 0. s, 3.1 MB/s
#
##
# This step is optional. Floppies are unpartitioned.
# Hard drives almost never are. This may or may not matter to you.
# fdisk /dev/sdz
Welcome to fdisk (util-linux 2.29.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0xa7c66574.
Command (m for help): p
Disk /dev/sdz: 3.8 GiB, 4089446400 bytes, 7987200 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
Disklabel type: dos
Disk identifier: 0xa7c66574
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p):
Using default response p.
Partition number (1-4, default 1):
First sector (2048-7987199, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-7987199, default 7987199):
Created a new partition 1 of type 'Linux' and of size 3.8 GiB.
Command (m for help): t
Selected partition 1
Partition type (type L to list all types): c
Changed type of partition 'Linux' to 'W95 FAT32 (LBA)'.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
#
##
# If you skipped the previous step, skip this to the next.
# This is for a PARTITIONED device.
# mkdosfs -v -i 20140440 -F 32 -n columbine4g /dev/sdz1
mkfs.fat 4.1 (2017-01-24)
mkfs.fat: warning - lowercase labels might not work properly with DOS
or Windows
/dev/sdz1 has 126 heads and 62 sectors per track,
hidden sectors 0x0800;
logical sector size is 512,
using 0xf8 media descriptor, with 7985152 sectors;
drive number 0x80;
filesystem has 2 32-bit FATs and 8 sectors per cluster.
FAT size is 7784 sectors, and provides 996194 clusters.
There are 32 reserved sectors.
Volume ID is 20140440, volume label columbine4g.
#
##
# For completeness, here's an up-to-date dialogue for
# an UNPARTITIONED device. This is a stick. As you
# have a disk, you might need to add -I if you
# *really* want it unpartitioned.
# mkdosfs -v -i 20140440 -F 32 -n COLUMBINE4G /dev/sdz
mkfs.fat 4.1 (2017-01-24)
attribute "partition" not found
/dev/sdz has 126 heads and 62 sectors per track,
hidden sectors 0x;
logical sector size is 512,
using 0xf8 media descriptor, with 7987200 sectors;
drive number 0x80;
filesystem has 2 32-bit FATs and 8 sectors per cluster.
FAT size is 7792 sectors, and provides 996448 clusters.
There are 32 reserved sectors.
Volume ID is 20140440, volume label COLUMBINE4G.
#
I don't have 26 devices, but sdz prevents casual cut-and-paste.
I use the approximate acquisition date for the VSN≡UUID (8 hex
digits) and, against recommendations, I use lowercase LABELs,
like columbine4g, and utf8 filenames. For those who care,
the labels are whatever the companies wrote on them, plus the
size, but cut to 11 chars.
Cheers,
David.
Re: Format an MS-DOS floppy on /dev/sdc
Curt wrote: > On 2019-03-17, Anders Andersson wrote: > > I got myself a USB 3.5" disk drive and want to format a 3.5" HD disk > > so that it Just Works™ as a standard MS-DOS floppy. > > Normally I would have used mformat from the mtools package, but it > > appears that I can not supply a device name, just "emulated names" > > like A: which are then translated to /dev/fd0 etc. > > It seems you're supposed to use '/etc/mtools.conf' for this kind of > thing. > > drive m: file="/dev/sdc" > > Then: > > mformat m: > > This from a very cursory examination of the problem on the internets. Also doable: mkfs.vfat /dev/sdc -dsr-
Re: systemd: how to start a service (kea DHCP4) after all network interfaces are up?
Sven Joachim, 16.3.2019 21:11 +0100: > On 2019-03-16 19:20 +0100, Markus Schönhaber wrote: > >> John Doe, 16.3.2019 14:18 +0100: >> >>> If your interface is configured by 'systemd', you could try: >>> >>> $ systemctl enable systemd-networkd-wait-online >> >> Thanks, but no, my network configuration is done through >> /etc/network/interfaces. Therefore this won't help. > > Try "systemctl enable ifupdown-wait-online.service" then. > See bug #912112[1]. Thanks for the info! But alas, since I'm on stretch, it isn't that easy, since the ifupdown package there provides neither the ifupdown-wait-online.service file nor the wait-online.sh script. I've downloaded the .deb for buster and tried to extract the relevant files from there and install them on my system, but I didn't manage to get that working in a way that the DHCP server was kept from starting too early. Due to the lack of time I'll refrain from trying to find out what I may have done wrong. And since there seems to be no out-of-the-box solution for this problem on stretch anyway, I'll stick to my ugly workaround for now and hope this will be sorted out in buster. That said, thanks again for pointing me in the right direction! -- Regards mks
Re: Recuperar contraseña root en LVM
> No haz probado con el live cd de ¿adueñarte de la partición? montas la > que tenga la raiz del sistema o las /usr /bin o /sbin una vez montada te > adueñas de ella con chroot y luego ejecutas "passwd" o "passwd usuario" > debería de darte para cambiar clave si hacer nada por el gestor de arranque > recuerdo que un servidor lo tenían con lilo y no lograba entrar y use una > versión de livecd llamada knoppix luego cuando knoppix fue descontinuada en > español yo contruí mis propios livecd o liveusb de debian adaptados a lo que > necesito. Voy a probar con esto que me dices, buscando un poco encontré que hay que tener cuidado con que la live-cd sea del mismo tipo que la de la distro instalada, es decir de 32 o 64 ambas. La live que usé fue tails desde un pendrive, aunque tengo la versión para 32. Voy a probar ahora en mi máquina, en una distro que es de 64 (aunque la pc es de 32) booteando con la live-cd de 64, siguiendo los pasos de: http://eithel-inside.blogspot.com/2015/10/restablecer-contrasena-olvidada.html Respecto a clonaciones o editar el shadow, no me quiero arriesgar mucho con eso, hay información importante que se baja a la pc diariamente. De todas maneras lo máximo que puede pasar es que no acepte la nueva contraseña de root, si utilizo chroot.
Re: Recuperar contraseña root en LVM
Por su puesto, antes arrancando con el cd live o flash drive. El dom., 17 mar. 2019 a las 11:38, remgasis remgasis () escribió: > Hola Dario. > > Entiendo que tratas de cambiar la contrasenia ... Tratar de cambiarla e > intentarlo via grub a veces no funciona como ya has comentado. Asi que > piensa mejor tus alternativas ... > > Como sabes, hay un archivo llamado /etc/shadow donde se almacenan las > contrasenias, si es que la gestion de las mismas no esta ya centralizado > con nis o ldap. En caso que este centralizado, o quieras ver si lo esta > porque no hay nada en el history, documentate sobre los archivos clientes > de uso, sino: > > edita shadow y desde la linea del usuario que comienza con dos puntos y > termina tambien con dos puntos coloca un hash de otro shadow que sepas la > contrasenia. > > Eso es todo. Fin del juego. > >
Re: Recuperar contraseña root en LVM
Hola Dario. Entiendo que tratas de cambiar la contrasenia ... Tratar de cambiarla e intentarlo via grub a veces no funciona como ya has comentado. Asi que piensa mejor tus alternativas ... Como sabes, hay un archivo llamado /etc/shadow donde se almacenan las contrasenias, si es que la gestion de las mismas no esta ya centralizado con nis o ldap. En caso que este centralizado, o quieras ver si lo esta porque no hay nada en el history, documentate sobre los archivos clientes de uso, sino: edita shadow y desde la linea del usuario que comienza con dos puntos y termina tambien con dos puntos coloca un hash de otro shadow que sepas la contrasenia. Eso es todo. Fin del juego.
Re: Recuperar contraseña root en LVM
Si dispones de otro disco de mismas características podrías clonarlo para hacer un test El dom., 17 mar. 2019 15:42, Darío escribió: > Gracias! > Sí también pienso que no debiera afectarle en nada, pero estuve probando > el truco en otra máquina que tiene dos distribuciones instaladas: una es > Huayra (basada en Debian) y Debian 8, bootea con el GRUB de Huayra e inicia > Debian 8, probé haciendo esos trucos para iniciar Huayra y recuperar la > contraseña o más bien reescribirla, pero jamás me aparece la consola para > seguir los pasos. En más, no me graba (con F10 o crtl+x) las modificaciones > que le hice al GRUB, tuve que hacerlo dentro del archivo > /boot/grub/grub.cfg, aún así no puedo acceder a la consola para resetear la > contraseña. > No sé si tendrá que ver con esa versión (quizás modificada) del GRUB ya > que no es la tradicional que viene en Debian 8. > >
Re: User rw Permissions on New Hard Drive
On Sat 16 Mar 2019 at 10:49:19 (+0100), Pascal Hambourg wrote: > Le 11/03/2019 à 19:46, David Wright a écrit : > > On Sat 09 Mar 2019 at 20:31:36 (+0100), Pascal Hambourg wrote: > > > > > > I did not mean using UDF on opticals discs but on regular drives, just > > > as any other general purpose filesystem. I once considered using it > > > for file sharing between Windows and Linux instead of the usual FAT > > > and NTFS. Indeed UDF is natively supported as a read-write filesystem > > > by both Linux and Windows, natively supports POSIX permissions and > > > does not suffer from FAT file size limitations. And I was surprised to > > > discover that the label set by Windows was not the label read by Linux > > > and vice versa. > > > > Without reading a review of how it performs, I'd worry about using it > > as a general purpose filesystem. It sounds as if it's designed mainly > > for handling specific issues raised by particular devices. > > No, the "U" stands for "Universal" and its is designed for a broad > range of media, including hard disks. It just has special features for > optical media, but is not restricted to them. > > The format.exe utility in Windows has an option to format a drive or > partition with UDF, so this is really not an oddity. > > > I might be > > happier if it were integrated into the kernel rather than just a > > user application. > > What do you mean ? The UDF driver is integrated in the kernel (unlike > NTFS which requires a FUSE driver to enable full-featured writes). Not > to be confused with CD/DVD authoring software which have a different > purpose. You're right: I hadn't appreciated that the udf module only gets loaded when you mount a UDF filesystem. It doesn't appear to be needed for reading the LABEL/UUID when a device is connected, so it remains absent from /proc/filesystems for example. But I *was* briefly caught out by the necessity of blanking the first MB of the device/partition before running mkudffs, which didn't help matters. (Reminds me of fighting with DOS over partition information.) Having read a little and experimented a little, I think I'll leave this format alone at least for a while. For USB sticks (and SD cards): sure, they might work with Windows and linux, but that's about it. They don't work in the car, nor in any of our TVs, nor cameras/phones. For spinning rust: I've read about erroneous 'space full' messages on large partitions, and the ongoing lack of any fsck tool. That could be a big problem with TB disks. > > > You wrote that the filesystem label was independent of any OS. > > > > No, I wrote "A filesystem that has a label, has that label regardless > > of any OS." In other words, if you hold a filesystem (on a device) in > > your hands, the label is still present, as a property of the > > filesystem, written there as a sequence of characters. > > > > This is in contrast to the string /dev/disk/by-label/LABEL which is > > effectively an artefact of the operating system, dependant on the > > device being connected to a particular type of OS, and not written > > anywhere on the device itself. > > I understand what you mean, but my point is that it does not make any > difference in practice. We know that: Cousin Stanley's disks mount successfully and so do Michael Stone's and mine. > Whatever intrinsic metadata is stored on the > device is irrelevant ; what actually matters is what metadata the > operating system uses as a label. If different operating systems use > different metadata as the label, then you cannot consider that the > label is independent of any operating systems. If an OS foo decides to use metadata bar as the "label" for a given device, then the information "bar" must appear on the device (or else "label" is being used in a metaphorical sense like in politics). All you've demonstrated in your example is that there might be more than one label, suiting different circumstances. In writing mkudffs, it appears that the authors have allowed easy avoidance of that problem by supplying an argument that sets both labels (here called identifiers) to the same string. A result is that linux (I haven't checked with Windows) will read that string as the value for LABEL. Going back to Cousin Stanley's point, the LABEL's value is bar, and I expressed the view that fstab's field 1 being set to "LABEL=bar" is more explicit than "/dev/disk/by-label/bar". If the "metadata the operating system uses as a label" bears no relation to the "intrinsic metadata is stored on the device" (for example, it might count the number of discs ever inserted into a reader, and use that number as the label), then I think the OS's designers might have difficulty justifying their decision. (If that example appears a stretch, it's because I'm having difficulty thinking of an example where a label isn't intended to be in or on something. Perhaps when it's been deliberately unpeeled or chiselled?) Cheers, David.
Re: Recuperar contraseña root en LVM
Gracias! Sí también pienso que no debiera afectarle en nada, pero estuve probando el truco en otra máquina que tiene dos distribuciones instaladas: una es Huayra (basada en Debian) y Debian 8, bootea con el GRUB de Huayra e inicia Debian 8, probé haciendo esos trucos para iniciar Huayra y recuperar la contraseña o más bien reescribirla, pero jamás me aparece la consola para seguir los pasos. En más, no me graba (con F10 o crtl+x) las modificaciones que le hice al GRUB, tuve que hacerlo dentro del archivo /boot/grub/grub.cfg, aún así no puedo acceder a la consola para resetear la contraseña. No sé si tendrá que ver con esa versión (quizás modificada) del GRUB ya que no es la tradicional que viene en Debian 8.
Recuperar contraseña root en LVM
Buenas! seguramente habrá algún hilo al respecto y he visto algunas páginas al respecto. La cuestión es que en esta máquina es un poco diferente y tengo que ir con cuidado, por eso consulto acá: la máquina en cuestión tiene cinco particiones más la swap, administrada en volúmenes lógicos: partición 1: data (100 GB) partición 2: home (150 GB) partición 3: root (21 GB) partición 4: swap (8 GB) partición 5: tmp (20 GB) partición 6: var (21 GB) las ví mediante una live-cd, son dos primarias de 70 GB y la otra de 250 GB. Esta máquina tiene un automatismo que se la pasa recolectando datos de mediciones, se corta la fuente, reinicia y sigue obteniendo datos sin necesidad de loguearse, de hecho al conectarle un monitor, se observa que está esperando loguearse en la tty1. Siempre que instalé alguna distribución linux, particioné el /home y / pero nunca utilizando volúmenes lógicos. El problema era ver qué estaba haciendo esta máquina, si funcionaba o no, efectivamente lo estaba haciendo a la perfección durante años, pero no tenemos datos de la contraseña de superusuario ni de algún otro usuario que los hay. Los pasos que hay que realizar en el grub: escribir init=/bin/bash luego de linux /boot/ luego ya en consola mount -o remount -rw / paswd root resetear la contraseña, y debería funcionar. Bien ahora la duda es si de alguna manera podrá afectar al funcionamiento que viene realizando de maravillas, ya que recuerdo que en un momento realicé este truco en otra máquina y no anduvo la recuperación. Por el momento nos conformamos con esta opción de recuperar los datos con una live-cd, ya que anda muy bien. La distro que tiene instalada es Debian 9. Saludos y gracias!
Re: Fstab Questions (Final time)
On Sun 17 Mar 2019 at 05:24:05 (-0700), Charlie Kravetz wrote: > On Sun, 17 Mar 2019 07:43:42 -0400 "Stephen P. Molnar" > wrote: > > >At least I hope it's the final time. > > > > > >I know that I have posted this question before, but due to reinstalling > >the OS, I have a clean slate at this point. Now, I've done quite a bit > >of goggling and utubing and I want to be sure that I'm not going to > >crash the system when I add two drives to the fstab. > > > >Here is my current drive structure: > > > > > >NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > >sda 8:0 0 465.8G 0 disk > >├─sda1 8:1 0 457.9G 0 part / > >├─sda2 8:2 0 1K 0 part > >└─sda5 8:5 0 7.9G 0 part [SWAP] > >sdb 8:16 0 1.8T 0 disk > >├─sdb1 8:17 0 1.8T 0 part > >├─sdb2 8:18 0 1K 0 part > >└─sdb5 8:21 0 7.9G 0 part > >sdc 8:32 0 465.8G 0 disk > >└─sdc1 8:33 0 465.8G 0 part > >sr0 11:0 1 1024M 0 rom > > > >sdc is a new SSD and I formatted it with only one partition. sdb still > >has a previous OS that I intend removing. > > > >Here are the the results of blkid: > > > >/dev/sda1: UUID="71f1ed49-9178-4bbc-b872-510f7982e245" TYPE="ext4" > >PARTUUID="1435f170-01" > >/dev/sda5: UUID="4b041dec-d00f-4acf-a731-f6a34d885105" TYPE="swap" > >PARTUUID="1435f170-05" > >/dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" > >PARTUUID="eb2be395-01" > >/dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" > >PARTUUID="0bc7db76-01" > >/dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" > >PARTUUID="0bc7db76-05" > > > >Here is the curerent fstab (missing exteraneous comment statements): > > > ># > ># / was on /dev/sda1 during installation > >UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 > ># swap was on /dev/sda5 during installation > >UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 > >/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 > > > >Finally, here is what I am proposing adding to the fstab: > > > >UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 > >UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 > > > >Note: I have added /sdb1 and /sdc1. > > > >The only questions at this point are: > >1. Will these changes crash the system,and > >2. Will I be able to read adn write to the added drives? > > I am no expert, and they can correct me if I am wrong. Should "users" > be singular, as in "user"? That depends on the m.o. If Ethel mounts the disk each morning and Ethan expects to unmount it in the afternoon, then "user" will thwart him. But in any case I can't see the point of having either, unless accompanied by "noauto", because the OS will already have done the deed. (I can see why the possibility is offered; just not a corresponding scenario.) The OP appears very timid about making this change, hence my recommendation for the inclusion of "nofail" on any partition that's not essential for the system to just run successfully. Once there is confidence that the mounts are working ok, then the nofail items could be removed, so that a successful boot shows the system is ready to perform all its tasks (rather than just being in a running state). But I think I've editorialized too much already, so I'll leave it there. (I'm no expert.) Cheers, David.
Re: Fstab Questions (Final time)
On Sun, 17 Mar 2019 07:43:42 -0400 "Stephen P. Molnar" wrote: >At least I hope it's the final time. > > >I know that I have posted this question before, but due to reinstalling >the OS, I have a clean slate at this point. Now, I've done quite a bit >of goggling and utubing and I want to be sure that I'm not going to >crash the system when I add two drives to the fstab. > >Here is my current drive structure: > > >NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >sda 8:0 0 465.8G 0 disk >├─sda1 8:1 0 457.9G 0 part / >├─sda2 8:2 0 1K 0 part >└─sda5 8:5 0 7.9G 0 part [SWAP] >sdb 8:16 0 1.8T 0 disk >├─sdb1 8:17 0 1.8T 0 part >├─sdb2 8:18 0 1K 0 part >└─sdb5 8:21 0 7.9G 0 part >sdc 8:32 0 465.8G 0 disk >└─sdc1 8:33 0 465.8G 0 part >sr0 11:0 1 1024M 0 rom > >sdc is a new SSD and I formatted it with only one partition. sdb still >has a previous OS that I intend removing. > >Here are the the results of blkid: > >/dev/sda1: UUID="71f1ed49-9178-4bbc-b872-510f7982e245" TYPE="ext4" >PARTUUID="1435f170-01" >/dev/sda5: UUID="4b041dec-d00f-4acf-a731-f6a34d885105" TYPE="swap" >PARTUUID="1435f170-05" >/dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" >PARTUUID="eb2be395-01" >/dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" >PARTUUID="0bc7db76-01" >/dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" >PARTUUID="0bc7db76-05" > >Here is the curerent fstab (missing exteraneous comment statements): > ># ># / was on /dev/sda1 during installation >UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 ># swap was on /dev/sda5 during installation >UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 >/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 > >Finally, here is what I am proposing adding to the fstab: > >UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 >UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 > >Note: I have added /sdb1 and /sdc1. > >The only questions at this point are: >1. Will these changes crash the system,and >2. Will I be able to read adn write to the added drives? > >Thanks in advance. > I am no expert, and they can correct me if I am wrong. Should "users" be singular, as in "user"? -- Charlie Kravetz Linux Registered User Number 425914 [http://linuxcounter.net/user/425914.html] Never let anyone steal your DREAM. [http://keepingdreams.com]
Re: Format an MS-DOS floppy on /dev/sdc
On 2019-03-17, Anders Andersson wrote: > I got myself a USB 3.5" disk drive and want to format a 3.5" HD disk > so that it Just Works™ as a standard MS-DOS floppy. > Normally I would have used mformat from the mtools package, but it > appears that I can not supply a device name, just "emulated names" > like A: which are then translated to /dev/fd0 etc. It seems you're supposed to use '/etc/mtools.conf' for this kind of thing. drive m: file="/dev/sdc" Then: mformat m: This from a very cursory examination of the problem on the internets. > The problem is that my disk drive shows up as a SCSI device on > /dev/sdc and I can not find a way to tell mformat to use it, so it > seems that I have to use the traditional mkfs.fat to format my disk. > However, there are dozens of parameters such as number of FATs, FAT > size, "media type", and I don't know anything about that! Can someone > figure out what type of magic I need to supply to mkfs.fat for it to > do exactly what mformat would to do a floppy, or alternatively, how to > make mformat work with /dev/sdc? > > -- “Let us again pretend that life is a solid substance, shaped like a globe, which we turn about in our fingers. Let us pretend that we can make out a plain and logical story, so that when one matter is despatched--love for instance-- we go on, in an orderly manner, to the next.” - Virginia Woolf, The Waves
Re: Fstab Questions (Final time)
On 3/17/2019 12:43 PM, Stephen P. Molnar wrote: > At least I hope it's the final time. > > > I know that I have posted this question before, but due to reinstalling > the OS, I have a clean slate at this point. Now, I've done quite a bit > of goggling and utubing and I want to be sure that I'm not going to > crash the system when I add two drives to the fstab. > > Here is my current drive structure: > > > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:0 0 465.8G 0 disk > ├─sda1 8:1 0 457.9G 0 part / > ├─sda2 8:2 0 1K 0 part > └─sda5 8:5 0 7.9G 0 part [SWAP] > sdb 8:16 0 1.8T 0 disk > ├─sdb1 8:17 0 1.8T 0 part > ├─sdb2 8:18 0 1K 0 part > └─sdb5 8:21 0 7.9G 0 part > sdc 8:32 0 465.8G 0 disk > └─sdc1 8:33 0 465.8G 0 part > sr0 11:0 1 1024M 0 rom > > sdc is a new SSD and I formatted it with only one partition. sdb still > has a previous OS that I intend removing. > > Here are the the results of blkid: > > /dev/sda1: UUID="71f1ed49-9178-4bbc-b872-510f7982e245" TYPE="ext4" > PARTUUID="1435f170-01" > /dev/sda5: UUID="4b041dec-d00f-4acf-a731-f6a34d885105" TYPE="swap" > PARTUUID="1435f170-05" > /dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" > PARTUUID="eb2be395-01" > /dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" > PARTUUID="0bc7db76-01" > /dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" > PARTUUID="0bc7db76-05" > > Here is the curerent fstab (missing exteraneous comment statements): > > # > # / was on /dev/sda1 during installation > UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 > # swap was on /dev/sda5 during installation > UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 > /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 > > Finally, here is what I am proposing adding to the fstab: > > UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 > UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 > > Note: I have added /sdb1 and /sdc1. > > The only questions at this point are: > 1. Will these changes crash the system,and Before rebooting the system try 'mount -a' and fix any error before rebooting. If 'mount -a' does not conplain, you should be fine; if an error were to happened, you can always recover. Also, keep an unmodified copy of your fstab file before modifying it. > 2. Will I be able to read adn write to the added drives? > Looks like it, trying your changes will be the only way to tell. P.S. If you are that afraid of messing around, having a test environment is clearly needed. -- John Doe
Format an MS-DOS floppy on /dev/sdc
I got myself a USB 3.5" disk drive and want to format a 3.5" HD disk so that it Just Works™ as a standard MS-DOS floppy. Normally I would have used mformat from the mtools package, but it appears that I can not supply a device name, just "emulated names" like A: which are then translated to /dev/fd0 etc. The problem is that my disk drive shows up as a SCSI device on /dev/sdc and I can not find a way to tell mformat to use it, so it seems that I have to use the traditional mkfs.fat to format my disk. However, there are dozens of parameters such as number of FATs, FAT size, "media type", and I don't know anything about that! Can someone figure out what type of magic I need to supply to mkfs.fat for it to do exactly what mformat would to do a floppy, or alternatively, how to make mformat work with /dev/sdc?
Re: GIMP Crash
Le 17/03/2019 à 01:27, Adam Haas a écrit : > I was working with the Gnu Image Manipulation Program yesterday when a > segmentation fault occurred. Attached is the information spit out in > association with the event. Please let me know what additional > information you need from me and I will pass it along. > > - Adam Haas Hello, Can you send the content of your /etc/apt/sources.list ? Thanks.
Fstab Questions (Final time)
At least I hope it's the final time. I know that I have posted this question before, but due to reinstalling the OS, I have a clean slate at this point. Now, I've done quite a bit of goggling and utubing and I want to be sure that I'm not going to crash the system when I add two drives to the fstab. Here is my current drive structure: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 457.9G 0 part / ├─sda2 8:2 0 1K 0 part └─sda5 8:5 0 7.9G 0 part [SWAP] sdb 8:16 0 1.8T 0 disk ├─sdb1 8:17 0 1.8T 0 part ├─sdb2 8:18 0 1K 0 part └─sdb5 8:21 0 7.9G 0 part sdc 8:32 0 465.8G 0 disk └─sdc1 8:33 0 465.8G 0 part sr0 11:0 1 1024M 0 rom sdc is a new SSD and I formatted it with only one partition. sdb still has a previous OS that I intend removing. Here are the the results of blkid: /dev/sda1: UUID="71f1ed49-9178-4bbc-b872-510f7982e245" TYPE="ext4" PARTUUID="1435f170-01" /dev/sda5: UUID="4b041dec-d00f-4acf-a731-f6a34d885105" TYPE="swap" PARTUUID="1435f170-05" /dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" PARTUUID="eb2be395-01" /dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" PARTUUID="0bc7db76-01" /dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" PARTUUID="0bc7db76-05" Here is the curerent fstab (missing exteraneous comment statements): # # / was on /dev/sda1 during installation UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 Finally, here is what I am proposing adding to the fstab: UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 Note: I have added /sdb1 and /sdc1. The only questions at this point are: 1. Will these changes crash the system,and 2. Will I be able to read adn write to the added drives? Thanks in advance. -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1
