Could be a permission issue, that the site does not have permission to make a directory within your new host.

see

http://legacy-documentation.concrete5.org/tutorials/sort-out-file-p...

Thanks for the reply - I've tried the commands from the page you linked but still no joy unfortunately.

I've attached a quick snapshot of the permissions of the root of the concrete/ folder - I think they look correct after the permission edits!

The problem will be in your site root or beneath that in the application or packages folder, not the concrete folder.

Hi,

I've been doing some testing, as soon as my concrete install gets to version 5.7.4.2 the mkdir errors appear, anything before that is fine.

This is a fresh install and I have ran the chmod commands again but no joy.

Just in case anybody else looks at this thread, I've reported this problem to Fasthosts after getting the same 'mkdir(): Input/output error.' and they have acknowledged that there is a problem on their new hosting platform installing Concrete5.

This is what they said :

-----
We are aware of an issue with installing concrete5 on our newer hosting platform.

The issue is currently under investigation.

Sadly we don't have an ETA for a fix on the issue, but the issue has occurred over the past couple of weeks so hopefully a fix should be implemented soon.

Apologies for any inconvenience caused.
-----

Just as an additional to this (after spending about 2 weeks with Fasthosts support...who aren't the best at times)

I managed to get it working by adding:



Into the concrete.php (application/config). It's slow but works.

It's down to their implementation of memcached on the newer cluster servers at Fasthosts but I can't seem to find a way to get concrete5 to use memcached as a session handler.

Hello.

Can you confirm which file you put this in? I am hosting with fasthosts and have the same mkdir error.

I can't see concrete.php under application/config.

Thanks
Peter.

I can't remember 100% what I did now but I believe I took a fresh copy of Concrete5, put it onto the hosting and created a concrete.php file in the application/config path and pasted the code on my previous reply into there - saved and then ran through the install and it worked.

Hello,

Did FastHosts ever come back to you on this? My site is incredibly slow still.

Thanks
Peter.

Hello,

Did FastHosts ever come back to you on this? My site is incredibly slow still.

Thanks
Peter.

Thank you for this. I have no idea why it worked, but it did.

Did you ever find out why this was suddenly necessary?

This can be suddenly necessary if the host or developer suddenly activates some forms of CDN/caching, such as Varnish. An alternative is to turn that off.