Filesystem problem with Lenovo 310
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
3
down vote
favorite
I have installed Ubuntu 18.04 in a Lenovo 310 and I have some problems after some time (the problem usually happens after watching flash videos on the browser) the filesystem gets read-only. For instance when I try to do ls, the following error appears:
bash: cannot create temp file for here-document: Read-only file system
and with dmesg I find the following:
[ 1113.452578] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452615] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452617] mmcblk1: command error, retrying timeout
[ 1113.452908] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452931] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452933] mmcblk1: command error, retrying timeout
[ 1123.552180] mmc1: Timeout waiting for hardware interrupt.
[ 1123.552209] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 1123.552216] mmc1: sdhci: Sys addr: 0x20000008 | Version: 0x00001002
[ 1123.552223] mmc1: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[ 1123.552229] mmc1: sdhci: Argument: 0x02400988 | Trn mode: 0x0000002b
[ 1123.552235] mmc1: sdhci: Present: 0x1fff0001 | Host ctl: 0x0000003d
[ 1123.552241] mmc1: sdhci: Power: 0x0000000b | Blk gap: 0x00000080
[ 1123.552248] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x00000207
[ 1123.552254] mmc1: sdhci: Timeout: 0x00000006 | Int stat: 0x00000000
[ 1123.552260] mmc1: sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
[ 1123.552266] mmc1: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 1123.552272] mmc1: sdhci: Caps: 0x546ec881 | Caps_1: 0x80000807
[ 1123.552278] mmc1: sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[ 1123.552285] mmc1: sdhci: Resp[0]: 0x00400e00 | Resp[1]: 0x00000000
[ 1123.552291] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00400e00
[ 1123.552296] mmc1: sdhci: Host ctl2: 0x0000000d
[ 1123.552303] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x000000016f310200
[ 1123.552306] mmc1: sdhci: ============================================
[ 1123.552579] mmcblk1: error -110 sending stop command, original cmd response 0x0, card status 0x400900
[ 1123.552619] mmcblk1: error -110 transferring data, sector 37751176, nr 8, cmd response 0x0, card status 0x0
When I reboot, there is a terminal telling me to run fsck and after doing that and rebooting again the system is again fine (for a while).
I have read that this might be a kernel problem, but that might be also be a problem with my hardware.
Could someone help me to discover which is the problem? Which log information can I provide to clarify this?
filesystem lenovo emmc
add a comment |Â
up vote
3
down vote
favorite
I have installed Ubuntu 18.04 in a Lenovo 310 and I have some problems after some time (the problem usually happens after watching flash videos on the browser) the filesystem gets read-only. For instance when I try to do ls, the following error appears:
bash: cannot create temp file for here-document: Read-only file system
and with dmesg I find the following:
[ 1113.452578] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452615] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452617] mmcblk1: command error, retrying timeout
[ 1113.452908] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452931] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452933] mmcblk1: command error, retrying timeout
[ 1123.552180] mmc1: Timeout waiting for hardware interrupt.
[ 1123.552209] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 1123.552216] mmc1: sdhci: Sys addr: 0x20000008 | Version: 0x00001002
[ 1123.552223] mmc1: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[ 1123.552229] mmc1: sdhci: Argument: 0x02400988 | Trn mode: 0x0000002b
[ 1123.552235] mmc1: sdhci: Present: 0x1fff0001 | Host ctl: 0x0000003d
[ 1123.552241] mmc1: sdhci: Power: 0x0000000b | Blk gap: 0x00000080
[ 1123.552248] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x00000207
[ 1123.552254] mmc1: sdhci: Timeout: 0x00000006 | Int stat: 0x00000000
[ 1123.552260] mmc1: sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
[ 1123.552266] mmc1: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 1123.552272] mmc1: sdhci: Caps: 0x546ec881 | Caps_1: 0x80000807
[ 1123.552278] mmc1: sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[ 1123.552285] mmc1: sdhci: Resp[0]: 0x00400e00 | Resp[1]: 0x00000000
[ 1123.552291] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00400e00
[ 1123.552296] mmc1: sdhci: Host ctl2: 0x0000000d
[ 1123.552303] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x000000016f310200
[ 1123.552306] mmc1: sdhci: ============================================
[ 1123.552579] mmcblk1: error -110 sending stop command, original cmd response 0x0, card status 0x400900
[ 1123.552619] mmcblk1: error -110 transferring data, sector 37751176, nr 8, cmd response 0x0, card status 0x0
When I reboot, there is a terminal telling me to run fsck and after doing that and rebooting again the system is again fine (for a while).
I have read that this might be a kernel problem, but that might be also be a problem with my hardware.
Could someone help me to discover which is the problem? Which log information can I provide to clarify this?
filesystem lenovo emmc
2
check the output ofdmesg
for error messages regarding the disk subsystem
â Sebastian Stark
Jun 11 at 17:53
I have installed it in an eMMC (in Lenovo Yoga 310).
â Alex Grilo
Jun 13 at 12:23
Only half the bounty??? What happened?
â Fabby
Jun 22 at 19:08
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I have installed Ubuntu 18.04 in a Lenovo 310 and I have some problems after some time (the problem usually happens after watching flash videos on the browser) the filesystem gets read-only. For instance when I try to do ls, the following error appears:
bash: cannot create temp file for here-document: Read-only file system
and with dmesg I find the following:
[ 1113.452578] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452615] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452617] mmcblk1: command error, retrying timeout
[ 1113.452908] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452931] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452933] mmcblk1: command error, retrying timeout
[ 1123.552180] mmc1: Timeout waiting for hardware interrupt.
[ 1123.552209] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 1123.552216] mmc1: sdhci: Sys addr: 0x20000008 | Version: 0x00001002
[ 1123.552223] mmc1: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[ 1123.552229] mmc1: sdhci: Argument: 0x02400988 | Trn mode: 0x0000002b
[ 1123.552235] mmc1: sdhci: Present: 0x1fff0001 | Host ctl: 0x0000003d
[ 1123.552241] mmc1: sdhci: Power: 0x0000000b | Blk gap: 0x00000080
[ 1123.552248] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x00000207
[ 1123.552254] mmc1: sdhci: Timeout: 0x00000006 | Int stat: 0x00000000
[ 1123.552260] mmc1: sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
[ 1123.552266] mmc1: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 1123.552272] mmc1: sdhci: Caps: 0x546ec881 | Caps_1: 0x80000807
[ 1123.552278] mmc1: sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[ 1123.552285] mmc1: sdhci: Resp[0]: 0x00400e00 | Resp[1]: 0x00000000
[ 1123.552291] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00400e00
[ 1123.552296] mmc1: sdhci: Host ctl2: 0x0000000d
[ 1123.552303] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x000000016f310200
[ 1123.552306] mmc1: sdhci: ============================================
[ 1123.552579] mmcblk1: error -110 sending stop command, original cmd response 0x0, card status 0x400900
[ 1123.552619] mmcblk1: error -110 transferring data, sector 37751176, nr 8, cmd response 0x0, card status 0x0
When I reboot, there is a terminal telling me to run fsck and after doing that and rebooting again the system is again fine (for a while).
I have read that this might be a kernel problem, but that might be also be a problem with my hardware.
Could someone help me to discover which is the problem? Which log information can I provide to clarify this?
filesystem lenovo emmc
I have installed Ubuntu 18.04 in a Lenovo 310 and I have some problems after some time (the problem usually happens after watching flash videos on the browser) the filesystem gets read-only. For instance when I try to do ls, the following error appears:
bash: cannot create temp file for here-document: Read-only file system
and with dmesg I find the following:
[ 1113.452578] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452615] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452617] mmcblk1: command error, retrying timeout
[ 1113.452908] mmc1: mmc_hs400_to_hs200 failed, error -110
[ 1113.452931] mmcblk1: timed out sending r/w cmd command, card status 0x400e00
[ 1113.452933] mmcblk1: command error, retrying timeout
[ 1123.552180] mmc1: Timeout waiting for hardware interrupt.
[ 1123.552209] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 1123.552216] mmc1: sdhci: Sys addr: 0x20000008 | Version: 0x00001002
[ 1123.552223] mmc1: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[ 1123.552229] mmc1: sdhci: Argument: 0x02400988 | Trn mode: 0x0000002b
[ 1123.552235] mmc1: sdhci: Present: 0x1fff0001 | Host ctl: 0x0000003d
[ 1123.552241] mmc1: sdhci: Power: 0x0000000b | Blk gap: 0x00000080
[ 1123.552248] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x00000207
[ 1123.552254] mmc1: sdhci: Timeout: 0x00000006 | Int stat: 0x00000000
[ 1123.552260] mmc1: sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
[ 1123.552266] mmc1: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 1123.552272] mmc1: sdhci: Caps: 0x546ec881 | Caps_1: 0x80000807
[ 1123.552278] mmc1: sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[ 1123.552285] mmc1: sdhci: Resp[0]: 0x00400e00 | Resp[1]: 0x00000000
[ 1123.552291] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00400e00
[ 1123.552296] mmc1: sdhci: Host ctl2: 0x0000000d
[ 1123.552303] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x000000016f310200
[ 1123.552306] mmc1: sdhci: ============================================
[ 1123.552579] mmcblk1: error -110 sending stop command, original cmd response 0x0, card status 0x400900
[ 1123.552619] mmcblk1: error -110 transferring data, sector 37751176, nr 8, cmd response 0x0, card status 0x0
When I reboot, there is a terminal telling me to run fsck and after doing that and rebooting again the system is again fine (for a while).
I have read that this might be a kernel problem, but that might be also be a problem with my hardware.
Could someone help me to discover which is the problem? Which log information can I provide to clarify this?
filesystem lenovo emmc
edited Jun 12 at 8:09
muru
128k19269459
128k19269459
asked Jun 11 at 16:01
Alex Grilo
664
664
2
check the output ofdmesg
for error messages regarding the disk subsystem
â Sebastian Stark
Jun 11 at 17:53
I have installed it in an eMMC (in Lenovo Yoga 310).
â Alex Grilo
Jun 13 at 12:23
Only half the bounty??? What happened?
â Fabby
Jun 22 at 19:08
add a comment |Â
2
check the output ofdmesg
for error messages regarding the disk subsystem
â Sebastian Stark
Jun 11 at 17:53
I have installed it in an eMMC (in Lenovo Yoga 310).
â Alex Grilo
Jun 13 at 12:23
Only half the bounty??? What happened?
â Fabby
Jun 22 at 19:08
2
2
check the output of
dmesg
for error messages regarding the disk subsystemâ Sebastian Stark
Jun 11 at 17:53
check the output of
dmesg
for error messages regarding the disk subsystemâ Sebastian Stark
Jun 11 at 17:53
I have installed it in an eMMC (in Lenovo Yoga 310).
â Alex Grilo
Jun 13 at 12:23
I have installed it in an eMMC (in Lenovo Yoga 310).
â Alex Grilo
Jun 13 at 12:23
Only half the bounty??? What happened?
â Fabby
Jun 22 at 19:08
Only half the bounty??? What happened?
â Fabby
Jun 22 at 19:08
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
You have a hardware problem, but you might be able to save the eMMC by doing the following:
- plug the eMMC into another computer running Ubuntu
install ddrescue:
sudo apt-get install gddrescue
copy the eMMC to an image on the HDD of the other computer:
ddrescue --direct --retry-passes=3 /dev/XdY /tmp/eMMC.img /tmp/eMMC.log
The above command will tells ddrescue to:
--direct
use direct disk access and ignore the kernelâÂÂs cache--retry-passes=3
retry bad sectors 3 times before giving up./dev/XdY
is the MMC we are rescuing whereX
andY
denominate the identifier of the MMCeMMC.img
is the name of the image fileeMMC.log
is the name of the logfile. Always use a logfile. This allows you to resume an interrupted image at the point you left off, or to retry bad sectors after an initial pass. Without a logfile, you will have to start over again!
After that completes, unmount the MMC if needed
Insert a new MMC in the MMC slot of the computer and execute:
ddrescue --force /tmp/eMMC.img /dev/XdY /tmp/eMMC.restore.log
insert the new MMC back into your Lenovo and reboot
Done!
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
You have a hardware problem, but you might be able to save the eMMC by doing the following:
- plug the eMMC into another computer running Ubuntu
install ddrescue:
sudo apt-get install gddrescue
copy the eMMC to an image on the HDD of the other computer:
ddrescue --direct --retry-passes=3 /dev/XdY /tmp/eMMC.img /tmp/eMMC.log
The above command will tells ddrescue to:
--direct
use direct disk access and ignore the kernelâÂÂs cache--retry-passes=3
retry bad sectors 3 times before giving up./dev/XdY
is the MMC we are rescuing whereX
andY
denominate the identifier of the MMCeMMC.img
is the name of the image fileeMMC.log
is the name of the logfile. Always use a logfile. This allows you to resume an interrupted image at the point you left off, or to retry bad sectors after an initial pass. Without a logfile, you will have to start over again!
After that completes, unmount the MMC if needed
Insert a new MMC in the MMC slot of the computer and execute:
ddrescue --force /tmp/eMMC.img /dev/XdY /tmp/eMMC.restore.log
insert the new MMC back into your Lenovo and reboot
Done!
add a comment |Â
up vote
2
down vote
You have a hardware problem, but you might be able to save the eMMC by doing the following:
- plug the eMMC into another computer running Ubuntu
install ddrescue:
sudo apt-get install gddrescue
copy the eMMC to an image on the HDD of the other computer:
ddrescue --direct --retry-passes=3 /dev/XdY /tmp/eMMC.img /tmp/eMMC.log
The above command will tells ddrescue to:
--direct
use direct disk access and ignore the kernelâÂÂs cache--retry-passes=3
retry bad sectors 3 times before giving up./dev/XdY
is the MMC we are rescuing whereX
andY
denominate the identifier of the MMCeMMC.img
is the name of the image fileeMMC.log
is the name of the logfile. Always use a logfile. This allows you to resume an interrupted image at the point you left off, or to retry bad sectors after an initial pass. Without a logfile, you will have to start over again!
After that completes, unmount the MMC if needed
Insert a new MMC in the MMC slot of the computer and execute:
ddrescue --force /tmp/eMMC.img /dev/XdY /tmp/eMMC.restore.log
insert the new MMC back into your Lenovo and reboot
Done!
add a comment |Â
up vote
2
down vote
up vote
2
down vote
You have a hardware problem, but you might be able to save the eMMC by doing the following:
- plug the eMMC into another computer running Ubuntu
install ddrescue:
sudo apt-get install gddrescue
copy the eMMC to an image on the HDD of the other computer:
ddrescue --direct --retry-passes=3 /dev/XdY /tmp/eMMC.img /tmp/eMMC.log
The above command will tells ddrescue to:
--direct
use direct disk access and ignore the kernelâÂÂs cache--retry-passes=3
retry bad sectors 3 times before giving up./dev/XdY
is the MMC we are rescuing whereX
andY
denominate the identifier of the MMCeMMC.img
is the name of the image fileeMMC.log
is the name of the logfile. Always use a logfile. This allows you to resume an interrupted image at the point you left off, or to retry bad sectors after an initial pass. Without a logfile, you will have to start over again!
After that completes, unmount the MMC if needed
Insert a new MMC in the MMC slot of the computer and execute:
ddrescue --force /tmp/eMMC.img /dev/XdY /tmp/eMMC.restore.log
insert the new MMC back into your Lenovo and reboot
Done!
You have a hardware problem, but you might be able to save the eMMC by doing the following:
- plug the eMMC into another computer running Ubuntu
install ddrescue:
sudo apt-get install gddrescue
copy the eMMC to an image on the HDD of the other computer:
ddrescue --direct --retry-passes=3 /dev/XdY /tmp/eMMC.img /tmp/eMMC.log
The above command will tells ddrescue to:
--direct
use direct disk access and ignore the kernelâÂÂs cache--retry-passes=3
retry bad sectors 3 times before giving up./dev/XdY
is the MMC we are rescuing whereX
andY
denominate the identifier of the MMCeMMC.img
is the name of the image fileeMMC.log
is the name of the logfile. Always use a logfile. This allows you to resume an interrupted image at the point you left off, or to retry bad sectors after an initial pass. Without a logfile, you will have to start over again!
After that completes, unmount the MMC if needed
Insert a new MMC in the MMC slot of the computer and execute:
ddrescue --force /tmp/eMMC.img /dev/XdY /tmp/eMMC.restore.log
insert the new MMC back into your Lenovo and reboot
Done!
edited Jun 20 at 21:32
answered Jun 19 at 21:21
![](https://i.stack.imgur.com/GlTt8.png?s=32&g=1)
![](https://i.stack.imgur.com/GlTt8.png?s=32&g=1)
Fabby
23.6k1351146
23.6k1351146
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1045652%2ffilesystem-problem-with-lenovo-310%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
2
check the output of
dmesg
for error messages regarding the disk subsystemâ Sebastian Stark
Jun 11 at 17:53
I have installed it in an eMMC (in Lenovo Yoga 310).
â Alex Grilo
Jun 13 at 12:23
Only half the bounty??? What happened?
â Fabby
Jun 22 at 19:08