# Node Suspension - Recovery **URL:** \ **Category:** Node Operators\ **Tags:** windows, storage-spaces\ **Created:** [June 9, 2022, 4:25am UTC](https://forum.storj.io/t/node-suspension-recovery/18660 "2022-06-09T04:25:56Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![SpyShadow](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/spyshadow/32/60_2.png) [@SpyShadow](https://forum.storj.io/u/SpyShadow)\ **Post date:** [June 9, 2022, 4:25am UTC](https://forum.storj.io/t/node-suspension-recovery/18660/1 "2022-06-09T04:25:56Z")
I was suspended today. A HDD lost connection yesterday. Did not notice it until today. I re-plug it in and it came back to life. I am in process of retiring the HDD (copying data to replacement HDD), so in a few hours, the drive will be removed from my drive pool. Audit shows 100% so I am assuming the data is ok. If the drive was dead, node recovery be impossible. I do wonder if I should use redundancy if I ever setup another node because it took a long time to accumulate the data. ![image](https://storj-s3.bcdn.literatehosting.net/original/2X/b/b9d784977560416cd0f94ee74c0449eda9edde55.png) ---
**Author:** ![SpyShadow](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/spyshadow/32/60_2.png) [@SpyShadow](https://forum.storj.io/u/SpyShadow)\ **Post date:** [June 10, 2022, 7:33am UTC](https://forum.storj.io/t/node-suspension-recovery/18660/2 "2022-06-10T07:33:54Z")
An update. So I was able to add a new disk and migrate data so node is now healthy but when I setup the storage pool, I choose “Simple” Layout for the storage. Having issues removing the bad drive. I am using windows server. Using the storage pools option to combine multiple HDDs. I executed the repair virtual disk command, waiting for it to complete and see if I can remove the bad drive then. First time dealing with the simple layout on windows server storage pools. I do understand there is no redundancy but the HDD came back to life and I managed to migrate 99% of the data from it. There is 2 GB left but I think that is from windows server storage system. ---
**Author:** ![skookum](https://storj.bcdn.literatehosting.com/letter_avatar/skookum/32/5_5575768a8748004e209b776fc1b2916d.png) [@skookum](https://forum.storj.io/u/skookum)\ **Post date:** [June 10, 2022, 9:11pm UTC](https://forum.storj.io/t/node-suspension-recovery/18660/3 "2022-06-10T21:11:41Z")
I’ve seen some different opinions on this forum regarding redundancy versus simplicity/low-cost. Personally I run a node on a ZFS file server that I would be using regardless so I benefit from having some resiliency if a drive fails. You’re right that it takes quite a while to accumulate data but only moments to lose it! ---
**Author:** ![SpyShadow](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/spyshadow/32/60_2.png) [@SpyShadow](https://forum.storj.io/u/SpyShadow)\ **Post date:** [June 11, 2022, 3:51am UTC](https://forum.storj.io/t/node-suspension-recovery/18660/4 "2022-06-11T03:51:18Z")
I think next time I will setup the pool with redundancy. So it’s looking like that if I can’t remove the bad disk, I will have to do a storj exit procedure, delete the pool and start over. repair virtual disk is still running. It’s 50% done. Had to reboot machine due to max out memory. ---
**Author:** ![SpyShadow](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/spyshadow/32/60_2.png) [@SpyShadow](https://forum.storj.io/u/SpyShadow)\ **Post date:** [June 15, 2022, 8:26am UTC](https://forum.storj.io/t/node-suspension-recovery/18660/5 "2022-06-15T08:26:45Z")
Looks like I got no choice but to do a graceful exit in order to rebuild the storage pool from scratch. Note to self, never use simple layout, use mirror or parity to keep a node online through HDD failures. ---
**Author:** ![SpyShadow](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/spyshadow/32/60_2.png) [@SpyShadow](https://forum.storj.io/u/SpyShadow)\ **Post date:** [July 17, 2022, 1:24pm UTC](https://forum.storj.io/t/node-suspension-recovery/18660/6 "2022-07-17T13:24:00Z")
So an update, Graceful Exit is still running. I got one satellite left for data to be removed. I been having to re-attach the HDD in Server Manager after reboot the machine after a week or so. System Memory seems to increase probably due to all the file accessing. Something to do with Windows.