1

Systemd Shutdown not finishing

view story
linux-howto

https://bbs.archlinux.org – Thank you very much for your answer I decided to keep dmraid because was the software used by the latest live Ubuntu distro and it could read, mount, umount the Raid normally and shutdown gracefully. I know mdadm can do the same, but something does not work. I can mount the volume from Nautilus (btw, I am using Gnome 3) but I can't umount it (device busy) so the shutdown process still does not finish. Here is the output of lsblk, focused on the RAID drives:sdc 8:32 0 298.1G 0 disk └─sdc1 8:33 0 298.1G 0 disk sdd 8:48 0 298.1G 0 disk └─sdd1 8:49 0 298.1 (HowTos)

Danial's picture
Submitted by Danial on 10/13/2012

Stories similar to Systemd Shutdown not finishing

Hey everyone, I've been hacking at this on and off for a couple days and am clearly in a little over my head. :(

I set up a raid 5 with 3 disks a few years ago and have had no problems until we had a power outage last week. I rebooted and md0 wouldn't come online. I didn't save the error message, but it said the superblock was bad. I did some research and decided to force assembly.

Hello,

I get some errors on Quantal shutdown, killing all process failed then /var is still busy and umount failed. So on startup /var isn't clean. I couldn't find in logs more information, rsyslogd seems stopped before this error occured.

Thank you.

Trying to set up a RAID 1 year 10 weeks ago

I'm trying to create a Raid array and these are the errors I keep getting.

disk showing busy 33 weeks 2 days ago

Want to create LV Group but when i unmount /dev/sda5 this showing

[root@xen01 ~]# umount /dev/sda5 umount: /: device is busy umount: /: device is busy

This means disk /dev/sda5 is busy and due to this i can't create phsical,logical volume on this disk.

[root@xen01 ~]# pvcreate /dev/sda5 Can't open /dev/sda5 exclusively.

Recover mdadm RAID5 3 years 15 weeks ago

Tried to look for similar cases but can't find anything similar.

I had a system with 4 disks: OS debian: - /dev/sda

RAID: - /dev/sdb - /dev/sdc - /dev/sdd

The old system disk crashed, so I installed a new one and retried to resync the array. It took two hours to resync the RAID, but I'm unable to mount it.

I want to set up software RAID-1 on my Ubuntu system, and found this example of an /etc/raidtab:

raiddev /dev/md0 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 persistent-superblock 1 device /dev/sdb1 raid-disk 0 device /dev/sdc1 raid-disk 1

I would however like the path to the raid device to be /raid.

I have a Linux mdadm RAID 10 array comprising of 6 (SATA) disks configured with n2 copies.

While pulling out one disk, another one in another mirror pair failed.

Hi all,

I'm working on a project to spin-down all of my hard drives (except the boot disk) when they aren't accessed. I'm running a fresh install of 9.10 and I have the following set of drives:

/dev/sda1 -- boot /dev/sdb1 -- HDS 500GB member of md0 raid 0 /dev/sdc1 -- SEA 500GB member of md0 raid 0

I have a 5-disk Intel RAID 5 along with a 6th boot disk with /, /boot, and swap.

What I was planning to do was mount the Intel RAID partitions (which I've added with fdisk) so that the 6th disk /home, /var, /srv, etc. link to the RAID on the other 5 disks.