I am running Debian GNU/Linux (Bookworm) and by using the gnome-disk-utility 45.1 (UDisks 2.10.1) I like to put a spinning disk immediately to stand-by (via GUI). Doing so I'm being prompted for a password. — BTW: I'm not looking for a command line way for doing this. Nevertheless, I am wondering why it is possible to format a disk (a.k.a. initializing a disk with new MBR or GUID partition scheme) without providing a password?! This can lead to accidental data loss, IMHO. I am asking this question because I'd like to put my disks into stand-by without being prompted for a password. How could I possibly achieve that? BTW: My non-root user is member of the following groups: redacteduser adm cdrom floppy sudo audio dip video plugdev users netdev bluetooth lpadmin scanner systemd-journal

I want to resize an LVM partition (specifically, I want to increase the root / mount and decrease the /home), because I am running low on disk space on one virtual partition.  Now people say LVM has resizeable partitions… they claim, at least.  I did not see it so far… 😉 How can I do so? ### Blivet GUI I tried to use blivet GUI from a Fedora Workstation installation disk. So I: 1. boot that media 2. start blivet-gui (after installing it, if needed) 3. go to the LVM section and find the virtual partitions there. However, when I right-click and go to "Edit", the menu entries are all greyed-out. Fedora 31 ### Other tries Alternatively, is there any other GUI that can edit the size of the inner LVM partitions? I've tried gnome-disks, GParted and blivet.  GParted does only recognize the disks and GNOME disks does not help either. I want to avoid using the command line for this. ---- Cross-posted [at Ask Fedora](https://ask.fedoraproject.org/t/how-to-use-blivet-gui-to-resize-an-lvm-partition/6685?u=rugk) .

I used to dual boot Windows and Fedora 35, and decided to just run windows in a vm. I deleted the Windows partitions successfully, but now I have free space in the middle that I can't figure out how to move safely. Since I don't have a swap partition, this question doesn't help, and since the partitions are on the same disk, I can't use this question . I don't want to use GParted because it's not installed on my Fedora live usb (and other unrelated reasons), so my options are Gnome Disks and blivet-gui. Is there a way to safely move the free space from the middle of nowhere to my main partition? **Print lsblk** Return mountpoint for fedora_localhost-live (nvme0n1p6). $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS zram0 252:0 0 8G 0 disk [SWAP] nvme0n1 259:0 0 476.9G 0 disk ├─nvme0n1p1 259:1 0 100M 0 part /boot/efi ├─nvme0n1p5 259:2 0 1G 0 part /boot └─nvme0n1p6 259:3 0 350.9G 0 part /home / Many thanks!!

While installing ChromeOS Flex into a machine, the installation process froze and we had to stop the installation. Now, the USB is not recognized in any machine, no matter if Windows or Linux. When executing df -h, the device does not show up. However, it does show up when executing lsusb as Bus 001 Device 008: ID ffff:1201. Additionally, on Ubuntu 20.04, I've tried using GParted, but the device is not detected. However, it does appear in Disks. As you can see, I can't perform any action on the device through Disks. Is there any solution to this? How can the USB be recovered? Thanks in advance.

Gnome comes with "Disks". If you select a disk, click the three-dot button, and select "Drive Settings", it shows Standby or APM settings. But these does not seem to work. Judging by the power meter that I had attached the computer to, the disk did not seem to go sleep (spin down) even after setting the Standby to 5 minutes and APM to 127 (spin-down permitted) after a long inactivity. Then I executed hddparam -S. It made the disk sleep after a while judging by the reduced wattage on the power meter. Why doesn't Gnome Disk's sleep setting not work but only hddparam -S? Aren't they the same thing? Or am I misuse/misunderstanding Gnome Disk's settings?

