Ich würde erstmal einen neuen Thread für dieses Problem auf Englisch machen. Vielleicht hat jemand eine Idee, wie man dass ohne Neuinstallation lösen kann.
OMV Volumes verkleinern/vergrößern
-
-
Warte mal bis ryecoaaron wieder da ist
-
Hallo Leute, leider habe ich immer noch riesige Probleme mit meinem Volume (LVM).
Mit der Fehlermeldung hat ein User in einem anderen Thread eine Idee welche ich teste.
Leider habe ich riesige Performance und Festplattenprobleme. Ich habe nun nochmals zwei WD red plus zu meinen vorhanden WD red Festplatten hinzugefügt und das LVM damit ergänzt und eingebunden.
Soweit so gut.
Aber jetzt fallen mir extreme Performance Probleme auf und es scheinen Daten (welche ja auf alle 4 Festplatten geschrieben werden) zu fehlen. Sprich wenn ich einen Plex Film anschaue geht der nur noch halb so lang und es fehlt der Schluß. Die fehlenden Minuten sind auf den neuen Festplatten oder wie muss ich mir das vorstellen? Auch startet der NAS nicht mehr immer, Ich muss den NAS mehrmals einschalten (der geht einfach wieder aus).
-
ryecoaaron cabrio_leo: I think you are pros regarding filesystems and LVM.
I attached two additional wd red to my existing LVM (with also two wd red) and added they under LVM within OMV (see screenshot before). Therefore the hard drives are recognized by the bios/uefi and omv.
But now I have horrible problems. The NAS does not start always. I have to press the power button some times to keep the machine on (the NAS immediately went off). And, although the memory space is displayed, there are corrupted files. I think there are some parts written to each of any harddrive included by the LVM.
An example: I copied a movie (to plex) and the movie should have a length of 2h but the movie is only 1h there. Where is the rest? What did I wrong with the LVM?
Thanks a lot.
-
But now I have horrible problems. The NAS does not start always. I have to press the power button some times to keep the machine on (the NAS immediately went off).
I think that is not related to LVM. For me that looks to be a serious power issue of your PC. First of all I would check the power supply of your PC. The two additional WD Red causes more load on the power supply, which could be the reason of your issue.
What happens if you remove the two new disks? Does the PC start anymore then?
Regarding your LVM problem, I can´t support you, because I never have used it. Sorry.
-
For me that looks to be a serious power issue of your PC
Would agree with this root cause analysis and would try confirm with a borrowed or reused power supply in the 230/300 Watt range
PicoPSU-90 12V DC-DC ATX Mini-ITX 0-90W Netzteil Power Supply, SALCAR Premium Ladegerät 12V 6A - 72W - Netzteil,
-
Now I tested the 120W (with additionally 48W) power supply. Same behavior. I pressed the power button to turn on the machine and it went off immediately. With the second press it stays on. And after 6 oder 7 reboots the containers (with my plex mediaserver) are mounted finally.
A mount error also occurs during the boot process.
-
Hi there.
The problems you describe suggest an hardware error. So we'd have to figure out that one first.
Using another power supply is a start, but you wouldn't have a proper one lying around, would you? Those picos are not always very reliable, depending on what you bought.
Your mainboard should only use about 10-15W, provided your footer is the hardware you're using. That also suggests you're using two HDDs with 12TB right? so in total your powersupply should be strong enough *if* it is a proper one.
other suggestions:
- did you check the SMART status of your drives? Are they reporting any issues?
- did you try a BIOS reset? Sometimes if a mainboard got powersupply issues the BIOS is fucked so a reset is a good way to make sure you don't have any issues there.
- did you check your RAM with memtest or similar?
Again, this is something hardware related most likely so we'd have to start to check all that first.
-
Also - do you have a backup?
Just a thought...
-
Zitat
What is proper in your opinion? An internal power supply?
In my experience cheap picos are likely to create problems. Not necessarily the case here but one possible source of error. That's why I mentioned it. A system turning off randomly and disks possibly not spinning up... seems one good place to start.
ZitatThe smart status I can check via OMV GUI?
Or via cli. OMV GUI probably easier. Do you have experience with interpreting those values? If not feel free to post them here.
ZitatRAM isn’t checked up to now (because I thought I worked proper until the new data drives arrived)
Again, your descriptions suggest a hardware issue, in any case it is advisable to exclude these as possible reasons for your problems.
Please check RAM with memtest. A debian-Install CD or any other that has memtest included will do. Let it run at least until you get the report, that there are no problems (over night is a good idea). If you get red warnings right away you know the RAM has an issue and needs to be replaced.
Do not let the HDDs connected during that, as long as you don't have a backup and don't know if the harddrives are indeed OK ... not a good idea.
Plus: you mentioned that you restarted your system dozens of times when it didn't boot up - also VERY bad idea. If it does not start find the problem, solve it. Especially if you do not have a backup...
ZitatSo now I have about 24TB of data without a backup.
But you do have two 14TB drives ... so it might be a good idea to use those to first do a backup?
Your data... I would *never* mess around with LVMs or any partitioning at all without a backup.
ZitatBy the way: I think these problems are related to other(s) posted here OMV starting Problem "emergency mode" on every start
Unlikely. Your system just turns off without reason. You may have more then one problem though. Fixing hardware issues or at least making sure there aren't any is the first step. Well .. doing a proper backup would be the fist step in my opinion.
-
feel free to post them here
I can't interpret it but I posted it yesterday here RE: OMV starting Problem "emergency mode" on every start
I would *never* mess around with LVMs or any partitioning at all without a backup.
You are right, but with the 2 data harddrives (more or less) all was fine. The problems occur by adding the data drive 3+4.
Do not let the HDDs connected during that
can I do that without losing my LVM?
But you do have two 14TB drives ... so it might be a good idea to use those to first do a backup?
but they are already integrated in the LVM - this was my first step after installing them
Your system just turns off without reason.
I think it is much better with the new 120W power supply (at least the suspend mode)
-
I can't interpret it but I posted it yesterday here RE: OMV starting Problem "emergency mode" on every start
This is only the SMART log for your SSD, but the problem may also be caused (much more likely actually) by an HDD. I recommend you start an extended test for each of those.
The SSD seems alright-ish, the count for unexpected powerloss is high but obviously related to your problem. The CRC errors are zero, which is the first thing you should watch. You're temperatures seem a bit high for this time of the year (unless you're based in Australia) but nothing to be concerned about especially for an SSD.
ZitatThe problems occur by adding the data drive 3+4.
I usually don't use LVMs for large datapools, but what exactly did you do?
ZitatI think it is much better with the new 120W power supply (at least the suspend mode)
LOL You're funny.
"Better" meaning it still *does* turn off from time to time and you still don't know why?
Alright, we know the SMART for SSD, now we need that for the remaining HDDs and the RAM-check. Did you try the BIOS-reset? I'd do them in exactely this order, mainly because if one of your drives is causing the issue I'd want to know that first of all.
-
If I may say so - I just scrolled through the other thread and it seems you had this problem for quite a while now - but you don't seem to want to go through the necessary steps to solve it.
You're choice, it's your data and you seem to be balancing right now with no safety-net in 20m above ground and the rope has started to swing ...
You're getting ATA errors and the system shuts randomly down... so if you do not want to lose all your data on those drives you really need to go through the diagnosis and stop turning your system on over and over without knowing what the problem is.
But again, your choice. Sometimes it's also a good experience to start with empty new drives...
Nothing makes humans learn faster then a bit of pain every once in a while. -
based in Australia
I'm far far away from Australia
SMART info HDD1
Code
Alles anzeigensmartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-14-amd64] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WD120EFAX-68UNTN0 Serial Number: 2AHNMEUY LU WWN Device Id: 5 000cca 27ad777ec Firmware Version: 81.00A81 User Capacity: 12,000,138,625,024 bytes [12.0 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 3.5 inches Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Sat Mar 13 23:35:32 2021 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM level is: 1 (minimum power consumption with standby) Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 87) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: (1259) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate PO-R-- 100 100 016 - 0 2 Throughput_Performance --S--- 128 128 054 - 108 3 Spin_Up_Time POS--- 156 156 024 - 420 (Average 421) 4 Start_Stop_Count -O--C- 100 100 000 - 2586 5 Reallocated_Sector_Ct PO--CK 100 100 005 - 0 7 Seek_Error_Rate -O-R-- 100 100 067 - 0 8 Seek_Time_Performance --S--- 140 140 020 - 15 9 Power_On_Hours -O--C- 100 100 000 - 6154 10 Spin_Retry_Count -O--C- 100 100 060 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 316 22 Unknown_Attribute PO---K 100 100 025 - 100 192 Power-Off_Retract_Count -O--CK 098 098 000 - 2711 193 Load_Cycle_Count -O--C- 098 098 000 - 2711 194 Temperature_Celsius -O---- 175 175 000 - 37 (Min/Max 17/43) 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 197 Current_Pending_Sector -O---K 100 100 000 - 0 198 Offline_Uncorrectable ---R-- 100 100 000 - 0 199 UDMA_CRC_Error_Count -O-R-- 200 200 000 - 0 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 1 Comprehensive SMART error log 0x03 GPL R/O 1 Ext. Comprehensive SMART error log 0x04 GPL R/O 256 Device Statistics log 0x04 SL R/O 255 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x08 GPL R/O 2 Power Conditions log 0x09 SL R/W 1 Selective self-test log 0x0c GPL R/O 5501 Pending Defects log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x12 GPL R/O 1 SATA NCQ Non-Data log 0x13 GPL R/O 1 SATA NCQ Send and Receive log 0x15 GPL R/W 1 Rebuild Assist log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x24 GPL R/O 256 Current Device Internal Status Data log 0x25 GPL R/O 256 Saved Device Internal Status Data log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (1 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 256 (0x0100) SCT Support Level: 0 Device State: Active (0) Current Temperature: 37 Celsius Power Cycle Min/Max Temperature: 20/37 Celsius Lifetime Min/Max Temperature: 17/43 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/65 Celsius Min/Max Temperature Limit: -40/70 Celsius Temperature History Size (Index): 128 (39) Index Estimated Time Temperature Celsius 40 2021-03-13 21:28 35 **************** ... ..( 4 skipped). .. **************** 45 2021-03-13 21:33 35 **************** 46 2021-03-13 21:34 36 ***************** ... ..( 23 skipped). .. ***************** 70 2021-03-13 21:58 36 ***************** 71 2021-03-13 21:59 37 ****************** ... ..( 94 skipped). .. ****************** 38 2021-03-13 23:34 37 ****************** 39 2021-03-13 23:35 35 **************** SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) Device Statistics (GP/SMART Log 0x04) not supported Pending Defects log (GP Log 0x0c) supported [please try: '-l defects'] SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 2 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 1 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FISWhy is the status LED for the SSD red and for the data drives green?
I usually don't use LVMs for large datapools, but what exactly did you do?
How do you realize large datapools?
I installed the LVM Plugin for OMV and added the physical volumes to a volume group to create 2 logical volumes (partitions).
Better means, the last time I restarted the NAS I only had to press the power two times (instead 6 or 7 times)
Usually the NAS goes to suspend at night, not completely off.
BIOS-reset
not yet, cause I'm not sure to preserve, but it should?!
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!