Beiträge von its-my-right

Hello, thank you for spending time helping me to solve my issue ! Until few days I'm not at home so I can't try what you advised me to, but as soon as I tried, I'll let you know the results. Thanks again !

Hi, my motherboard is an Asus C60M1-I, and my system HDD is a 80 Gb seagate. I must add that my OMV is installed over debian 6 and that I managed this system to work for several months without any problems of that kind. All I did to get these problems was to update OMV

Hello all,

Today I tried to update from 0.4.16 to 0.4.28. It worked fine but after rebooting my NAS, the ps2 keyboard and the usb mouse did not work anymore. For the mouse, I've got to unplug/replug it in order for it to work but with the keyboard it do not work. But with an usb keyboard, it works like the mouse after unplugging/replugging it.

Also, I had network problems after rebooting, but I managed to solve them manually.

Do you know what possibly happened ? and how to solve this mouse/keyboard problem ? Because I do not plug keyboard/mouse on my NAS everyday but still, it is annoying.

Thank you very much for your help !

Hello everyone,

I have a new problem since few days:

Some logs are not viewable from OMV's webui, for example, the autoshutdown one.

When I try to access it, I just get an error message:

Error
An error has occured

And the "details" button only says me:

Internal Server Error

Do you know what did cause that and how could I fix it ?

thank you !

Ok thanks, I really need to correctly configure my disks power management settings because my situation is not acceptable.

I did two tests separate by only 7h and watched the LCC thanks to smart, before and after:

2To seagate : +0
1To samsung: +58
60 Go seagate (on which is install debian + omv): +10
3To WD: +5
3To Seagate: +7

It does not seem really normal to me, especially the Samsung one ! So I rellay need to find a fix quickly before it dies

Hello everyone !

I built my NAS last week and I am still perfecting it's installation.
Today I worry about the "advanced power management" of HDD availables. I read on the internet various thing, but my (maybe false) conclusion is that it is better to let all the disks on "Disabled" because other options could cause damages to disks.

Is that right ?

How did you set your advanced power management for HDD ?

Also, what is the difference between the "1 - disabled" and "255 - disabled" settings ?

Thank you !

Same here ! Can someone explain how to make daap works under omv 0.4 ?

Thanks !

Please Help, exactly the same problem here (omv 0.4). Thanks !

Here is what sensors-detect answer me:

root@NAS:~# sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: System manufacturer System Product Name
# Board: ASUSTeK COMPUTER INC. C60M1-I


This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.


Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
Intel Core family thermal sensor...                         No
Intel Atom thermal sensor...                                No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No


Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8771
    (logical device 4 has address 0x290, could be sensors)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No


Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No


Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No


Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus
Module i2c-dev loaded successfully.


Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                No


Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.
root@NAS:~#

It's an Asus C60 m1-i with integrated cpu.

I installed Debian 6 on my Hard drive, and install openmediavault from it. Now it works like a charm with original ram and psu. I don't know at all what was missing in openmediavault that is not in debian and let me sleep/resume properly, but I'm so glad it works !

It happens that I'm running the latest bios update. I will try to install debian 6.0.6 on my system disk and test the pm-suspend option. If it works, I think it would definitely means that there is no more hardware problems.

I changed the memory sticks and now I get the suspend to successfully resume. (the original memory stick was in the QVL of the motherboard...)

But... from time to time, when I resume: I've got nothin on screen (and nas no reechable via ip) or I get the error:

version glibc_private not defined in file ld-linux-x86-64.so.2 with link time reference

Is there a way to repair that ?

Thanks

I've tried 2 other psu and no changes at all.

I can correctly resume from a suspend to disk (hibernate) but not from a suspend to ram (suspend with pm-suspend).

I've tried pm-suspend with all the quirks I've found on the manpage but still no changes: no display, no network...

I don't know at all what is causing that...

Ok thank you !

In fact my psu is a brand new Antec Neo eco 400c. So maybe it is not "bad" but it is the "eco" side doing this ?

Will try tomorrow with the cooler master psu which allows windows 7 to suspend/resume for a long time on my Htpc and let you know.

But what I don't get is why the resume from hibernate works well and not the resume from suspend, if it is my psu. Which step exactly in a classic suspend/resume cycle do you think is blocking on my conf ?

Thank you

When resume after suspend I can't.

But when I send magic packet when nas shutdown or in hibernate mode, it works, the nas wake up and I can reech it via ssh. Only the "suspend" mode does not resume correctly, and I would really like it to work because it is the faster to re-establish network connexion, etc after waking up...

Hello everybody,

First I'd like to say I'm a big newbie about linux (first time I touch it), but I'm very willing to learn. Secondly: I am French, so excuse my English.

I've got Openmediavault 0.4 installed on HDD. I was very interested in WOL combined to AutoShutdown. Let's just see the WOL part for now.

I've managed to install pm-utils on my system through command lines and managed to modify (following tutorial on ubuntu doc) files in order to activate wake on lan every time on the network adapter.

So that's it, when suspending (using pm-suspend), the nas suspends ! and I can send it magic packet and the fans are back on, it resumes !

.....

Almost...

Because there is no display on screen, I can't access the nas from web interface, ssh, windows network... I must cut power, disconnect/reconnect system drive, and power on in order to get my openmediavault back.

Do you know what exactly I should do in order to get a proper resume that allows system to launch and network to be ok ?

I heard it might be because my Bios doesn't propose me to change between S1/S3 sleep mode (no option at all) ? Or because of the SWAP space ? Is there anything I could do in order to get my suspend/resume to work properly ?

Thank you so much !

(it's another topic but in web interface, under system infos, it says 1.57 GiB memory...? I've got a transceng 2 Go fully compatible with my motherboard (it's in it's compatibility list) is that in any way normal ?)