I wanted to measure my SSD read/write performance and found some recommendations for using dd and gnome-disks. (from my understanding, hdpart is not relevant since it's not using the disk itself but only cached data). The problem is that I get different results with these tools and I wish to understand why it happens. The rootfs is mounted from a local internal eMMC and the SSD has a mounted ext4 filesystem. Thanks

I wanted to use btrfs on my Linux Mint PC more, but I keep encountering new issues. Now I've found out (tried on two USB sticks) that btrfs formatted USB stick can be properly unmounted/ejected via GUI (Nemo), but not from terminal. $ umount /dev/sdb1 Error finding object for block device 0:87 For other fs it works, just checked that after I insert USB stick and it is automounted, running umount in terminal works (for ext4 and ISO 9660), but not for btrfs. Why? Sticks were formatted with btrfs via Gnome-disks, maybe it matters... Added 1: Btrfs partition on local harddrive mounted via Gnome-Disks GUI produced same error on umount in terminal. I was able to successfully sudo mount and sudo umount it in terminal. Added 2: sudo umount works and does not produce the error.

I have a USB key with the following partitions: - FAT EFI 300MB - EXT4 Debian System 200GB (40GB used) - FAT 16GB - Swap 18GB (I think I should remove this partition anyway) I decided to shrink the EXT4 Debian partition from 200GB to 60GB, using gnome-disks. After a while the job seemed done but I think that something went wrong because now the partition is still 200GB and it seems that I only have 20GB of free space in that partition. If I try to boot form the USB key, the Debian system of course works fine but it confirms that the partition is still 200GB and that there are only 20GB of free space left. Giving that before the operation I had 40GB of used space, how this can be possible and how I can fix it? **EDIT**

$ lsblk /dev/sda
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    1 233,3G  0 disk 
├─sda1   8:1    1   300M  0 part 
├─sda2   8:2    1 201,2G  0 part 
├─sda3   8:3    1  16,9G  0 part 
└─sda4   8:4    1  14,9G  0 part

**EDIT 2** I resized again the partition with gnome-disks, this time restoring the original size (i ran the resize command with no resize to do at all), now the partition and the file system seems aligned **EDIT 3** Now I retried shrinking in two trances, the first by 64GB, the second 90GB, both worked and the Debian partition is now 60GB I still wandering why this happened and how to prevent/fix by command line

Does the write-benchmark of gnome-disks write back the original data after the test? It is destructive? The *Benchmark Settings* window only states this: Please back up important data before using the write benchmark. Furthermore, how does it handle mounted filesystems on the tested disk?

I recently bought an external hard drive by maxone to use with a Mac that I have. The instructions that I got with it was to connect it to a Windows PC and format it before I can use it with a Mac, but since I only have a Linux machine available I was hoping to be able to format it from Linux. I have encountered similar problems some years ago but ended up finding a Windows PC to solve it. I was surprised to not find forum posts that helped me resolve it but I searched and the few things that were similar that I found were not solved, others had minor differences than my case, maybe I just didn't understand some of them properly. ## My System Linux Mint 20.04 Toshiba Satelite laptop with the hard drive connected to the USB 3.0 connection. uname -a results: Linux 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ## The Problem + What I tried When I connect the hard drive I can see it turns on and feel it spinning. In the Linux Mint settings under "Disks" I can see a new hard drive pop up as "Maxone USB 3.0". The "Volume" section says "No Media" and appears as /dev/sdc. The the gears button has everything greyed out (including the formatting option" except for "Edit mount options" which use defaults. I can see in the terminal that /dev/sdc exists. It does not appear under in /proc/partitions though. fdisk -l does not recognize the disk at all. I tried using Gparted but it did not recognize the hard drive either. lsusb did find: Bus 004 Device 005: ID 152d:0583 JMicron Technology Corp. / JMicron USA Technology Corp. Maxone sudo lshw -c disk finds: *-disk description: SCSI Disk product: USB 3.0 vendor: Maxone physical id: 0.0.0 bus info: scsi@7:0.0.0 logical name: /dev/sdc version: 0209 serial: DD564198838A2 configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512 When I connect the hard drive I see in dmesg the following: [205381.443074] usb 4-1: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd [205381.464174] usb 4-1: New USB device found, idVendor=152d, idProduct=0583, bcdDevice= 2.09 [205381.464179] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [205381.464183] usb 4-1: Product: Maxone [205381.464186] usb 4-1: Manufacturer: Maxone [205381.464188] usb 4-1: SerialNumber: 000020200909 [205381.470699] scsi host7: uas [205381.472216] scsi 7:0:0:0: Direct-Access Maxone USB 3.0 0209 PQ: 0 ANSI: 6 [205381.473026] sd 7:0:0:0: Attached scsi generic sg3 type 0 Given all of this I could not figure out a way to format the hard drive, as I do not have a partition to format or a way to initialize the drive (that I can tell at least). ### Edit As per the comments I ran some more commands that unfortunately did not work and here are the results: sudo mkfs -t fat /dev/sdc: mkfs.fat 4.1 (2017-01-24) attribute "partition" not found mkfs.fat: unable to discover size of /dev/sdc sudo mkfs -t ext4 /dev/sdc: mke2fs 1.45.5 (07-Jan-2020) mkfs.ext4: Device size reported to be zero. Invalid partition specified, or partition table wasn't reread after running fdisk, due to a modified partition being busy and in use. You may need to reboot to re-read your partition table. sudo echo , | sudo sfdisk /dev/sdc: sfdisk: cannot open /dev/sdc: No such file or directory (this is despite /dev/sdc existing (I can see it using ls) ## Final Questions Is the only way to initialize and format a newly bought external hard drive that was intended for Windows in Windows itself? Is there no way to do this on Linux? What causes the drive to be recognized as /dev/sdc but at the same time not be registered by fdisk? Is this because of the filesystem type on it? Shouldn't fdisk be able to nuke and re-initialize a hard drive no matter what? Thank you for your time and any help you may be able to provide.

I struggled to title this so if you have a better title please edit or request a change. Trying to dual-boot windows and Ubuntu. I used mkusb to create a bootable Ubuntu disk, installed it, then went to create a bootable Windows disk in the same manner. Ran mkusb, selected dus, install, clone iso file. The process failed (I think because you're meant to use a different option for Windows isos), I don't have the error message. Now whenever I try to use mkusb I get: No suitable target device found. This also happens if I try to use the mkusb restore option. **Full mkusb terminal output:** target device is /dev/sdb.

---------------------------------------------------------------------
Usage: mkusb [input-file]      # optional parameter
---------------------------------------------------------------------
d:  dus , guidus, mkusb-dus    - Classic, easy to use
p: Plug,   mkusb-plug          - New, easy to use
n: NoX,    sudo mkusb-nox      - original text mode
b: Bas,    sudo mkusb-bas      - basic text mode for old/basic linux
e: Eleven, sudo -H mkusb-11    - Old user interface
q: Quit
---------------------------------------------------------------------
Select version of mkusb (d/p/n/b/e/q) d
 dus 12.5.7 
live system or temporary superuser permissions
clean if necessary and return
Drive that contains source file: /dev/sda
Live drive, that is booted from: /dev/sda
lsblk: /dev/sdb: not a block device
 No suitable target device found 
p_target: target=/dev/
No target device or bad target device
clean if necessary and return
clean if necessary and return
clean if necessary and quit

$: sudo fdisk -l does not list /dev/sdb. I tried using gparted to wipe the partition table and create a new one, however gparted displays the 16GB drive as ~8GB: I proceeded with formatting the available space and creating a new msdos partition table, this is the format shown in the gparted screen above. The warning associated with the partition reads: >5.52 GiB of unallocated space within the partition. To grow the filesystem to fill the partition, select the partition and choose the menu item: Partition --> Check. Running Partition --> Check results in Could not detect file system. at the terminal and fails. If I open up gnome-disks I get this information: Which looks completely different to the partition breakdown given by gparted. Note, the partition sizes were the same before I modified things in gparted, the only difference was the first partition was an Ubuntu image with a different format. Before running gparted I tried zeroing the drive with dd which stopped after ~8GB and appeared to have no effect. In short, I have no clue what's going on with the partition table on this drive. **Questions:** 1. What have I done to the partition table? 2. Can I fix it? I still need to install Windows and I would like to recover the drive afterwards. **Bonus round:** 3. I'm aware mkusb "uses the whole drive" but I know I've lost at least one drive to the same problem. What causes it to royally screw up the drives it targets? 4. Why is it so finicky to restore the partition table after using mkusb? I'd like to understand what's going on here as well as how to resolve the issue. Thank you

When I use a GUI environment, I have there only ext4, NTFS, FAT and other, but I need to type their name. I tried one time to type there ext2, but it seems it gets stuck. I was waiting a lot and it still did not format. My OS Debian, using Gnome 3.

I am running Ubuntu server 18.04 and I am using an ICY BOX IB-RD2253-U31 enclosure with two WD Black disks (no NAS disks) in RAID 1 mode (mirror). I want to put the two disks in sleep mode / spin them down with hdparm (lowest power consumption sleep mode) with sudo hdparm -Y /dev/sdb but the disks seem to run like nothing happened. I also tried sudo udisksctl power-off -b /dev/sdb: This causes the OS to eject the drives, but the disks are still running (I can hear them running). Is this the fault of the enclosure? And is there any way to spin down the disks completely until needed again?

I'm trying to create a 64GB LVM partition for my root volume. lvcreate -L 64G volume0 -n lv_root However, when I start gnome-disks the partition is listed as 69GB? Incidentially this is the same size I get using: df -H How would I create a logical volume that is 64GB in size rather than 69GB? Is this something to do with GB vs GiB or is this a quirk of LVM?

Why does the GUI tool for formatting disks have no option to format with ext2 and ext3 filesystems? Why would a tool used for formatting exclude these filesystems? What is the rationale behind this annoyance?

I'm working on Linux Mint 18.3, and I have a Seagate Backup Plus 2TB external HDD. I've had a few minor problems with the drive which I was able to fix, but I've hit a really problematic snag. Copying from my internal HDD or SSD to the Seagate drive gives normal transfers speeds (100MB/s for about 1.3 GB and then slows down to 20MB/s on my USB3 port). HOWEVER, if I try to copy from my Seagate drive to either my internal HDD or SSD, I get the very precise copying speed of 2.5MB/s. Here is the KICKER: if, while a file is copying from the Seagate drive, I go into the Disks utility and manually force a refresh of the S.M.A.R.T. data from the Seagate disk, the speed is massively boosted for about a second and a half. The Seagate is formatted as NTFS (I know...), so I thought this would work better on Windows. I tried on my Windows 7 partition, and this time, any file I would copy from Seagate to internal HDD or SSD would give the speed of around 750KB/s. So it's even slower (seems like USB 1.1 speeds) than on Linux. I have tried this experiment in different temperature conditions (I thought maybe the external drive was being hardwired to limit speed as to not overheat) as well as after having installed the Seagate Dashboard program. Does anyone know what causes this and how it can be fixed? I hate having to constantly click the "Refresh SMART data" button and I'm not too sure it's good for the health of the drive either. NB: The SMART data shows no bad or reallocated sectors. EDIT: As per frostschutz's comment, I proceeded to try copying files from the Seagate drive to my laptop's Lubuntu partition and lo and behold, I got the USB 2.0 speeds that my laptop is capable of. So I knew the problem wasn't with the external HDD. Context: My computer has a "built-in" usb hub, as in there's a few USB slots coming out from the motherboard, but there's also a few of them in the "front" of the machine, and that latter one is the hub. I never use that one, as the speeds are slower, but still I keep it plugged in. When I proceeded, in order to run the dmesg and lsusb commands, to plug back the Seagate drive into my computer, in the same 3.0 USB port that I had been getting precisely 2.5MB/s out of, I tried yet again to copy a file, just for the hell of it (the same file I've kept trying, it's a big meaty 23GB file). Lo and behold, a steady 125MB/s write speed to my internal HDD. For the whole 23GB. Besides me plugging the Seagate into another computer, absolutely nothing else changed. Something reset what the drive was reading and made it ok again. I believe this whole episode has something to do with the way in which I've experimented unplugging the Seagate drive. For some reason, when I "safely remove drive" the Seagate external HDD, it doesn't put the drive to sleep as I still hear the platter spinning and if I unplug from the USB port, it makes a sharp sound as the head is put to rest. Before settling for the unmount and then hdparm -y /dev/sdx command, which did indeed solve my problem of putting the drive to sleep before unplugging, I tried a few other stuff which I don't even remember, which somehow made the drive behave weirdly when jacked into any of my computer's USB ports. For all intents and purposes, my problem is solved, but I will provide dmesg data for anyone curious in figuring this out with me. [ 5448.682599] usb 2-5: new SuperSpeed USB device number 2 using xhci_hcd [ 5448.703297] usb 2-5: New USB device found, idVendor=0bc2, idProduct=ab24 [ 5448.703301] usb 2-5: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 5448.703304] usb 2-5: Product: BUP Slim BK [ 5448.703307] usb 2-5: Manufacturer: Seagate [ 5448.703309] usb 2-5: SerialNumber: xxxxxx (my edit) [ 5448.705875] scsi host6: uas [ 5448.706528] scsi 6:0:0:0: Direct-Access Seagate BUP Slim BK 0304 PQ: 0 ANSI: 6 [ 5448.762823] sd 6:0:0:0: Attached scsi generic sg3 type 0 [ 5448.763012] sd 6:0:0:0: [sdc] Spinning up disk... [ 5449.778572] . [ 5450.802589] . [ 5451.826604] . [ 5452.850628] . [ 5452.850898] ready [ 5452.851222] sd 6:0:0:0: [sdc] 3907029167 512-byte logical blocks: (2.00 TB/1.82 TiB) [ 5452.851226] sd 6:0:0:0: [sdc] 2048-byte physical blocks [ 5453.201932] sd 6:0:0:0: [sdc] Write Protect is off [ 5453.201936] sd 6:0:0:0: [sdc] Mode Sense: 4f 00 00 00 [ 5453.202097] sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5453.233738] sdc: sdc1 [ 5453.234888] sd 6:0:0:0: [sdc] Attached SCSI disk [ 5811.595986] usb 2-5: USB disconnect, device number 2 [ 5811.597333] sd 6:0:0:0: [sdc] Synchronizing SCSI cache [ 5811.844787] sd 6:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK The last three or so lines are after I unmounted it, I believe. lsusb -t gave this: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M |__ Port 5: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 8: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 8: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M And lsusb -v gave this (only included the seagate one): Bus 002 Device 003: ID 0bc2:ab24 Seagate RSS LLC Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x0bc2 Seagate RSS LLC idProduct 0xab24 bcdDevice 1.00 iManufacturer 2 iProduct 3 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 121 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 36mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 1 bNumEndpoints 4 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 98 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 MaxStreams 32 Data-in pipe (0x03) Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 MaxStreams 32 Data-out pipe (0x04) Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 MaxStreams 32 Status pipe (0x02) Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 0 Command pipe (0x01) Distro/kernel: Linux PC 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I have a computer I use for imaging disks running Ubuntu 16.04. Each disk is inserted into a USB 3.0 dock, imaged/wiped, and then disconnected. The disks don't have any mounted filesystems which need to be dismounted. They disappear from gnome-disks as expected. Eventually, using gparted and/or the gnome-disks, I am no longer able to see any new disks that get added. Sometimes, new disks show up under an old /dev/sdx device and I can access them but they show the old device's partition table and size. I assume this is because /dev/sdx is filling up and the kernel is holding onto pointers to disks which no longer exist? Edit: I should add that a number of these disks have bad sectors or other issues, so that could be a part of the problem as well. This "block device exhaustion" happens faster when more malfunctioning drives are added/removed. Once it happens, even good drives won't appear when added to the system. But I notice this happens even if all drives I'm adding/removing are healthy and functioning. What can I do to prevent this behaviour or tell the kernel to "forget" disconnected disks?

I have been able to backup and restore a Linux Mint system partition with 'Disks' (command to run: gnome-disks; package to install: gnome-disk-utility) from a live session, but I am not sure that was the best way to do it: on the contrary! I need advice on what I did wrong in order to have a proper procedure available next time I need it. My initial configuration was this: The backup/restoration procedure involved the /dev/sda2 partition (ext4). With the swap space (that I'll not discuss anymore in order to simplify the description), it involves about 70 GB. The rest are ntfs partitions, one a Windows system partition, the other a "Depo" partition accessible from both Windows and Linux. This is what I did: BACKUP: --- - with **gparted** in a live session shrunk the partition to the smallest size (from 70 to 30 GB) - made the backup (30 GB) with **Disks** (as an iso image that I saved on an external device) (After creating an extended partition and testing different Linux systems like Ubuntu Gnome and Solus, I wanted to go back to the initial situation, as I decided I preferred my original single Linux Mint stable and well customized system.) RESTORATION: --- - with Gparted, deleted the entire (70 GB) extended partition and created a new 70 GB ext4 primary partition - with Disks, **restored the 30 GB partition (from the iso image) onto the 70 GB one!!!! ---- maybe I should have restored it onto unformatted space?** - IS THIS THE ERROR? - at this point the entire 70 GB partition seemed almost full, although the restored image had only 30 GB; boot-repair complained about lack of space when trying to install grub on that partition and failed to install grub - and gparted reported only 600 MB free, while c 40 GB free space was somehow visible but ONLY in the *image* gparted showed, not in the numbers; RESIZING WAS NOT POSSIBLE - after **restarting in a new live session**: gparted reported only 600 MB free but resizing was possible: reducing the partition to real full space of 30 GB, **40 GB appeared unallocated all of a sudden, then extending entire partition to full 70 GB was possible** - at this point only grub was missing, and running boot-repair in live session all went fine (I selected advanced options: install grub on sda, boot from the given partition (sda2), un-checked "purge grub" as there was no grub installed anyway) After booting from local drive, the old grub list was available and the old system was in place. The only problem, it took a lot of time first time to enter session, and I also think the boot time is now generally somewhat longer.. --- So, my question is: should one restore a system partition image onto an empty partition the way I did or on an not-formatted space? or in a somehow different way?

I have made a backup of my Linux Mint Xfce partition and I have restored it (all with "Disks" - gnome-disks) twice. (More here ). The partition includes all the system (no separate partitions between /, /home/, /boot etc, just /.) After each restoration the system works fine, but the boot time is very long (2-3 minutes) compared to what it used to be (20 seconds maximum). Why is that and can I fix it? As I shut down every day I am thinking about reinstalling my system but I would prefer to avoid that, as it would be what the whole backup process was trying to avoid. --- Update: I have found a similar situation when shrinking a system partition with a similar system. The situation improved when the same partition was increased back to its initial size. Possibly the system is looking for a "familiar" size of the partition at boot-up and asks for more boot time when it encounters a smaller size...

I have a laptop with the accursed Western Digital hard drive. I have used SMART to look at Load/Unload cycles (smartctl -a|grep Load). They increase too fast towards the 300,000 lifetime limit. I use GNOME Disks to change the hard drive APM to 254, and they stop increasing. This wasn't a solution on its own: I also had to create /usr/lib/systemd/system-sleep/harddrive.sh which does systemctl restart udisks2 - to handle resume from suspend, when this drive settings is lost. But some months later, I noticed the drive was clicking again and indeed Load/Unload were increasing. What went wrong? Also I went to look in GNOME Disks. I can no longer find either SMART data, nor the drive APM setting! What happened?! I have no SELinux alerts in SELinux Troubleshooter. $ rpm -q gnome-disk-utility gnome-disk-utility-3.22.1-1.fc25.x86_64 $ rpm -q --whatprovides /usr/libexec/udisks2/udisksd storaged-2.6.2-2.fc25.x86_64 $ systemctl status udisks2 ● udisks2.service - Disk Manager Loaded: loaded (/usr/lib/systemd/system/udisks2.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2017-02-23 14:10:47 GMT; 3min 55s ago Docs: man:udisks(8) Main PID: 6416 (udisksd) Tasks: 5 (limit: 4915) CGroup: /system.slice/udisks2.service └─6416 /usr/libexec/udisks2/udisksd --no-debug Feb 23 14:10:47 alan-laptop systemd: Starting Disk Manager... Feb 23 14:10:47 alan-laptop udisksd: udisks daemon version 2.6.2 starting Feb 23 14:10:47 alan-laptop udisksd: Acquired the name org.freedesktop.UDisks2 on the system message bus Feb 23 14:10:47 alan-laptop systemd: Started Disk Manager. $ journalctl -b |grep udisks.*sda Feb 21 09:05:42 alan-laptop udisksd: Applying configuration from /etc/udisks2/WDC-WD5000LPLX-75ZNTT0-WX71A958AN1Y.conf to /dev/sda Feb 21 09:05:42 alan-laptop udisksd: Set APM level to 254 on /dev/sda [WDC-WD5000LPLX-75ZNTT0-WX71A958AN1Y] Feb 21 10:20:56 alan-laptop udisksd: Applying configuration from /etc/udisks2/WDC-WD5000LPLX-75ZNTT0-WX71A958AN1Y.conf to /dev/sda Feb 21 10:20:56 alan-laptop udisksd: Set APM level to 254 on /dev/sda [WDC-WD5000LPLX-75ZNTT0-WX71A958AN1Y] ... Feb 23 10:07:16 alan-laptop udisksd: Applying configuration from /etc/udisks2/WDC-WD5000LPLX-75ZNTT0-WX71A958AN1Y.conf to /dev/sda Feb 23 10:07:17 alan-laptop udisksd: Set APM level to 254 on /dev/sda [WDC-WD5000LPLX-75ZNTT0-WX71A958AN1Y] Feb 23 12:31:36 alan-laptop udisksd: Applying configuration from /etc/udisks2/WDC-WD5000LPLX-75ZNTT0-WX71A958AN1Y.conf to /dev/sda Feb 23 12:31:36 alan-laptop udisksd: Set APM level to 254 on /dev/sda [WDC-WD5000LPLX-75ZNTT0-WX71A958AN1Y] $ date Thu 23 Feb 14:25:05 GMT 2017 My particular workaround for the suspend problem is not effective right now. The configuration was not applied when it resumed at this time: Feb 23 13:02:55 alan-laptop systemd-sleep: System resumed. This is despite udisks being started at this time: Feb 23 13:02:55 alan-laptop udisksd: udisks daemon version 2.6.2 starting Feb 23 13:02:55 alan-laptop udisksd: Acquired the name org.freedesktop.UDisks2 on the system message bus Some version of storaged (udisks) is [supposed to be re-applying the setting on resume](https://github.com/storaged-project/udisks/issues/72) , but that doesn't seem to be the case on my system. I tried disabling my script in case it broke something, but again, after resume from suspend, hdparm -B /dev/sda shows 128.