Umont Root raid device

j5 · n00b Joined: 18 Apr 2005 Posts: 9 Location: Blumenau / SC

Hi everyone,

I had a little problem in my new Firewall server: (Software RAID-1 on /)

When i ran the shutdown process, it runs /lib/rcscripts/addon/raid-stop.sh, and then it fails with Device or Resource Busy..

I've tried to put a ps aux; lsof before the mdadm command, but i had just found kernel processes, udevd the the /sbin/rc command...

I've also killed udevd before the shutdown process but the error persists. Then i made some research and Slackware for example doesnt execute any raidtop /dev/md0 or mdadm -S /dev/md0 on the shutdown process.

How i temporary solved the problem? rm /lib/rcscripts/addon/*

. But very strange, maybe a design problem ? IMHO, that script shoudn't be in /lib... maybe some script libraries, but not a shutdown process itself.

Sorry my bad english, with best regards...

---
Giovanni F. Moser Frainer
_________________
Giovanni

R!tman · Posted: Sat Jul 09, 2005 10:55 pm Post subject:

I get the same problem:

richard.scott · Posted: Fri Jul 22, 2005 6:33 pm Post subject:

I had the same problem and also noticed I had both madam and raidtools installed.

I uninstalled mdadm and found the problem went away.

I gues its a one or the other kind of thing?

R!tman · Posted: Fri Jul 22, 2005 8:29 pm Post subject:

richard.scott · Posted: Fri Jul 22, 2005 9:34 pm Post subject:

Have a look at this bug report https://bugs.gentoo.org/show_bug.cgi?id=83821

they suggest that both mdadm and raidtools should not be installed together.

R!tman · Posted: Sat Jul 23, 2005 6:58 am Post subject:

richard.scott · Posted: Sat Jul 23, 2005 10:45 am Post subject:

You could try unmerging both packages (if any are still installed) and re-emerging mdadm and see if that updates the portage database of who own's what.

My problem seems to be because the root partition has not bee unmounted when it try's to stop the raid-array. I can't see any major problem with not having the raid-stop.sh script as each boot seems to be ok with the filesysem being checked at boot up.

R!tman · Posted: Sat Jul 23, 2005 10:55 am Post subject:

I believe I know the cause of the problem now :-)

:

On my computer the files raid-start.sh and raid-stop.sh are, for obvious reasons, not in /lib/rcscripts. They are in /lib64/rcscripts.

I believe that was the cause of the error message. Now, I also get this:

R!tman · Posted: Sat Jul 23, 2005 11:13 am Post subject:

Well, maybe not solved :-(

.
Although when I emerge mdadm I get this

richard.scott · Posted: Sat Jul 23, 2005 11:30 am Post subject:

ah, this explains things a little more:

https://bugs.gentoo.org/show_bug.cgi?id=99611

In answer to why we now see the errors this bug says:

richard.scott · Posted: Sat Jul 23, 2005 11:32 am Post subject:

are you using a 64bit chip?

I don't get the /lib64 directory listed in my setup. I get this:

R!tman · Posted: Sat Jul 23, 2005 12:06 pm Post subject:

I use the "multilib" use flag. Maybe that is why I have some libs in lib64.

And for the bug report: Do I understand this correct that the error was always there, only it was output to /dev/null?

EDIT: The "WONTFIX" is a little disturbing regarding the bug report :-(

.

Rusty1973 · Posted: Fri Aug 04, 2006 8:31 am Post subject: Had the same Problem

I had the same Problem, that my md1 / wouldn't unmount on shutdown.
I just unemerged mdadm and left raidtools on the system and it works.

Now i only have the Problem Disabling barriers, not supported by the underlying device XFS mounting for filesystem :md2
_________________
I think Linux is able to replace Redmound's Software it is just a matter of time
"Vista just arrived and DRM will take place"

Some years ago it was "FREE KEVIN"
Today it is "FREE THE DESKTOP"

mgbowman · n00b Joined: 31 Jul 2005 Posts: 47

I just recently started exploring the wonderful world of software RAID and have been experiencing the same issues (along with the similar error at bootup). Am I to understand this correctly that the communitity doesn't want to do anything about this? I agree with R!tman with the WONTFIX status being disturbing and know this is a minor issue, but it's just not right.

--mgb
_________________
"Computer programs only do what you tell them to do, not what you want them to do."

SweepingOar · Apprentice Joined: 31 Dec 2003 Posts: 263 Location: LA

Any action on this issue? I've got the same error on shutdown.

MaDDeePee · Guru Joined: 18 Aug 2004 Posts: 393 Location: Germany

Since Raidtools is gone, i need a solution.

I dont like error messages...

andretti · Tux's lil' helper Joined: 25 Feb 2007 Posts: 94

Actually why do we need to (or should) stop raid devices before powering the machine off?

honeymak · Guru Joined: 30 Dec 2002 Posts: 595

i have lvm2 on raid1
/ resides on lvm2

/dev/md0 - consists of /dev/sda1 /dev/sdb1 - /boot - ext3 - raid1
/dev/md1 - consists of /dev/sda2 /dev/sdb2 - swap - raid1
/dev/md2 - consists of /dev/sda3 /dev/sdb3 - / - jfs on lvm2 on raid1

i didn't try the hard way (pipe error to /dev/null)

i see error msg like u guys when shutting down

after a reboot, i can't vgchange/vgdisplay, thus, it does mean something not clean
i just telinit 1
then jfs_fsck on /
it has something to replay
thus it means something not really clean, though it seems not really fs level (every reboot, checkroot reports / is clean)

after that fsck,
telinit 3
i can vgdisplay normally

thus, that busy thing cannot work in /
is this really a bug?
raidtools or pipe to /dev/null is safe? it's a doubt

maybe for the meantime, don't make anything on / ?
just rsync? ohoh
:roll:

_________________
hackers - make sth real
academics - read sth said to be real

stuorguk · Posted: Tue Aug 21, 2007 8:20 am Post subject:

Any updates to this? I am using Raid1 with Reiser4. Every time I shutdown, the root partition is not being unmounted, and causes problems on boot up.

ferg · Posted: Wed Aug 22, 2007 11:00 am Post subject:

I've always seen this error, regarding my root partition. I don't see a problem with the error message though. Remember it's still unmounting the filesystem stored on the RAID array and remounting it Read Only, it's just not stopping the RAID array where the filesystem is stored. As long as the filesystem is unmounted then all is well.

I guess if the error message really annoys you then do as Richard.Scott points out about earlier incarnations, and edit the file to pipe the error to /dev/null.

Cheers
Ferg
_________________
Climb up it, kayak down it + make sure it runs on GNU/Linux
"cease to exist, giving my goodbye, drive my car into the ocean,
you think I'm dead, but i sail away, on a wave of mutilation!"

stuorguk · Posted: Wed Aug 22, 2007 11:11 am Post subject:

It's more than just am error message. Every other boot fails, as the drive was not unmounted cleanly. The kernel loads, and then halts until you do a Ctrl-D to restart it again. Second time around it's ok, until the next reboot.

ferg · Posted: Wed Aug 22, 2007 1:30 pm Post subject:

snailhead · n00b Joined: 13 Nov 2006 Posts: 5

I propose this for raid-stop.sh