Hi,
I'm using Proxmox Virtual Environment 4.4-1 . I encountered the error "command 'lxc-start -n ' failed: exit code 1" after restarting the server couple of days back. I assumed I have ran out of space on the container (which happened few weeks back) and I tried to resize the container size by incrementing 1 GB. This was failed and following is the error message.
I'm still not able to get the container up. There are few other containers and a VM on the same server, which are working fine though. Appreciateany help in fixing this issue.
Thank you.
I'm using Proxmox Virtual Environment 4.4-1 . I encountered the error "command 'lxc-start -n ' failed: exit code 1" after restarting the server couple of days back. I assumed I have ran out of space on the container (which happened few weeks back) and I tried to resize the container size by incrementing 1 GB. This was failed and following is the error message.
Code:
Virtual Environment 4.4-1/eb2d6f1e
Container 102 ('web' ) on node 'host'
Logs
()
Size of logical volume pve/vm-102-disk-1 changed from 31.00 GiB (7936 extents) to 32.00 GiB (8192 extents).
Logical volume vm-102-disk-1 successfully resized
e2fsck 1.42.12 (29-Aug-2014)
Pass 1: Checking inodes, blocks, and sizes
Inode 7 has illegal block(s). Clear? yes
Illegal block #131094 (7962752) in inode 7. CLEARED.
Illegal block #131095 (11239552) in inode 7. CLEARED.
Illegal block #131096 (20480128) in inode 7. CLEARED.
Illegal block #131097 (23888000) in inode 7. CLEARED.
Illegal block #132118 (7962753) in inode 7. CLEARED.
Illegal block #132119 (11239553) in inode 7. CLEARED.
Illegal block #132120 (20480129) in inode 7. CLEARED.
Illegal block #132121 (23888001) in inode 7. CLEARED.
Illegal block #133142 (7962754) in inode 7. CLEARED.
Illegal block #133143 (11239554) in inode 7. CLEARED.
Illegal block #133144 (20480130) in inode 7. CLEARED.
Too many illegal blocks in inode 7.
Clear inode? yes
Restarting e2fsck from the beginning...
Resize inode not valid. Recreate? yes
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 116, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 116.
Fix? yes
Setting filetype for entry '.' in ??? (116) to 2.
Missing '..' in directory inode 116.
Fix? yes
Setting filetype for entry '..' in ??? (116) to 2.
Directory inode 117, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 117.
Fix? yes
Setting filetype for entry '.' in ??? (117) to 2.
Missing '..' in directory inode 117.
Fix? yes
Setting filetype for entry '..' in ??? (117) to 2.
Directory inode 120, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 120.
Fix? yes
Setting filetype for entry '.' in ??? (120) to 2.
Missing '..' in directory inode 120.
Fix? yes
Setting filetype for entry '..' in ??? (120) to 2.
Directory inode 126, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 126.
Fix? yes
Setting filetype for entry '.' in ??? (126) to 2.
Missing '..' in directory inode 126.
Fix? yes
Setting filetype for entry '..' in ??? (126) to 2.
Directory inode 132, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 132.
Fix? yes
Setting filetype for entry '.' in ??? (132) to 2.
Missing '..' in directory inode 132.
Fix? yes
Setting filetype for entry '..' in ??? (132) to 2.
Directory inode 133, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 133.
Fix? yes
Setting filetype for entry '.' in ??? (133) to 2.
Missing '..' in directory inode 133.
Fix? yes
Setting filetype for entry '..' in ??? (133) to 2.
Directory inode 139, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 139.
Fix? yes
Setting filetype for entry '.' in ??? (139) to 2.
Missing '..' in directory inode 139.
Fix? yes
Setting filetype for entry '..' in ??? (139) to 2.
Directory inode 141, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 141.
Fix? yes
Setting filetype for entry '.' in ??? (141) to 2.
Missing '..' in directory inode 141.
Fix? yes
Setting filetype for entry '..' in ??? (141) to 2.
Directory inode 143, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 143.
Fix? yes
Setting filetype for entry '.' in ??? (143) to 2.
Missing '..' in directory inode 143.
Fix? yes
Setting filetype for entry '..' in ??? (143) to 2.
Directory inode 144, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 144.
Fix? yes
Setting filetype for entry '.' in ??? (144) to 2.
Missing '..' in directory inode 144.
Fix? yes
Setting filetype for entry '..' in ??? (144) to 2.
Directory inode 146, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 146.
Fix? yes
Setting filetype for entry '.' in ??? (146) to 2.
Missing '..' in directory inode 146.
Fix? yes
Setting filetype for entry '..' in ??? (146) to 2.
Directory inode 148, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 148.
Fix? yes
Setting filetype for entry '.' in ??? (148) to 2.
Missing '..' in directory inode 148.
Fix? yes
Setting filetype for entry '..' in ??? (148) to 2.
Directory inode 149, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 149.
Fix? yes
Setting filetype for entry '.' in ??? (149) to 2.
Missing '..' in directory inode 149.
Fix? yes
Setting filetype for entry '..' in ??? (149) to 2.
Directory inode 150, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 150.
Fix? yes
Setting filetype for entry '.' in ??? (150) to 2.
Missing '..' in directory inode 150.
Fix? yes
Setting filetype for entry '..' in ??? (150) to 2.
Directory inode 151, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 151.
Fix? yes
Setting filetype for entry '.' in ??? (151) to 2.
Missing '..' in directory inode 151.
Fix? yes
Setting filetype for entry '..' in ??? (151) to 2.
Directory inode 153, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 153.
Fix? yes
Setting filetype for entry '.' in ??? (153) to 2.
Missing '..' in directory inode 153.
Fix? yes
Setting filetype for entry '..' in ??? (153) to 2.
Directory inode 154, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 154.
Fix? yes
Setting filetype for entry '.' in ??? (154) to 2.
Missing '..' in directory inode 154.
Fix? yes
Setting filetype for entry '..' in ??? (154) to 2.
Directory inode 155, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 155.
Fix? yes
Setting filetype for entry '.' in ??? (155) to 2.
Missing '..' in directory inode 155.
Fix? yes
Setting filetype for entry '..' in ??? (155) to 2.
Directory inode 156, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 156.
Fix? yes
Setting filetype for entry '.' in ??? (156) to 2.
Missing '..' in directory inode 156.
Fix? yes
Setting filetype for entry '..' in ??? (156) to 2.
Directory inode 157, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 157.
Fix? yes
Setting filetype for entry '.' in ??? (157) to 2.
Missing '..' in directory inode 157.
Fix? yes
Setting filetype for entry '..' in ??? (157) to 2.
Directory inode 158, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 158.
Fix? yes
Setting filetype for entry '.' in ??? (158) to 2.
Missing '..' in directory inode 158.
Fix? yes
Setting filetype for entry '..' in ??? (158) to 2.
Directory inode 160, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 160.
Fix? yes
Setting filetype for entry '.' in ??? (160) to 2.
Missing '..' in directory inode 160.
Fix? yes
Setting filetype for entry '..' in ??? (160) to 2.
Directory inode 166, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 166.
Fix? yes
Setting filetype for entry '.' in ??? (166) to 2.
Missing '..' in directory inode 166.
Fix? yes
Setting filetype for entry '..' in ??? (166) to 2.
Directory inode 173, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 173.
Fix? yes
Setting filetype for entry '.' in ??? (173) to 2.
Missing '..' in directory inode 173.
Fix? yes
Setting filetype for entry '..' in ??? (173) to 2.
Directory inode 175, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 175.
Fix? yes
Setting filetype for entry '.' in ??? (175) to 2.
Missing '..' in directory inode 175.
Fix? yes
Setting filetype for entry '..' in ??? (175) to 2.
Directory inode 176, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 176.
Fix? yes
Setting filetype for entry '.' in ??? (176) to 2.
Missing '..' in directory inode 176.
Fix? yes
Setting filetype for entry '..' in ??? (176) to 2.
Directory inode 177, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 177.
Fix? yes
Setting filetype for entry '.' in ??? (177) to 2.
Missing '..' in directory inode 177.
Fix? yes
Setting filetype for entry '..' in ??? (177) to 2.
Directory inode 178, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 178.
Fix? yes
Setting filetype for entry '.' in ??? (178) to 2.
Missing '..' in directory inode 178.
Fix? yes
Setting filetype for entry '..' in ??? (178) to 2.
Directory inode 179, block #0, offset 0: directory corrupted
Salvage? yes
...........
...........
Setting filetype for entry '..' in ??? (1171) to 2.
Directory inode 1172, block #0, offset 0: directory corrupted
Salvage? yesI'm still not able to get the container up. There are few other containers and a VM on the same server, which are working fine though. Appreciateany help in fixing this issue.
Thank you.
