NSA 325 - internal volume down - No such file or directory: '/i-data/md0/.system'
Comments
-
Well, I've started the actions above, and now it's in recovering status
I think all of your advices were missing from my toolbox.... Thank you!0 -
We'll see when recovering is done. Theoretically the raid manager is independent from the volume manager. You had an valid raid array /dev/md0, and you pulled a disk. Then the array is degraded, but that doesn't affect the volume on it. Because raid1. The array can recover without knowledge of the filesystem inside. That's why it lasts that long, all sectors are copied, no matter if they are in use or not. The raid system doesn't know.The kernel messages after the mount look normal. Just a succeeded attempt to mount a valid ext4 filesystem. (Except for the 'Uncached vma' messages. Don't know what that are. I have them too, and they seem harmless.)
0 -
Recovery has been finished, everything is ok. Thanks again for your help!0
Categories
- All Categories
- 431 Beta Program
- 2.6K Nebula
- 170 Nebula Ideas
- 114 Nebula Status and Incidents
- 6K Security
- 385 USG FLEX H Series
- 294 Security Ideas
- 1.5K Switch
- 78 Switch Ideas
- 1.2K Wireless
- 42 Wireless Ideas
- 6.7K Consumer Product
- 267 Service & License
- 412 News and Release
- 87 Security Advisories
- 31 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.9K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 83 Security Highlight