haughjd Absent Member.
Absent Member.
1640 views

Can't read superblock - is my ifodler server RO@

Hello,

I have a problem with my iFolder3 server. Which, is currently running on
an IBM server RAID 5 with 3HDD.

SUSE Linux Enterprise Server 9 (i586)
We have OES1, and iFolder 3.2.
Kernal: 2.6.5-7.244-default

I’m not an expert on linux, but I feel my problem is related to the
way my drives have been mounted. I can no longer log into iFolder, access
iManager – and I’m seeing lots of problems with apache. My
server has been working well for almost 18 months. And now since
Wednesday I've got problems!

When the server boots up, xWindows loads as normal, but as I move around
the interface I start to see various messages such as:

‘Will not save configuration’
‘Configuration file ****** not writable’.

I’ve been reading some TID’s on the internet which talk about
the system going into RO mode to protect itself. I’m assuming this
is what’s happened to me. But who knows?

If I enter the command ‘mount’, at a prompt, it lists all the
drives that are mounted the only one which is RO is my CDROM.

I found another TID which suggested giving the command:

Mount –o –rw,remount /

Which I believe should remount my drive as RW(Read/Write), but when I give
this command, all I get is an error:-

‘can’t read superblock’.

If I exit xWindows, to return to the command prompt. When I log in as
root, the message is displayed:

FATAL: cannot change permissions of TTY: Read-only file system.

So now I’m stuck with a server, that’s not working well at
all, and I’m looking for some advice, suggestions of where to go
next.

Can you help.

Thanks,
Jon
haughjd@endekaceramics.com


Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Can't read superblock - is my ifodler server RO@

It sounds like your iFolder issue is a symptom of a much larget issue,
perhaps even a failing disk? I suggest you ask in the SLES forums as
you're more likely to get help with this there.

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Can't read superblock - is my ifodler server RO@

Jonathan Haughton wrote:

> Hello,
>
> I have a problem with my iFolder3 server. Which, is currently
> running on an IBM server RAID 5 with 3HDD. SUSE Linux Enterprise
> Server 9 (i586) We have OES1, and iFolder 3.2. Kernal:
> 2.6.5-7.244-default
>
> I’m not an expert on linux, but I feel my problem is related to
> the way my drives have been mounted. I can no longer log into
> iFolder, access iManager – and I’m seeing lots of
> problems with apache. My server has been working well for almost 18
> months. And now since Wednesday I've got problems!
>
> When the server boots up, xWindows loads as normal, but as I move
> around the interface I start to see various messages such as:
>
> ‘Will not save configuration’
> ‘Configuration file ****** not writable’.
>
> I’ve been reading some TID’s on the internet which talk
> about the system going into RO mode to protect itself. I’m
> assuming this is what’s happened to me. But who knows?
>
> If I enter the command ‘mount’, at a prompt, it lists all
> the drives that are mounted the only one which is RO is my CDROM.
>
> I found another TID which suggested giving the command:
>
> Mount –o –rw,remount /
>
> Which I believe should remount my drive as RW(Read/Write), but when I
> give this command, all I get is an error:-
>
> ‘can’t read superblock’.


You are trying to remount / (root). Did you install all your stuff in
one single partition ?

Can you do a:
cat /etc/fstab
mount
df -h

and post the outcome of all commands here please

--
Cheers,
Edward
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.